I doubt this is done on porpose MWEB?

fixx

Well-Known Member
Joined
Feb 13, 2006
Messages
288
Reaction score
7
Location
South Africa
I get replies from 192.168.0.1 over MWEB's uncapped ADSL. Is this their way to prevent the subnet from routing over the Internet rather than filtering it?

6 * * * Request timed out.
7 15 ms 13 ms 15 ms 196.22.169.134
8 14 ms 15 ms 15 ms 196.22.189.3
9 22 ms 22 ms 27 ms 196.22.169.70
10 22 ms 41 ms 23 ms 196.22.185.38
11 29 ms 22 ms 21 ms 192.168.0.1
 
Tracing route to 192.168.0.1 over a maximum of 30 hops

2 * * * Request timed out.
3 18 ms 18 ms 17 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 19 ms 20 ms 19 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 25 ms 24 ms 25 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.6.6]
6 24 ms 24 ms 27 ms 196.22.185.38
7 29 ms 27 ms 25 ms 192.168.0.1

Trace complete.
 
They've probably got a null route in the router for the bogon spaces. It's one way to keep it in the network.
 
I think Libby had a thread about this not too long ago.....
 
Top
Sign up to the MyBroadband newsletter
X