Never mind, I found my mistake. Sorry to bother people.
It turns out routing table on the 10.0.0.2 host was wrong, and it was
causing the return packets to be lost.
When I made the configuration agree with what I describe below,
everything works as expected.
-David
David Zelinsky <[EMAIL PR
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 no
On Sat, Mar 08, 2008 at 03:37:54PM -0500, David Zelinsky wrote:
> I'm trying to set up a firewall/gateway, and I can't seem to get
> ip forwarding to work. I'm using linux kernel 2.6.23 with iptables
> enabled. Here's what happens.
>
> The firewall machine has two interfaces (both on private net
I'm trying to set up a firewall/gateway, and I can't seem to get
ip forwarding to work. I'm using linux kernel 2.6.23 with iptables
enabled. Here's what happens.
The firewall machine has two interfaces (both on private networks, for
testing purposes):
IFIPNetmask
eth0 192.168.0
4 matches
Mail list logo
