Priority: P3 (important, not urgent). A gateway whose DSL line is up is still reported as having its uplink down, and netOrk's reachability takes that as evidence that the site is isolated.
get_wan_status builds its answer from getBasicInformation (WanIp, WanAccessType, SystemUpTime, MaxUpstream, MaxDownstream). A VMG4005-B50A (V5.17(ABQA.3.1)C0) sends none of these there, so every call returns is_connected: false, link_status: "Down", external_ip: "" and zeros for uptime and both bitrates, whatever the line does.
What netOrk does with it: the poll stores it as Device.wan_status_snapshot. The dashboard's WAN uplinks read it, and reachability adds an ISOLATED / wan_down evidence item for every gateway with is_connected: false.
The gateway has the line state in cardpage_status, which the driver already reads (#23, #28):
WanLanInfo[] entries with X_ZYXEL_Type: "WAN": Status, X_ZYXEL_SrvName, IPv4Address[]
In bridge mode the gateway has no WAN address of its own, so "connected" has to mean the DSL line is in sync, not that there is an external IP.
Same cause in get_nat_translations: inside_global is built from WanIp and comes out as ":<port>".
Priority: P3 (important, not urgent). A gateway whose DSL line is up is still reported as having its uplink down, and netOrk's reachability takes that as evidence that the site is isolated.
`get_wan_status` builds its answer from `getBasicInformation` (`WanIp`, `WanAccessType`, `SystemUpTime`, `MaxUpstream`, `MaxDownstream`). A VMG4005-B50A (V5.17(ABQA.3.1)C0) sends none of these there, so every call returns `is_connected: false`, `link_status: "Down"`, `external_ip: ""` and zeros for uptime and both bitrates, whatever the line does.
What netOrk does with it: the poll stores it as `Device.wan_status_snapshot`. The dashboard's WAN uplinks read it, and reachability adds an `ISOLATED` / `wan_down` evidence item for every gateway with `is_connected: false`.
The gateway has the line state in `cardpage_status`, which the driver already reads (#23, #28):
- `DslChannelInfo[]`: `Status`, `UpstreamCurrRate`, `DownstreamCurrRate`, `DSLUpTime`, `LinkEncapsulationUsed`
- `WanLanInfo[]` entries with `X_ZYXEL_Type: "WAN"`: `Status`, `X_ZYXEL_SrvName`, `IPv4Address[]`
In bridge mode the gateway has no WAN address of its own, so "connected" has to mean the DSL line is in sync, not that there is an external IP.
Same cause in `get_nat_translations`: `inside_global` is built from `WanIp` and comes out as `":<port>"`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Priority: P3 (important, not urgent). A gateway whose DSL line is up is still reported as having its uplink down, and netOrk's reachability takes that as evidence that the site is isolated.
get_wan_statusbuilds its answer fromgetBasicInformation(WanIp,WanAccessType,SystemUpTime,MaxUpstream,MaxDownstream). A VMG4005-B50A (V5.17(ABQA.3.1)C0) sends none of these there, so every call returnsis_connected: false,link_status: "Down",external_ip: ""and zeros for uptime and both bitrates, whatever the line does.What netOrk does with it: the poll stores it as
Device.wan_status_snapshot. The dashboard's WAN uplinks read it, and reachability adds anISOLATED/wan_downevidence item for every gateway withis_connected: false.The gateway has the line state in
cardpage_status, which the driver already reads (#23, #28):DslChannelInfo[]:Status,UpstreamCurrRate,DownstreamCurrRate,DSLUpTime,LinkEncapsulationUsedWanLanInfo[]entries withX_ZYXEL_Type: "WAN":Status,X_ZYXEL_SrvName,IPv4Address[]In bridge mode the gateway has no WAN address of its own, so "connected" has to mean the DSL line is in sync, not that there is an external IP.
Same cause in
get_nat_translations:inside_globalis built fromWanIpand comes out as":<port>".