Re: [ilugd] Private IP in Public Network

2012-10-10 Thread Naresh Narang
On Wed, Oct 10, 2012 at 10:45 AM, Naresh Narang nknar...@yahoo.com wrote: On Tue, Oct 9, 2012 at 3:00 PM, Naresh Narang nknar...@yahoo.com wrote: 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. I doubt

Re: [ilugd] Private IP in Public Network

2012-10-10 Thread Arun Khan
On Wed, Oct 10, 2012 at 1:29 PM, Naresh Narang wrote: On Wed, Oct 10, 2012 at 10:45 AM, Naresh Narang wrote: On Tue, Oct 9, 2012 at 3:00 PM, Naresh Narang wrote: 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

Re: [ilugd] Private IP in Public Network

2012-10-10 Thread Naresh Narang
OK, please start a campaign to educate the millions of users who have net access across the globe. Alternately, or mandate the vendors of such devices to put such rules by default into their devices. Also, as a side note, yes I have seen some ISPs exposing their private networks to external,

[ilugd] Private IP in Public Network

2012-10-09 Thread Nirmalya Lahiri
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

Re: [ilugd] Private IP in Public Network

2012-10-09 Thread Raj Mathur (राज माथुर)
On Tuesday 09 Oct 2012, 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

Re: [ilugd] Private IP in Public Network

2012-10-09 Thread Amit Patkar | ATPL
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

Re: [ilugd] Private IP in Public Network

2012-10-09 Thread Naresh Narang
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

Re: [ilugd] Private IP in Public Network

2012-10-09 Thread Arun Khan
On Tue, Oct 9, 2012 at 1:27 PM, Nirmalya Lahiri nirmalyalah...@yahoo.com wrote: 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

Re: [ilugd] Private IP in Public Network

2012-10-09 Thread Arun Khan
On Tue, Oct 9, 2012 at 3:00 PM, Naresh Narang nknar...@yahoo.com wrote: 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. I doubt very much that ISP is advertising Private IP routes to the public. -- Arun

Re: [ilugd] Private IP in Public Network

2012-10-09 Thread Naresh Narang
On Tue, Oct 9, 2012 at 3:00 PM, Naresh Narang nknar...@yahoo.com wrote: 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. I doubt very much that ISP is advertising Private IP routes to the public.

Re: [ilugd] Private IP in Public Network

2012-10-09 Thread Arun Khan
On Wed, Oct 10, 2012 at 10:45 AM, Naresh Narang nknar...@yahoo.com wrote: On Tue, Oct 9, 2012 at 3:00 PM, Naresh Narang nknar...@yahoo.com wrote: 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. I doubt