Topics

Hi all,

After 24.7.12 upgrade, it looks like the ET Pro Telemetry widget shows either empty box or "failed to load widget".

From the CLI, sensor_info.py *sometimes* works, and when it works it takes several seconds to complete, though it reports the sensor is still ACTIVE, while other times the script failed with exception stating remote end closed connection, like below:

--------
  File "/usr/local/lib/python3.11/http/client.py", line 294, in _read_status
    raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response
--------

Anyone also seeing this?

Thanks a lot.

Hi all,

Have been seeing this after upgraded to 20.7, it happens to my wan ipv6 99.9% of time after reboot

Symptom: WAN does not get ipv6 address, LAN (tracking ipv6 of WAN) seems to get a ipv6 address from ISP's delegated prefix (which I know by looking at GUI interface overview page), however LAN does not publish the prefix in router advertisement (which I know from Wireshark capturing on a host connected to lan)

Weird thing is it almost look like there being some timing issue or race condition at boot to amplify the underlying problem, on the other hand it has higher chance to work if I disconnect WAN side PPPoE, wait couple of seconds then redial when the system is in a rather inactive state. Meaning WAN gets ipv6 assigned from ISP, LAN gets prefix and advertising as expected.

Currently I worked around by just requesting prefix, this gives me more reliable ipv6 after boot without manual intervention.

Btw, for anyone interested my ISP gives out an address via DHCPv6 (Which is via ipv4 PPPoE) and a /64 prefix (different from the DHCPv6 address is under) it had worked until 20.7.

Anyone seeing the same?

Thanks and cheers,
Ivan