Hi,
I have a RB4011iGS+5HacQ2HnD-IN. New to RouterOS and networking in general. Everytime my PPPoE connection disconnects, when i turn off/on router and fails to connect or ISP’s Switch takes a long time to restart in case of power outage how to automatically reconnect/redial to the ISP? Everytime i have to goto System → Reboot if it fails, again i have to reboot and so on. Is there a way to automatically a reconnect?
The PPPoE client normally does reconnect automatically. So something is wrong. You could use a script to disable and re-enable the PPPoE client interface if you lose connectivity, but it would be a workaround and normally it should not be necessary.
As a first step, post an anonymized export of your configuration (see the mini-howto in my automatic signature below). It will probably require sniffing during the outage, on the physical interface to which the PPPoE client is attached, to see what is going on and why the PPPoE session doesn’t re-establish.
/export hide-sensitive file=anynameyouwish
anav, you’re like a dog who marks every tree it walks by, but instead of trees you’re marking forum topics 
not really necessary as sindy kind of adviced/requested the same thing..
Plugpulled, regardless of the actual cause of the issue, which should be fixed anyway, you can get auto reboot using watchdog.
https://wiki.mikrotik.com/wiki/Manual:System/Watchdog
First, find a stable IP address, e.g. the remote address from the PPPoE interface. Or 1.1.1.1. Make sure the IP is pingable from the device.
Then, set the IP as watchdog address. As soon as the IP is unreachable for the time specified (by default: 1 minute), the device will reboot. There is an extra 5 minute wait time before the first subsequent reboot to make sure the device is slowly rebooting as long as the network is unavailable.
/system watchdog set watch-address=1.1.1.1 ping-timeout=5m
Sorry nescafe, if some one said to me anonymized, my eyes would glaze over. I like direct clear speech.
Many times it takes two or three or more times to ask for the export before th op actually produces it. A little reinforcement never hurt.
Not going to change my ways anytime soon.
Did you ever find a fix for this?
I’ve experienced the same for some time across two sites. Both were using PPPoE client for xDSL (one ADSL, one VDSL) via Draytek Vigor 120/130 modems.
The ADSL has just migrated to fibre with ISP-supplied ONT. That one’s not yet had any downtime to see if the PPPoE behaves the same on this one.
If I disable then re-enable the PPPoE client interface, it comes up straight away.
Not set up a watchdog as yet, but considering it if I can’t resolve it. On the VDSL site, I now have a secondary Mikrotik with LTE connectivity which I can use for remote access when the VDSL is down to bounce the modem/router.
Log from this morning:
08:41:09 pppoe,ppp,info Uno FTTC: terminating… - peer is not responding
08:41:09 pppoe,ppp,info Uno FTTC: disconnected
08:41:09 pppoe,ppp,info Uno FTTC: initializing…
08:41:09 interface,info GREoIPsec_66BHR link down
08:41:09 pppoe,ppp,info Uno FTTC: connecting…
08:41:09 route,ospf,info backbone-v2 { version: 2 router-id: 172.16.1.1 } backbo ne-v2 { 0.0.0.0 } interface { broadcast 172.16.1.1%*12 } neighbor { router-id: 1 72.16.1.2 state: Full } state change to Down
08:41:09 route,ospf,info backbone-v2 { version: 2 router-id: 172.16.1.1 } backbo ne-v2 { 0.0.0.0 } interface { broadcast 172.16.1.1%*12 } destroyed
08:41:19 pppoe,ppp,info Uno FTTC: terminating… - disconnected
08:41:19 pppoe,ppp,info Uno FTTC: disconnected
08:41:19 pppoe,ppp,info Uno FTTC: initializing…
08:41:19 pppoe,ppp,info Uno FTTC: connecting…
08:41:29 pppoe,ppp,info Uno FTTC: terminating… - disconnected
08:41:29 pppoe,ppp,info Uno FTTC: disconnected
08:41:29 pppoe,ppp,info Uno FTTC: initializing…
08:41:29 pppoe,ppp,info Uno FTTC: connecting…
08:41:40 pppoe,ppp,info Uno FTTC: terminating… - disconnected
08:41:40 pppoe,ppp,info Uno FTTC: disconnected
08:41:40 pppoe,ppp,info Uno FTTC: initializing…
08:41:40 pppoe,ppp,info Uno FTTC: connecting…
08:41:50 pppoe,ppp,info Uno FTTC: terminating… - disconnected
08:41:50 pppoe,ppp,info Uno FTTC: disconnected
08:41:51 pppoe,ppp,info Uno FTTC: initializing…
08:41:51 pppoe,ppp,info Uno FTTC: connecting…
08:43:08 ipsec,info killing ike2 SA: 66BHR x[4500]-x[4500] spi:79a3f9134a4e1629:0c61e0c41bc9a922
08:43:51 pppoe,ppp,info Uno FTTC: terminating…
08:43:51 pppoe,ppp,info Uno FTTC: disconnected
08:43:54 pppoe,ppp,info Uno FTTC: initializing…
08:43:54 pppoe,ppp,info Uno FTTC: connecting…
08:50:03 system,info,account user soram logged in from 192.168.58.254 via ssh
08:51:04 pppoe,ppp,info Uno FTTC: terminating…
08:51:04 pppoe,ppp,info Uno FTTC: disabled
08:51:04 system,info device changed by ssh:soram@192.168.58.254/action:3602 (/in terface set “Uno FTTC” disabled=yes; /queue interface set “Uno FTTC”; /interface pppoe-client set “Uno FTTC” disabled=yes)
08:51:12 pppoe,ppp,info Uno FTTC: initializing…
08:51:12 pppoe,ppp,info Uno FTTC: connecting…
08:51:12 system,info device changed by ssh:soram@192.168.58.254/action:3603 (/i nterface set “Uno FTTC” disabled=no; /queue interface set “Uno FTTC”; /interface pppoe-client set “Uno FTTC” disabled=no)
08:51:12 pppoe,ppp,info Uno FTTC: authenticated
08:51:12 pppoe,ppp,info Uno FTTC: connected
08:51:12 interface,info Uno FTTC detect UNKNOWN
08:51:16 ipsec,info new ike2 SA (I): 66BHR x[4500]-x[4500] spi:9238bfc299b886ba:0434dc657c97b84c
08:51:17 ipsec,info new ike2 SA (R): 66BHR x[4500]-x[4500] spi:b9913f4daba60129:264a21bc2b4bf8e9
08:51:18 ipsec,info,account peer authorized: 66BHR x[4500]-x[4500] spi:9238bfc299b886ba:0434dc657c97b84c
08:51:18 ipsec,info,account peer authorized: 66BHR x[4500]-x[4500] spi:b9913f4daba60129:264a21bc2b4bf8e9
08:51:18 ipsec,info killing ike2 SA: 66BHR x[4500]-x[4500] spi:9238bfc299b886ba:0434dc657c97b84c
08:51:18 interface,info Uno FTTC detect INTERNET
08:51:21 interface,info GREoIPsec_66BHR link up
I experience the same issue as you, @sjoram , on vdsl both with frotzbox and zyxel modems, with the hAP ax3 on 7.14.3.
I sadly have not found a solution after a couple of days of digging, and will most likely resort to a watchdog. Really annoying issue, since I bought the zyxel because of it. I assumed it was some form of a malfunction on the fritzbox side. Who could have thought, that enabling-disabling the pppoe client fixes that.
No solution for me but a workaround below.
Check interface state every 15 mins, if not connected, disable wait 2 seconds and re-enable