Of subnets and configs

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Of subnets and configs

antoniosk

2382 posts

Uber Geek
+1 received by user: 742

ID Verified

Trusted

Lifetime subscriber

#208430 11-Feb-2017 17:37

I'm on Voda cable using the new technicolor 4400 modem. Have ditched using the supplied HG659 for an alternative (Synology) which looks impressive, but one thing I've not been able to resolve is pinging the technicolor to see what the stats are for the cable config.

I used to be able to do this with the Motorola/Cisco modems via my Apple routers - the address is 192.168.100.1 for the cable modem.

192.168.100.1 is pingable - I was able to see it from another router I briefly used - but I get no such joy from the current config.

Default gateway is 192.168.1.1. DHCP Server in router is using the range 192.168.1.2 - 192.168.1.99. Subnet is 255.255.255.0

So how can I ping 192.168.100.1?

________

Antoniosk

yitz

2238 posts

Uber Geek
+1 received by user: 594

#1718708 11-Feb-2017 17:46

Traffic (port 80 http) could be firewalled off on the relevant interface.

RossT

9 posts

Wannabe Geek

#1719260 13-Feb-2017 10:35

I was under the impression that ping doesn't use a specific port. (?)

Maybe the router is set to block/disallow ICMP/ping in the firewall.

My first thought would be to check the firewall rules or turn off the routers firewall temporarily to try the ping.

PolicyGuy

1820 posts

Uber Geek
+1 received by user: 1769

ID Verified

Lifetime subscriber

#1719272 13-Feb-2017 11:00

Maybe because the new router put the internal traffic on the 192.168.1.x network, not the 192.168.100.x network?
If your default gateway is 192.168.1.1, well then that's the router's address on "your" side.

192.168.x.y are 'Private' address ranges (255 subnets each with mask 255.255.255.0), so you shouldn't actually be able to ping 192.168.100.1 from 192.168.1.x unless there's a specific routing for that in your router. Probably your old router assigned addresses in 192.168.100.x, but the new one uses 192.168.1.x.

yitz

2238 posts

Uber Geek
+1 received by user: 594

#1719280 13-Feb-2017 11:18

I think cable modems (in general) do something fancy, maybe they intercept DHCP to add a route to 192.168.100.x in the response for the router or something like that.

Some routers might not accept those routes for security reasons (?) so you may need to add a static route for 192.168.100.1 going out the WAN interface.

Then you should at least be able to ping it, and (depending on firewall/access control) the cable modem management web interface through a browser.

solutionz

589 posts

Ultimate Geek
+1 received by user: 164
Inactive user

#1719302 13-Feb-2017 11:40

Set your DHCP subnet to 255.255.0.0 and your 192.168.x.x devices will be able to communicate with one another.