ISP is utterly stupid. You're receiving routes for 192.168.2 and may be others. You must null route all 1918 addresses on edge router.
--Naresh Sent from my iPhone On Oct 9, 2012, at 5:28 PM, Amit Patkar | ATPL <a...@avhan.com> wrote: > Hi, > > This is not at all problem with your end or TATA Communication. Since you are > using IP range of 192.168.7.1-192.168.7.253, your subnet mask is 255.255.255.0 > This means, any IP outside your range will be forwarded to your router > (192.168.7.51). Now since router is configured to pass traffic on > 115.115.147.137, this request is sent on public network. THis is normal. > Now this will continue till IP 192.168.2.10 is reached. Every G/W in path > will try to reach this IP and keeps forwarding requests to subsequent G/W of > the router / L3 switch. > > There are guidelines to define IP addresses. Where as it all depends on > routes defined in router. TATA Communication has very little control on this. > It is problem with last mile router. Their route configuration seems to be > incorrect. > > On the other hand, if you want to drop such traffic, you should configure > appropriate Deny rule in your router. > > Thanks & Regards, > Amit Patkar > > On 10/9/2012 1:27 PM, Nirmalya Lahiri wrote: >> Hi everyone, >> today I have discover a critical network infrastructure which is almost >> impossible. I believe very few people have seen this before. >> >> The story is .... in my office we have leased internet connection with >> static IP from TATA Communication Ltd. In my local network I have configured >> network ip (192.168.7.0). So all the PC in my local network has the IP of >> the range 192.168.7.1 to 192.168.7.253. >> >> For a experimental purpose yesterday I have ping to 192.168.2.10... It >> should not return reply. But unfortunately I got reply from a host. After >> investigation I have found that the host is outside of my local network. >> Please look into the tracepath report from my local PC to that unknown host. >> >> nirmalya@nirmalya-desktop:~$ tracepath 192.168.2.10 >> 1: nirmalya-desktop.local (192.168.7.103) 0.141ms pmtu 1500 >> 1: 192.168.7.51 (192.168.7.51) 0.706ms >> 1: 192.168.7.51 (192.168.7.51) 0.700ms >> 2: 115.115.147.137 (115.115.147.137) 150.228ms >> 3: 121.240.2.54 (121.240.2.54) 188.099ms asymm 6 >> 4: 121.240.2.57 (121.240.2.57) 175.322ms asymm 6 >> 5: 172.25.81.133 (172.25.81.133) 176.625ms asymm 6 >> 6: 172.29.253.34 (172.29.253.34) 208.708ms asymm 8 >> 7: 172.31.16.193 (172.31.16.193) 186.462ms asymm 8 >> 8: 172.31.35.138 (172.31.35.138) 206.554ms asymm 10 >> 9: 172.31.8.134 (172.31.8.134) 226.454ms asymm 10 >> 10: 172.25.82.62 (172.25.82.62) 206.389ms asymm 9 >> 11: 192.168.2.10 (192.168.2.10) 217.967ms reached >> Resume: pmtu 1500 hops 11 back 247 >> >> >> In this report 192.168.7.103 is my personal PC, 192.168.7.51 is internal IP >> of router, 115.115.147.137 is gateway IP of our leased internet connection. >> >> I have already reported it to TATA Communication Ltd. They give us >> commitment to solve it by 24hour. >> >> Have anyone see this before? >> --- >> [Nirmalya Lahiri] >> + - [+91-9433113536] >> _______________________________________________ >> Ilugd mailing list >> Ilugd@lists.linux-delhi.org >> http://frodo.hserus.net/mailman/listinfo/ilugd > > > _______________________________________________ > Ilugd mailing list > Ilugd@lists.linux-delhi.org > http://frodo.hserus.net/mailman/listinfo/ilugd _______________________________________________ Ilugd mailing list Ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd
