On Sunday 13 January 2008, Hans-Werner Hilse wrote: > Hi, > > On Sun, 13 Jan 2008 16:42:56 +0530 > > Holla <[EMAIL PROTECTED]> wrote: > > One thing, I cannot understand is the difference in traceroute > > results. What does this say in plain english ? :-) > > > > At PC2 > > # traceroute 218.248.240.46 (ISP's DNS server) > > traceroute to 218.248.240.46 (218.248.240.46), 30 hops max, 40 byte > > packets 1 192.168.2.43 (192.168.2.43) 1.730 ms 0.840 ms 0.920 ms > > 2 192.168.1.1 (192.168.1.1) 1.440 ms 1.469 ms 1.287 ms > > 3 * * * > > 4 * * * > > > > At PC1 > > > > # traceroute 218.248.240.46 > > traceroute to 218.248.240.46 (218.248.240.46), 30 hops max, 40 byte > > packets 1 192.168.1.1 (192.168.1.1) 0.848 ms 0.706 ms 0.681 ms > > 2 117.192.128.1 (117.192.128.1) 19.712 ms 18.878 ms 19.920 ms > > 3 218.248.160.134 (218.248.160.134) 19.292 ms 19.796 ms 19.190 ms > > I'd say your router (Router1) isn't doing NAT for packets from other > subnets than it's LAN interface is configured for -- regardless of the > (correctly) configured internal additional route. > > So your option would be to set up PC1 for doing NAT, not necessarily > for packets 192.168.2/24<->192.168.1/24, but for all packets from > 192.168.2/24 going to the internet. > > Your provider most likely does not have anything to do with all this.
I agree that this is not related to the ISP. What you probably need to do is set up RIP2 in your router 1, to be able to recognise other subdomains (192.168.2.XXX). Then it'll process packets coming from that subdomain. The router manual ought to help you out on setting this up. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
