I have my ClearOS setup with a 2 MIC basic solution where enps38 is LAN & enp3s10 is WAN.
Now for years with cable DOCSIS 3.0 modems (even different brands), any LAN client could access the modem at 192.168.100.1 and check it's health.
I have since upgraded to a DOCSIS 3.1 Modem, an SB8200, which also uses 192.168.100.1.
Yet for some strange reason, either ClearOS or the router is blocking LAN clients from accessing the page.
Strangely even if I type in "telnet 192.168.100.1 80" on the ClearOS even that fails. The ClearOS & LAN clients can ping the modem.
I was reading that this is a very common issue with SB8200/S33 modems and some recommend forwarding any 192.168.100.1 and/or adding a second LAN IP in the 192.168.100.0/24 subnet.
So far, the only way I have been able to ever access the modem interface was oddly putting a patch cable from the modems second Ethernet & plugging it in to the LAN switch but I think that causes issues over time.
Now for years with cable DOCSIS 3.0 modems (even different brands), any LAN client could access the modem at 192.168.100.1 and check it's health.
I have since upgraded to a DOCSIS 3.1 Modem, an SB8200, which also uses 192.168.100.1.
Yet for some strange reason, either ClearOS or the router is blocking LAN clients from accessing the page.
Strangely even if I type in "telnet 192.168.100.1 80" on the ClearOS even that fails. The ClearOS & LAN clients can ping the modem.
I was reading that this is a very common issue with SB8200/S33 modems and some recommend forwarding any 192.168.100.1 and/or adding a second LAN IP in the 192.168.100.0/24 subnet.
So far, the only way I have been able to ever access the modem interface was oddly putting a patch cable from the modems second Ethernet & plugging it in to the LAN switch but I think that causes issues over time.
Share this post:
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »