1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice

Welcome To SNBForums

SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.

If you'd like to post a question, simply register and have at it!

While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!

PPPOE dropping and not reconnecting

Discussion in 'Asuswrt-Merlin' started by criminala, May 20, 2019.

  1. criminala

    criminala Occasional Visitor

    Joined:
    May 14, 2015
    Messages:
    14
    Ever since i upgraded to the 384.11 build i'm facing issues with PPPOE connection dropping . I started using PPPOE since that version , before i used a double NAT setup .
    Updated recently to 384.11_2 , but issues persist .

    The issue is that PPPOE (WAN) gets disconnected , but never reconnects . This happens at least every day on random times .
    I need to go in the admin page to WAN settings , press on apply (without changing any settings) , and only then my PPPOE and WAN come back online .

    I am using an AC68U and the modem is an external one (technicolor bbox3) .
     
  2. criminala

    criminala Occasional Visitor

    Joined:
    May 14, 2015
    Messages:
    14
    The log when a disconnection happens (i censored some data for privacy , if i forgot something let me know) :

    Code:
    May 19 07:45:06 avahi-daemon[272]: Files changed, reloading.
    May 19 07:45:06 avahi-daemon[272]: Loading service file /tmp/avahi/services/mt-daap.service.
    May 19 07:45:06 iTunes: daemon is stopped
    May 19 07:45:06 FTP_Server: daemon is stopped
    May 19 07:45:07 Samba_Server: smb daemon is stopped
    May 19 07:45:07 kernel: gro disabled
    May 19 07:45:07 dropbear[199]: Early exit: Terminated by signal
    May 19 07:45:07 dnsmasq[236]: exiting on receipt of SIGTERM
    May 19 07:45:07 avahi-daemon[272]: Got SIGTERM, quitting.
    May 19 07:45:07 avahi-daemon[272]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.10.1.
    May 19 07:45:07 avahi-daemon[272]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.1.1.
    May 19 07:45:07 avahi-daemon[272]: avahi-daemon 0.7 exiting.
    May 19 07:45:08 pppd[21643]: Hangup (SIGHUP)
    May 19 07:45:08 pppd[21643]: Terminating on signal 15
    May 19 07:45:08 pppd[21643]: Connect time 589.2 minutes.
    May 19 07:45:08 pppd[21643]: Sent 592665244 bytes, received 3116387000 bytes.
    May 19 07:45:08 lldpd[298]: removal request for address of 213.yyyyyyy.16%22, but no knowledge of it
    May 19 07:45:08 ovpn-client1[24932]: write UDP: Network is unreachable (code=101)
    May 19 07:45:08 pppd[21643]: Connection terminated.
    May 19 07:45:08 pppd[21643]: Sent PADT
    May 19 07:45:09 pppd[21643]: Exit.
    May 19 07:45:09 kernel: Attempt to kill tasklet from interrupt
    May 19 07:45:09 kernel: et0: et_mvlan_netdev_event: event 9 for vlan1 mvlan_en 0
    May 19 07:45:09 kernel: device eth0 left promiscuous mode
    May 19 07:45:09 kernel: br0: port 1(vlan1) entering forwarding state
    May 19 07:45:09 kernel: et0: et_mvlan_netdev_event: event 2 for vlan1 mvlan_en 0
    May 19 07:45:09 kernel: et0: et_mvlan_netdev_event: event 9 for vlan2 mvlan_en 0
    May 19 07:45:09 kernel: et0: et_mvlan_netdev_event: event 2 for vlan2 mvlan_en 0
    May 19 07:45:09 kernel: et0: et_mvlan_netdev_event: event 13 for vlan1 mvlan_en 0
    May 19 07:45:09 kernel: device eth0 entered promiscuous mode
    May 19 07:45:09 kernel: br0: topology change detected, propagating
    May 19 07:45:09 kernel: br0: port 1(vlan1) entering forwarding state
    May 19 07:45:09 kernel: br0: port 1(vlan1) entering forwarding state
    May 19 07:45:09 kernel: et0: et_mvlan_netdev_event: event 1 for vlan1 mvlan_en 0
    May 19 07:45:09 kernel: et0: et_mvlan_netdev_event: event 13 for vlan2 mvlan_en 0
    May 19 07:45:09 kernel: et0: et_mvlan_netdev_event: event 1 for vlan2 mvlan_en 0
    May 19 07:45:09 lldpd[298]: removal request for address of 169.yyyyyyy.102%4, but no knowledge of it
    May 19 07:45:09 ovpn-client1[24932]: write UDP: Network is unreachable (code=101)
    May 19 07:45:12 ovpn-client1[24932]: write UDP: Network is unreachable (code=101)
    May 19 07:45:13 ovpn-client1[24932]: write UDP: Network is unreachable (code=101)
    May 19 07:45:13 ovpn-client1[24932]: event_wait : Interrupted system call (code=4)
    May 19 07:45:13 ovpn-client1[24932]: SIGTERM received, sending exit notification to peer
    May 19 07:45:13 ovpn-client1[24932]: write UDP: Network is unreachable (code=101)
    May 19 07:45:13 ovpn-client1[24932]: write UDP: Network is unreachable (code=101)
    May 19 07:45:14 ovpn-client1[24932]: vpnrouting.sh tun11 1500 1585 10.8.8.4 255.255.255.0 init
    May 19 07:45:15 openvpn-routing: Configuring policy rules for client 1
    May 19 07:45:15 openvpn-routing: Tunnel down - VPN client access blocked
    May 19 07:45:15 ovpn-client1[24932]: Closing TUN/TAP interface
    May 19 07:45:15 ovpn-client1[24932]: /usr/sbin/ip addr del dev tun11 10.8.8.4/24
    May 19 07:45:15 lldpd[298]: removal request for address of 10.8.8.4%27, but no knowledge of it
    May 19 07:45:15 ovpn-client1[24932]: updown.sh tun11 1500 1585 10.8.8.4 255.255.255.0 init
    May 19 07:45:16 rc_service: service 2810:notify_rc updateresolv
    May 19 07:45:16 rc_service: waitting "restart_net_and_phy" via  ...
    May 19 07:45:19 WAN_Connection: Fail to connect with some issues.
    May 19 07:45:20 nat: apply redirect rules
    May 19 07:45:24 nat: apply nat rules (/tmp/nat_rules_ppp0_eth0)
    
     
  3. Martineau

    Martineau Part of the Furniture

    Joined:
    Jul 8, 2012
    Messages:
    2,299
    Location:
    UK
    Not sure why your PPPoE WAN connection was terminated after nearly 10 hours, but it does seem that the watchdog did attempt to restart the WAN ("restart_net_and_phy") and may have timed out?

    However, perhaps my ChkWAN script can be used to monitor the WAN connection and will attempt the WAN restart(s) when appropriate, and assuming you have 'Start with WAN' for VPN Client 1, this should pre-empt the need for your manual GUI intervention.
     
  4. criminala

    criminala Occasional Visitor

    Joined:
    May 14, 2015
    Messages:
    14
    My first thought is that merlin wrt should be able to handle it on it's own , without the use of external scripts . :)

    What i've done in the meantime is changed dns servers from cleanbrowsing to quad9 , this got me a much more stable connection .
    Then i also changed wan detection from DNS probe to PPP echo (again) , and changed the value to 10 for PPP Echo Interval and 2 for Max failures . (the default values that i used before didn't seem to work well for me)

    In the past few days , not had a disconnection anymore . So let's see in the coming days , and also let's see if the connection reconnects when necessary .
     
    Last edited: May 23, 2019
    maxbraketorque likes this.