dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
861
share rss forum feed

Zero3K

join:2009-06-13
Louisville, KY

[Connectivity] Cable Modem Pages

I am able to access other's cable modem pages (such as one on 10.0.1.1). Why is that and is there any way to prevent it?


brown1481

join:2011-02-17
Lewis Center, OH
said by Zero3K:

I am able to access other's cable modem pages (such as one on 10.0.1.1). Why is that and is there any way to prevent it?

That is a private IP address and isn't routable. If you are able to log in that means it is a device on your local network. Similar to the 192.168.x.x addresses.

Mystic95Z

join:2005-05-10
Sellersburg, IN
said by brown1481:

said by Zero3K:

I am able to access other's cable modem pages (such as one on 10.0.1.1). Why is that and is there any way to prevent it?

That is a private IP address and isn't routable. If you are able to log in that means it is a device on your local network. Similar to the 192.168.x.x addresses.

You are correct that it is a private IP, but I just put that IP in my browser and got someone else's cable modem, its not mine as I run a 192.168.x.x network. I get the following when I run a tracert on that address.

tracert 10.0.1.1

Tracing route to 10.0.1.1 over a maximum of 30 hops

1 1 ms 1 ms 1 ms unknown [192.168.1.1]
2 * * * Request timed out.
3 12 ms 12 ms 13 ms 74-128-45-65.dhcp.insightbb.com [74.128.45.65]
4 10 ms 11 ms 13 ms 74.128.9.225
5 20 ms 15 ms 15 ms 74.128.8.158
6 27 ms 31 ms 23 ms network-065-029-001-033.midwest.rr.com [65.29.1.33]
7 26 ms 25 ms 23 ms tge2-4.clvhoh1-rtr1.neo.rr.com [24.164.117.129]

8 25 ms 27 ms 27 ms tge2-4.lyndoh1-rtr1.neo.rr.com [24.164.115.168]

9 28 ms 25 ms 25 ms tge1-3.mntroh1-swt402.neo.rr.com [24.164.115.166]
10 27 ms 25 ms 28 ms tge1-50.mntroh1-swt401.neo.rr.com [24.164.118.66]
11 33 ms 37 ms 57 ms gig18-0.mntroh1-ar41.neo.rr.com [24.164.118.2]
12 34 ms 49 ms 40 ms 10.0.1.1

Trace complete.

Zero3K

join:2009-06-13
Louisville, KY
said by Mystic95Z See Profile
You are correct that it is a private IP, but I just put that IP in my browser and got someone else's cable modem, its not mine as I run a 192.168.x.x network. I get the following when I run a tracert on that address.

tracert 10.0.1.1

Tracing route to 10.0.1.1 over a maximum of 30 hops

1

2 * * * Request timed out.
3 12 ms 12 ms 13 ms 74-128-45-65.dhcp.insightbb.com [74.128.45.65]
4 10 ms 11 ms 13 ms 74.128.9.225
5 20 ms 15 ms 15 ms 74.128.8.158
6 27 ms 31 ms 23 ms network-065-029-001-033.midwest.rr.com [65.29.1.33]
7 26 ms 25 ms 23 ms tge2-4.clvhoh1-rtr1.neo.rr.com [24.164.117.129]

8 25 ms 27 ms 27 ms tge2-4.lyndoh1-rtr1.neo.rr.com [24.164.115.168]

9 28 ms 25 ms 25 ms tge1-3.mntroh1-swt402.neo.rr.com [24.164.115.166]
10 27 ms 25 ms 28 ms tge1-50.mntroh1-swt401.neo.rr.com [24.164.118.66]
11 33 ms 37 ms 57 ms gig18-0.mntroh1-ar41.neo.rr.com [24.164.118.2]
12 34 ms 49 ms 40 ms 10.0.1.1

Trace complete.

That is what is also happening to me if my router's IP is different than the one I mentioned in the first post.


HFCNUT82

join:2007-12-13
reply to Zero3K
The IP you mentioned is actually the IP used by the service provider's side of the cable modem. The 10.0.0.0/8 scopes are normally used by all Cable providers due to the extreme range of IPs available in the subnet. That 10. IP is used when the modem comes online after identifying the RF parameters needed to communicate with the CMTS. The IP allows layer 3 connectivity in order to obtain the TFTP package used to define your speed package and other DOCSIS parameters.

The 95% of modems I have came in contact also have another IP put in place by the manufacturer that uses an IP from the 192.168.0.0/16 scope. 9 out of 10 times this IP is in the 192.168.100.0/24 scope. This allows you to view the internal diagnostics of the modem but some firmwares have features blocked and require additional passwords. (Arris is big on this method)

As far as accessing other devices, yes it is possible since the 10. IPs are technically private ips being used on one big LAN relatively speaking. The only way prevent this would have to be put in place by the actual modem manufacturer. Reason why is that if the service provider attempted to do this, it would be an ACL (Access control list) NIGHTMARE. Pus, the firmware would be able to identify WAN and LAN access to the device.