From: Wesley Darlington (wesley at domain yelsew.com)
Date: Wed 01 Aug 2001 - 12:09:59 IST
Hi All,
With snippage...
On Wed, Aug 01, 2001 at 11:52:35AM +0100, Gavin O Gorman wrote:
> eth0 - 192.168.100.2
> eth1 - 159.134.206.7 ( external address, not real one )
> 159.134.207.7 is connected to 159.134.206.1, the router to the net.
> I want to be able to ping 159.134.206.1 ( not actually get on the net, i'm
> not looking to do NAT here, just barebones ip forwarding )
> when i attempt to ping 159.134.207.7 it is grand. When i attempt to
> ping 159.134.206.1, 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 159.134.206.7?
> 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*
private addresses.
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...
Wesley.
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:11:25 GMT