From: Wesley Darlington (wesley at domain yelsew.com)
Date: Wed 01 Aug 2001 - 12:09:59 IST
On Wed, Aug 01, 2001 at 11:52:35AM +0100, Gavin O Gorman wrote:
> eth0 - 192.168.100.2
> eth1 - 188.8.131.52 ( external address, not real one )
> 184.108.40.206 is connected to 220.127.116.11, the router to the net.
> I want to be able to ping 18.104.22.168 ( not actually get on the net, i'm
> not looking to do NAT here, just barebones ip forwarding )
> when i attempt to ping 22.214.171.124 it is grand. When i attempt to
> ping 126.96.36.199, it times out.
Does the "gateway to the net" know that to get packets (back) to
192.168.100.0/24, it has to send them via 188.8.131.52?
> with still no luck. One possibility I thought of is that the router will
> just drop any packets it recieves from a private IP address. Could that be
> it ?
Probably. There's nothing special about private addresses as far as the
router is concerned - it just doesn't know how to get packets to *your*
You probably want to do nat on the dual-homed iptables box. Or configure
your router with a static route to 192.168.100.0/24. Or run a routing
protocol on your routers...
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:11:25 GMT