my netwrok config.

my comp, 192.168.1.2
gateway 192.168.1.1
and if fwd enabled on gateway

my net routing is :

192.168.1.2 <--> 192.168.1.1 <--> ISP Public address

here is my query : when i ping 10.0.0.1 ( non existent in my network ) my gateway at 192.168.1.1 should tell me host 10.0.0.1 not reachable. but the bsnl ( my isp's gateway ) is telling me that 10.0.0.1 is not reachable....

what am i doing wrong ? or is it a problem at the bsnl's end ?

ping and traceroute command outputs below




Pinging 10.0.0.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.0.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

tracert 10.0.0.1

Tracing route to 10.0.0.1 over a maximum of 30 hops

1 2 ms 1 ms 1 ms 192.168.1.1
2 55 ms * 49 ms 59.95.64.1
3 166 ms 80 ms 149 ms 218.248.255.18
4 78 ms 83 ms 84 ms 218.248.255.18
5 59.162.0.178.static.vsnl.net.in [59.162.0.178] reports: Destination host unreachable.

Trace complete.

Hey Nobody,

I don't think, there is any issue at all. If your Gateway (192.168.1.1) see any IP outside its Net range (192.168.1.0), it will simply pass it to next gateway and so on, until the host is not found. This error (Host not found) will be thrown by the gateway, which has direct access to that network range.

I may be wrong, but this is my understanding of gateways. Correct me, if I am wrong.

Can you also paste output of,

ifconfig or ipconfig /all ?

I'll suggest you to put a few anti-spoofing rules in your gateway's firewall script first.
You know that 10.0.0.0/8, 172.16.0.0/16 and all those network-ids, reserved for local networks can't access your machine directly,, and if a packet is reaching the gateway with an IP belonging to these networks, someone is trying to do something nasty.

Actually, BSNL is using 10.0.0.0/8 network somewhere inside, and it's the problem of natting at their end.

this natting problem was hunted down by chetan a long time ago - i did not update this because it slipped out of my mind - since the gateway router uses a busybox linux - very common gateway linux distribution if anyone faces this problem again :

There is nothing wrong in your network settings in any way just that BSNL has not done their network correctly.

Today i restested everything again but i did not find this to be a problem - so i can say this has been resolved.