Open InternalLoss opened 4 years ago
I'd imagine some of the commands will return different responses when in modem mode. Perhaps, there needs to be a check for modem mode which I believe will potentially have it's own SNMP OID to query and then prevent certain methods being run when the Hub3 is in modem mode.
Looks like it's the dns_servers
method that throws the error for the info command. Either gracefully handling a no results response or prevent certain commands being run when in modem mode would be potential fixes.
There's a JSON endpoint (checkConnType) which returns this:
{
"conType": "LAN",
"gwWan": "f",
"remoteAddr": "192.168.100.2",
"lang": "English",
"provMode": "1",
"dsLite": "0",
"modemMode": "1",
"firstInstall": "1"
}
And potentially an SNMP OID request: http://192.168.100.1/snmpGet?oids=1.3.6.1.4.1.4491.2.1.14.1.5.4.0 which returns "1" when on the modem mode page when logged in, potentially this is the OID for modem mode?
Now I'm in Modem Mode on my VM Router, im not too surprised there's a small bug:
I'm going to presume this is likely due to me being in Modem Mode c: