@Vincent-TP 

 

Hi Vincent,

Thank you for the update regarding the firmware status. Given the critical nature of this device in a business environment, I have performed a forensic analysis of the instability to assist your engineering team in accelerating the fix. Please find the technical details below:

1. Data Plane vs. Control Plane: The issue is not limited to the Web UI. The Data Plane (routing/forwarding) is severely affected. During the instability phase, I experience severe packet loss and throughput degradation, confirming that this is a system-wide memory exhaustion issue affecting the network stack and not merely an interface hang.

2. LAN Connectivity: Yes, the LAN IP remains pingable, but with significantly increased jitter and latency. This confirms the CPU is not fully locked, but the kernel is struggling with resource allocation, specifically in the buffer management for the IPoE/MAP-E stack.

3. Recurrence Pattern: The recurrence is deterministic and correlates directly with the DHCPv6 lease renewal cycle. By default, the system enters this degraded state every 24–48 hours, coinciding with the renewal period. I have implemented a workaround by increasing the lease time, which mitigates the frequency of the failure but does not solve the underlying memory leak in the Japanese firmware integration.

4. Management Mode: I am managing the router exclusively via its standalone web interface. There is no Omada Controller involved in the current topology.

Additional Technical Context: For the engineering team's awareness, this is a hardware unit labeled "UN" (Universal) running the "JP" (Japanese) firmware version. I suspect the memory management issues stem from the porting of the Japanese-specific protocol stack (MAP-E/IPoE) onto the universal hardware base.

I have maintained detailed logs of the memory utilization spikes and session states. I expect that the "next version" of the firmware you mentioned addresses this leak at the kernel level rather than just providing a cosmetic fix for the UI.

I look forward to receiving a concrete timeline for the release of the corrected firmware.

Regards,

  @Vincent-TP 

 

I am providing the diagnostic data (log-ER8411-2026-06-26.bin) extracted via the Omada administration panel. The device was purchased new on March 26, 2026. Below are the technical findings observed in the system logs:

1. System Storage Status

• The system diagnostic reports the root partition (/dev/root mounted at /rom) with 100% utilization, totaling 28,160 1K-blocks used of 28,160 available (0% free space).

2. Logs and Diagnostic Sections

• The native diagnostic sections (==========LAST STARTUP LOG========== and ==========KERNAL PANIC LOG==========) contain no data entries.

3. Network Logs and System Events

• The system logs display inconsistent timestamps, alternating between the current time (2026) and the date 2025-06-11.

• In the logs dated 2025-06-11, the following hardware initialization events are recorded:

  • The physical connection status of [SFP WAN/LAN3] was up.

  • The physical connection status of [SFP+ WAN/LAN2] was up.

  • The LAN(LAN) IP address/mask ... were changed to 192.168.0.1/255.255.255.0.

• The ipvsix process records cyclical lease timeout followed by renew successfully events with an approximate interval of 2 hours.

• The DHCP Server records rejected request events for local network devices.

I request an investigation into these logs and the storage utilization status of the equipment, given that the device has been in operation for only 3 months.



How can I attach files here ?