I'm guessing here, but do you mean that I have to add the routes to the
Linux box? Don't know if they can be added to the D Link.

Either way I'd need help!

Did I mention that now I can access Apache from the laptop? This is
good,so we may not even have to go any further on this. As long as I can
go from those behind the D Link to the Linux box, I'm happy!


On Mon, 2002-12-30 at 13:12, Kyle Faber wrote:
> On Monday 30 December 2002 1:38 pm, mazdaracer wrote:
> > Interesting!  Changed D Link to 192.168.5.2 and the laptop updated to
> > 5.100 with a 5.2 gateway. Have net access; can also ping 192.168.0.10,
> > the linux box!
> >
> > Tried to ping from the linux box to the laptop. No go. But then I
> > noticed it was as if I was pinging from eth0, the external interface,
> > and not eth1. So do I have an issue on the linux side now?
> >
> 
> 	Excellent.  This answer is easy.  You can't ping through a NAT device unless 
> you build manual route tables.  Even though they happen to both be internal 
> subnets, pinging though the DLink to the laptops is like being outside your 
> DSL and trying to ping through another router.  It's just not going to 
> happen, the NAT Device is blocking the pings.
> 
> 	Don't know if that sentence actually makes sense.  Someone who knows what I 
> am trying to say want to re-interpolate that for me?
> 
> 
> Kyle Faber
> EMR Internet
> kyle@emr.net
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change  you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss