USG60W GUI Routing Traces cause system reboot
danyedinak
Posts: 51 Ally Member
There are two different scenarios that result in system reboots when using the Routing Traces function : WAN, and LAN.
To reproduce the LAN side issue :
To reproduce the WAN side issue:
Note that this WAN side (host) problem does NOT happen if the host IP address is on an internal interface (lan1, lan2). Can reproduce IFF destination host is on an external WAN interface. Does not have to be a public IP - can reproduce in a lab environment by tracing to a valid private IP on the wan side.
IFF the interval is set to 105 seconds or lower, the system capture completes successfully and the system does not reboot.
To reproduce the LAN side issue :
- USG60W running firmware 4.35(AAKZ.0C0) or 4.38(AAKZ.0) with factory default configuration.
- WAN IP set to DHCP or Static IP.
- Maintenance | Diagnostics | Routing Traces
- Select "Source" radio button
- Enter source IP of the router's LAN IP address (192.168.1.1)
- Enter the Destination IP of a device on LAN1
- Click Capture
- Device reboots immediately.
To reproduce the WAN side issue:
- USG60W running firmware 4.35(AAKZ.0C0) or 4.38(AAKZ.0) with factory default configuration.
- WAN IP set to DHCP or Static IP.
- Maintenance | Diagnostics | Routing Traces
- Select "Host" radio button
- Enter Host IP of device on the WAN side of the device
- Set Protocol to any
- Set Interval to any number from 106 to 120 seconds
- Click Capture
- The system will become unresponsive and reboot between 20 and 50 seconds later. At 120 seconds, the reboot is almost instantaneous.
Note that this WAN side (host) problem does NOT happen if the host IP address is on an internal interface (lan1, lan2). Can reproduce IFF destination host is on an external WAN interface. Does not have to be a public IP - can reproduce in a lab environment by tracing to a valid private IP on the wan side.
IFF the interval is set to 105 seconds or lower, the system capture completes successfully and the system does not reboot.
0
All Replies
-
@ danyedinak
Regarding to this case,
after follow the steps you mentioned, the device worked stable. Here is my setting.
Lan IP
Wan IP
Therefore, can you private message the configuration and diagnostic information for check further?
0
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 146 Nebula Ideas
- 96 Nebula Status and Incidents
- 5.7K Security
- 262 USG FLEX H Series
- 271 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 40 Wireless Ideas
- 6.4K Consumer Product
- 249 Service & License
- 387 News and Release
- 84 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.5K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 73 Security Highlight