Re: ip forwarding woes



David Zelinsky wrote:

With this setup, I expect to be able to ping 10.0.0.2 from 192.168.0.2
(and vice versa), with packets routed through the firewall, but it
doesn't work.

What am I overlooking?

It looks like that 10.0.0.2 does not have a route to 192.168.0.0/24 or
that 192.168.0.2 does not have a route to 10.0.0.0/24 or both:
192.168.0.2# ip route add 10.0.0.0/24 via 192.168.0.1
10.0.0.2# ip route add 192.168.0.0/24 via 10.0.0.1

If the firewall is the main router for the network then you can set up a
default route to it on each of the other hosts:
192.168.0.2# ip route add default via 192.168.0.1
10.0.0.2# ip route add default via 10.0.0.1

You will need to have the iproute package installed to get the ip(8)
command.



--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx



Relevant Pages

  • Re: Web server behind Symantec Enterprise Firewall
    ... I've published a virtual IP at the Firewall to which i route the http ... NAT rule AccesoServer was chosen, but client transparency is ... Since the web server is on the LAN, you shouldn't have to add any route ...
    (comp.security.firewalls)
  • Re: Urgent RRAS wont work Help!
    ... plus it worked before without a route on the FW. ... > Where you need the extra routing is on the firewall. ... > port access rights to clients on the 184.155.0.0 network. ...
    (microsoft.public.win2000.ras_routing)
  • Re: Web server behind Symantec Enterprise Firewall
    ... It seems it does not matter wich interfaces i set at the rule, ... tries to route it trought the same interface. ... firewall to the internal sever?... ... > on the firewall to point to the web server. ...
    (comp.security.firewalls)
  • Re: Urgent RRAS wont work Help!
    ... Where you need the extra routing is on the firewall. ... route but whatever config I use it won't route. ... The clients on the ... network have the default gateway set as 184.155.0.80 via DHCP. ...
    (microsoft.public.win2000.ras_routing)
  • Re: strange problem connecting 2 linux boxes
    ... > problem is because of a firewall. ... >> WRONG ROUTE TO IP ADDRESS ... The firewall host here could ping a host ... No ifconfig or route output from 192.168.0.1 ... ...
    (comp.os.linux.networking)