| 1 |
On Sunday 13 January 2008, Hans-Werner Hilse wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> On Sun, 13 Jan 2008 16:42:56 +0530 |
| 5 |
> |
| 6 |
> Holla <holla.net@×××××.com> wrote: |
| 7 |
> > One thing, I cannot understand is the difference in traceroute |
| 8 |
> > results. What does this say in plain english ? :-) |
| 9 |
> > |
| 10 |
> > At PC2 |
| 11 |
> > # traceroute 218.248.240.46 (ISP's DNS server) |
| 12 |
> > traceroute to 218.248.240.46 (218.248.240.46), 30 hops max, 40 byte |
| 13 |
> > packets 1 192.168.2.43 (192.168.2.43) 1.730 ms 0.840 ms 0.920 ms |
| 14 |
> > 2 192.168.1.1 (192.168.1.1) 1.440 ms 1.469 ms 1.287 ms |
| 15 |
> > 3 * * * |
| 16 |
> > 4 * * * |
| 17 |
> > |
| 18 |
> > At PC1 |
| 19 |
> > |
| 20 |
> > # traceroute 218.248.240.46 |
| 21 |
> > traceroute to 218.248.240.46 (218.248.240.46), 30 hops max, 40 byte |
| 22 |
> > packets 1 192.168.1.1 (192.168.1.1) 0.848 ms 0.706 ms 0.681 ms |
| 23 |
> > 2 117.192.128.1 (117.192.128.1) 19.712 ms 18.878 ms 19.920 ms |
| 24 |
> > 3 218.248.160.134 (218.248.160.134) 19.292 ms 19.796 ms 19.190 ms |
| 25 |
> |
| 26 |
> I'd say your router (Router1) isn't doing NAT for packets from other |
| 27 |
> subnets than it's LAN interface is configured for -- regardless of the |
| 28 |
> (correctly) configured internal additional route. |
| 29 |
> |
| 30 |
> So your option would be to set up PC1 for doing NAT, not necessarily |
| 31 |
> for packets 192.168.2/24<->192.168.1/24, but for all packets from |
| 32 |
> 192.168.2/24 going to the internet. |
| 33 |
> |
| 34 |
> Your provider most likely does not have anything to do with all this. |
| 35 |
|
| 36 |
I agree that this is not related to the ISP. What you probably need to do is |
| 37 |
set up RIP2 in your router 1, to be able to recognise other subdomains |
| 38 |
(192.168.2.XXX). Then it'll process packets coming from that subdomain. The |
| 39 |
router manual ought to help you out on setting this up. |
| 40 |
-- |
| 41 |
Regards, |
| 42 |
Mick |
Archives