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 take forever to reconnect after reboot

Discussion in 'Asuswrt-Merlin' started by matge, Jun 1, 2020.

  1. matge

    matge New Around Here

    Joined:
    May 31, 2020
    Messages:
    3
    Hi!
    I am with Bell Fibe business plan and I've put the Sagecom 2000 in bridge mode. So my Asus RT-AC68U with Merlin (latest version) connect to WAN through pppoe. I used all the default settings, entered my credentials and everything is up and running.

    When I apply a settings to the router that need a restart, however, reconnecting to WAN take forever. (OK! maybe 15 minutes.) Here's a log where we see router trying to reconnect with errors. To be honest, I don't really understand those errors.
    Code:
    01:Jun:2020    00:43:37    172.17.0.1    err     Timeout waiting for PADO packets
    01:Jun:2020    00:43:37    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:43:31    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:43:31    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(449): eth2: Assoc 00:07:A6:07:95:71, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:43:31    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(420): eth2: Auth 00:07:A6:07:95:71, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:42:46    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:42:44    172.17.0.1    info     nvram: consolidating space!
    01:Jun:2020    00:42:26    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:42:22    172.17.0.1    err     Timeout waiting for PADO packets
    01:Jun:2020    00:42:02    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:41:59    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(449): eth2: Assoc 00:07:A6:07:95:93, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:41:59    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(420): eth2: Auth 00:07:A6:07:95:93, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:41:11    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:41:07    172.17.0.1    err     Timeout waiting for PADO packets
    01:Jun:2020    00:40:36    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:40:33    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 60:23:A4:BC:4F:D2, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:40:33    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(420): eth1: Auth 60:23:A4:BC:4F:D2, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:40:11    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:40:08    172.17.0.1    notice     service 1494:notify_rc restart_letsencrypt
    01:Jun:2020    00:39:56    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:39:56    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(386): eth2: Deauth_ind 40:4E:36:D3:25:2B, status: 0, reason: Class 3 frame received from nonassociated station (7)
    01:Jun:2020    00:39:56    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(386): eth2: Deauth_ind 40:4E:36:D3:25:2B, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
    01:Jun:2020    00:39:52    172.17.0.1    err     Timeout waiting for PADO packets
    01:Jun:2020    00:38:41    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:38:37    172.17.0.1    err     Timeout waiting for PADO packets
    01:Jun:2020    00:37:31    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:37:31    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(449): eth2: Assoc D4:11:A3:EE:28:77, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:37:31    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(420): eth2: Auth D4:11:A3:EE:28:77, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:37:26    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:37:22    172.17.0.1    err     Timeout waiting for PADO packets
    01:Jun:2020    00:37:11    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:37:11    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(449): eth1: Assoc D4:53:83:D0:59:9B, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:37:11    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(420): eth1: Auth D4:53:83:D0:59:9B, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:36:31    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:36:26    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:36:22    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:36:20    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(449): eth2: Assoc 40:4E:36:D3:25:2B, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:36:20    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(420): eth2: Auth 40:4E:36:D3:25:2B, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:36:16    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:36:12    172.17.0.1    notice     apply redirect rules error!
    01:Jun:2020    00:36:09    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(449): eth2: Assoc 20:DF:B9:D3:83:09, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:36:09    172.17.0.1    notice     WLCEVENTD wlceventd_proc_event(420): eth2: Auth 20:DF:B9:D3:83:09, status: 0, reason: d11 RC reserved (0)
    01:Jun:2020    00:36:07    172.17.0.1    err     Timeout waiting for PADO packets
    01:Jun:2020    00:36:06    172.17.0.1    notice     apply redirect rules error!
    
    Any advice are welcome! :)

    Thanks all for time and help :)
     
  2. heysoundude

    heysoundude Very Senior Member

    Joined:
    Sep 20, 2016
    Messages:
    1,011
    Will Bell allow business customers to do these sorts of things?
    what happens when you plug a computer directly into the Sagecomm gateway?
    Shouldn't Bell's tech support people be able to help troubleshoot to this point?
    Are you CERTAIN that everything is correct on your router?

    (Is Fibe IPv6?)
     
  3. matge

    matge New Around Here

    Joined:
    May 31, 2020
    Messages:
    3
    When Bell tech came do the installation, he highly suggest me to do this. He gave me the instructions and we did it together and that went fine!

    I have over look the WAN settings and the PPPoE settings a couple of time and didn't see anything wrong. I'll call Bell but I'll need to schedule a no internet period and in these times of work at home, it is more complicated! If anyone has other tips, thanks! I'll update this post after my call to Bell
     
  4. rotareneg

    rotareneg Occasional Visitor

    Joined:
    Apr 1, 2018
    Messages:
    11
    Completely different ISP here (Nex-Tech) but I've had this same issue as well. It's a fiber connection using PPPoE, and with every router I've used (RT-N16, WRT54GL, RT-AC66 B1,) reconnecting after a reboot or power cycle can sometimes take a while, with the same messages in the log.
     
    matge likes this.
  5. heysoundude

    heysoundude Very Senior Member

    Joined:
    Sep 20, 2016
    Messages:
    1,011
    One thing I forgot to ask -
    Does Bell assign you a static IP?


    Sent from my iPhone using Tapatalk
     
  6. matge

    matge New Around Here

    Joined:
    May 31, 2020
    Messages:
    3
    No I don't have static IP! and on each reconnect, I think I always have a different IP.
     
    heysoundude likes this.
  7. heysoundude

    heysoundude Very Senior Member

    Joined:
    Sep 20, 2016
    Messages:
    1,011
    That’s (probably) the problem right there.
    DDNS is your solution.
    Go sign up for a free account at tunnelbroker.net, make the tunnel, then make your router do the rest.

    How often do you reboot your router?


    Sent from my iPhone using Tapatalk