WAN Disconnection , any idea what cause this.

[Pauluk]

Hey all

Lost our FTTP service this morning, red light on my asus rt-ax86u but green lights on our ONT box. Heres the part of the log when it went down, any ideas what it could be? Not sure if this shows enough info, didnt want to share too much secure info.
Thanks


Jul 26 08:04:09 wlceventd: wlceventd_proc_event(511): eth6: Disassoc 70:EE:##0:837:12, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jul 26 08:04:10 WAN Connection: Fail to connect with some issues.
Jul 26 08:07:30 rc_service: wanduck 1391:notify_rc restart_wan_if 0
Jul 26 08:07:30 pppd[2382]: Connection terminated.
Jul 26 08:07:30 odhcp6c[2988]: Failed to send DHCPV6 message to ff02::1:2 (Network is unreachable)
Jul 26 08:07:30 rc_service: dhcp6c 19246:notify_rc restart_ddns
Jul 26 08:07:30 rc_service: waitting "restart_wan_if 0" via wanduck ...
Jul 26 08:07:30 wlceventd: wlceventd_proc_event(511): eth7: Disassoc B0:E4:##:AB:E1:C5, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jul 26 08:07:30 wlceventd: wlceventd_proc_event(511): eth7: Disassoc B0:E4:##:AB:E1:C5, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jul 26 08:07:32 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_inet6addr_event,148: Could not rdpa_system_ipv6_host_address_table_find ret=-5^[[0m
Jul 26 08:07:32 dnsmasq[1475]: failed to create listening socket for ::1: Address already in use
Jul 26 08:07:32 dnsmasq[1475]: interface br0 failed to join DHCPv6 multicast group: Address already in use

 

[ColinTaylor]

The initial problem was with your ISP. It's difficult to speculate why the Asus didn't later recover without seeing more of the log.

You don't say what firmware version you're using but the Asus firmware has lots of "issues" with IPv6 support so it's not particularly surprising that it didn't recover properly.

 

[Pauluk]

ok thanks Colin, yes ISP said it was a DNS problem which was very unusual (i`ve only been with them a week!)

its the stock 3.0.0.4.386_49599 firmware. I`m also realising my 4g usb stick as failover failed to work aswell so thats another issue.