Thread: Superhub Modem Mode - Can no longer detect WAN IP
View Single Post
Old 09-10-2013, 14:17   #9
qasdfdsaq
cf.mega poster
 
Join Date: Aug 2004
Posts: 11,207
qasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronze
qasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronzeqasdfdsaq is cast in bronze
Re: Modem Mode - Can no longer detect WAN IP
Quote:
Originally Posted by ferretuk View Post
The power up sequence is not relevant to the OP's issue... Turning the router on after the modem will speed reconnection up as its first DHCP request will be replied to and it won't have to back off and try again after a timeout...
The first DHCP request should always be replied to, because the modem replies with its own DHCP response if the DOCSIS connection is not yet up. The router will be given a temporary local IP (192.168.100.x) with a short lease of 30 or 60 seconds giving it access to the modem's status page at 192.168.100.1 until the WAN is up properly (if it ever comes up).

This is standard on most, if not all DOCSIS modems, including the Superhub in modem mode. Hence, with a working modem and router, regardless of WAN/DOCSIS/Internet connection state you should never end up without a DHCP assigned address of some sort.

If it does, that would suggest some sort of connectivity issue between the router and the modem (Superhub) or a fault with one or the other.
qasdfdsaq is offline   Reply With Quote