Mike Mazur wrote:
Router1 needs a route to point back to PC2 so when traffic bound for it
comes it, it'll know what to do with it.
route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.23
Also if you want PC2 to access the net, you would need PC1 to be smart
enough to route/NAT packets from PC2 to Router 1.
Not true in this case.
Router1 is the NAT device and everything else is internal or so I
assumed. You don't want NAT behind NAT on your network if you can help
it. It tends to break things and is hard to troubleshoot.
PC1 does need to have IP forwarding turned on which the original poster
mentioned he configured.
The tests I would run are:
ping 192.168.2.43 from router1. That'll test that router1 knows how to
get to 192.168.2.0. I don't think packet forwarding has to be working
for this to return since the interfaces are all local on PC1.
ping router 1 from PC2 and vice versa. That'll make sure that PC1 is
forwarding packets correctly.
If both of these are fine, it's possible the router1 is not NATing
192.168.2.0/24 addresses.
kashani
--
gentoo-user@lists.gentoo.org mailing list
