1 |
Hi, |
2 |
|
3 |
On Sun, 13 Jan 2008 16:42:56 +0530 |
4 |
Holla <holla.net@×××××.com> wrote: |
5 |
|
6 |
> One thing, I cannot understand is the difference in traceroute |
7 |
> results. What does this say in plain english ? :-) |
8 |
> |
9 |
> At PC2 |
10 |
> # traceroute 218.248.240.46 (ISP's DNS server) |
11 |
> traceroute to 218.248.240.46 (218.248.240.46), 30 hops max, 40 byte packets |
12 |
> 1 192.168.2.43 (192.168.2.43) 1.730 ms 0.840 ms 0.920 ms |
13 |
> 2 192.168.1.1 (192.168.1.1) 1.440 ms 1.469 ms 1.287 ms |
14 |
> 3 * * * |
15 |
> 4 * * * |
16 |
> |
17 |
> At PC1 |
18 |
> |
19 |
> # traceroute 218.248.240.46 |
20 |
> traceroute to 218.248.240.46 (218.248.240.46), 30 hops max, 40 byte packets |
21 |
> 1 192.168.1.1 (192.168.1.1) 0.848 ms 0.706 ms 0.681 ms |
22 |
> 2 117.192.128.1 (117.192.128.1) 19.712 ms 18.878 ms 19.920 ms |
23 |
> 3 218.248.160.134 (218.248.160.134) 19.292 ms 19.796 ms 19.190 ms |
24 |
|
25 |
I'd say your router (Router1) isn't doing NAT for packets from other |
26 |
subnets than it's LAN interface is configured for -- regardless of the |
27 |
(correctly) configured internal additional route. |
28 |
|
29 |
So your option would be to set up PC1 for doing NAT, not necessarily |
30 |
for packets 192.168.2/24<->192.168.1/24, but for all packets from |
31 |
192.168.2/24 going to the internet. |
32 |
|
33 |
Your provider most likely does not have anything to do with all this. |
34 |
|
35 |
-hwh |
36 |
-- |
37 |
gentoo-user@l.g.o mailing list |