| 1 |
Mike Mazur wrote: |
| 2 |
>> Router1 needs a route to point back to PC2 so when traffic bound for it |
| 3 |
>> comes it, it'll know what to do with it. |
| 4 |
>> route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.23 |
| 5 |
> |
| 6 |
> Also if you want PC2 to access the net, you would need PC1 to be smart |
| 7 |
> enough to route/NAT packets from PC2 to Router 1. |
| 8 |
|
| 9 |
Not true in this case. |
| 10 |
|
| 11 |
Router1 is the NAT device and everything else is internal or so I |
| 12 |
assumed. You don't want NAT behind NAT on your network if you can help |
| 13 |
it. It tends to break things and is hard to troubleshoot. |
| 14 |
|
| 15 |
PC1 does need to have IP forwarding turned on which the original poster |
| 16 |
mentioned he configured. |
| 17 |
|
| 18 |
The tests I would run are: |
| 19 |
|
| 20 |
ping 192.168.2.43 from router1. That'll test that router1 knows how to |
| 21 |
get to 192.168.2.0. I don't think packet forwarding has to be working |
| 22 |
for this to return since the interfaces are all local on PC1. |
| 23 |
|
| 24 |
ping router 1 from PC2 and vice versa. That'll make sure that PC1 is |
| 25 |
forwarding packets correctly. |
| 26 |
|
| 27 |
If both of these are fine, it's possible the router1 is not NATing |
| 28 |
192.168.2.0/24 addresses. |
| 29 |
|
| 30 |
kashani |
| 31 |
-- |
| 32 |
gentoo-user@l.g.o mailing list |
Archives