Does anyone encounter this unpleasant issue?
WAN gets disconnected after these events:
- turning on the router;
- changing some LAN related settings.
My ISP provides DHCP to the clients, so the router should get the net automatically after turning on, but surprisingly it doesn't. More than that it loses the WAN after applying changes to LAN (not WAN!) settings. For instance if I change LAN\IPTV "Enable multicast routing (IGMP Proxy)", WAN disconnects. To get it again connected I have to go to the Network Map, click "Disconnected", and pass three Network Wizard steps (that means to press Next three times).
SystemLog:
RT-AC66U: 354.29.
WAN gets disconnected after these events:
- turning on the router;
- changing some LAN related settings.
My ISP provides DHCP to the clients, so the router should get the net automatically after turning on, but surprisingly it doesn't. More than that it loses the WAN after applying changes to LAN (not WAN!) settings. For instance if I change LAN\IPTV "Enable multicast routing (IGMP Proxy)", WAN disconnects. To get it again connected I have to go to the Network Map, click "Disconnected", and pass three Network Wizard steps (that means to press Next three times).
SystemLog:
And of course...
Jun 3 12:25:43 miniupnpd[612]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jun 3 12:25:43 miniupnpd[612]: Failed to get IP for interface eth0
Jun 3 12:25:43 miniupnpd[612]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
...
Maybe these lines can be useful...WAN Connection: ISP's DHCP did not function properly.
RT-AC66U: 354.29.
Last edited: