Community discussions

MikroTik App
 
axc27
just joined
Topic Author
Posts: 7
Joined: Sat Jun 17, 2017 10:28 pm

hAP ac (RB 962UiGS): Port flapping on LAN port when used for PPPOE connection

Fri May 25, 2018 9:59 am

Hi there!

First post, and am directly coming up with a problem/question. I have been reading here a lot and, except for the problem described here, been able to answer all my configuration questions by doing research. But I did not find a solution for this problem, despite spending quite some time on resolving it (in research and in testing, therefore my apologies for the long post).

Brief description:
I am running a “hAP ac” as my home router and access point, connected to a DSL line via different modems.
If I the mikrotik is doing the PPPOE work (modem connected to ethernet port), i encounter frequent port flaps (1-2 times per day, but then often two to three “flaps” as a burst). This inevitably drops the internet connection and takes some time to reconnect. Accessing the modem directly (web interface) during the reconnection time shows that the VDSL connection has not been dropped but is still up. This usually happens in high load situations.
When having the modem do the PPPOE work with all data forwarded to the mikrotik (e. g. router with mikrotik in DMZ), the same setup is perfectly stable for weeks - no port flaps, not connection drop-outs (same cables, same power supply, etc.).

I did set up data logging to a remote syslog server to have more than 1000 lines available.
Additionally I did set up a script regularly generating some load on the internet connection on the same server (speed test every 30 minutes, logging the results to a file). This does help reproduce the problems.


Hardware:

Mikrotik:
RouterBOARD 962UiGS-5HacT2HnT
Current software version: 6.42.2
Current firmware: 6.42.2
Factory firmware: 3.34

Bought it a year ago (May 2017). Regularly updated the Software (channel “current”) and always updated the firmware as well.

VDSL modem:
Fritzbox 7362 in modem mode
OS Version: 06.83
ethernet port: 1 Gb/s

Fritzbox 7412 in modem mode
OS Version: 06.83
ethernet port: 100 Mb/s

DrayTek Vigor 130 in modem mode
OS Version: 3.8.2
ethernet port: 1 Gb/s

Setup:
VDSL (1&1, Germany) <- -> Modem <- -> Mikrotik

Max speed of the VDSL line is 50 Mb/s down, 10 Mb/s up (line capacity is 83 down / 34 up).

As the PPPOE connection has to be tagged with VLAN id 7 (telekom network), added a VLAN to the ethernet port (vlan7-pppoe) and set the PPPOE client (pppoe-out1) to use this device. To access the modem web interface, I add an ip address in the correct subnet to the ethernet port. (learned this just a few days ago when reading documentation for the draytek - this does work with the fritz box as well)

When working with the router and DMZ solution, I disable the VLAN end set the corresponding ethernet port to DHCP client.
Other devices connected to the Mikrotik were all running at 1Gb/s:
  • HP1810-8G switch,
  • Fritzbox handling the VOIP connections only (not connected at the moment).

Log file excerpt of a port flapping and reconnect event:

2018-05-20T19:37:26.319917+02:00 router pppoe,ppp,info pppoe-out1: connected
2018-05-20T19:41:19.285735+02:00 router interface,info ether5-WAN link down
2018-05-20T19:41:19.294424+02:00 router pppoe,debug vlan7-pppoe: terminating sessions: interface state changed
2018-05-20T19:41:19.294424+02:00 router pppoe,ppp,debug pppoe-out1: LCP lowerdown
2018-05-20T19:41:19.294424+02:00 router pppoe,ppp,debug pppoe-out1: LCP closed
2018-05-20T19:41:19.294424+02:00 router pppoe,ppp,debug pppoe-out1: CCP lowerdown
2018-05-20T19:41:19.294424+02:00 router pppoe,ppp,debug pppoe-out1: BCP lowerdown
2018-05-20T19:41:19.294424+02:00 router pppoe,ppp,debug pppoe-out1: BCP down event in starting state
2018-05-20T19:41:19.294424+02:00 router pppoe,ppp,debug pppoe-out1: IPCP lowerdown
2018-05-20T19:41:19.294424+02:00 router pppoe,ppp,debug pppoe-out1: IPCP closed
2018-05-20T19:41:19.295171+02:00 router pppoe,ppp,debug pppoe-out1: IPV6CP lowerdown
2018-05-20T19:41:19.295171+02:00 router pppoe,ppp,debug pppoe-out1: IPV6CP down event in starting state
2018-05-20T19:41:19.295171+02:00 router pppoe,ppp,debug pppoe-out1: MPLSCP lowerdown
2018-05-20T19:41:19.295171+02:00 router pppoe,ppp,debug pppoe-out1: CCP close
2018-05-20T19:41:19.295171+02:00 router pppoe,ppp,debug pppoe-out1: BCP close
2018-05-20T19:41:19.295171+02:00 router pppoe,ppp,debug pppoe-out1: IPCP close
2018-05-20T19:41:19.295539+02:00 router pppoe,ppp,debug pppoe-out1: IPV6CP close
2018-05-20T19:41:19.295539+02:00 router pppoe,ppp,debug pppoe-out1: MPLSCP close
2018-05-20T19:41:19.295772+02:00 router pppoe,ppp,info pppoe-out1: terminating... - disconnected
2018-05-20T19:41:19.313295+02:00 router pppoe,ppp,debug pppoe-out1: LCP lowerdown
2018-05-20T19:41:19.313578+02:00 router pppoe,ppp,debug pppoe-out1: LCP down event in starting state
2018-05-20T19:41:19.314191+02:00 router pppoe,ppp,info pppoe-out1: disconnected
2018-05-20T19:41:19.314191+02:00 router pppoe,ppp,info pppoe-out1: initializing...
2018-05-20T19:41:19.315155+02:00 router pppoe,ppp,info pppoe-out1: connecting...
2018-05-20T19:41:19.315552+02:00 router pppoe,ppp,debug pppoe-out1: CCP close
2018-05-20T19:41:19.315793+02:00 router pppoe,ppp,debug pppoe-out1: BCP close
2018-05-20T19:41:19.316134+02:00 router pppoe,ppp,debug pppoe-out1: IPCP close
2018-05-20T19:41:19.316448+02:00 router pppoe,ppp,debug pppoe-out1: IPV6CP close
2018-05-20T19:41:19.317143+02:00 router pppoe,ppp,debug pppoe-out1: MPLSCP close
2018-05-20T19:41:19.317143+02:00 router pppoe,ppp,info pppoe-out1: terminating...
2018-05-20T19:41:19.317544+02:00 router pppoe,ppp,debug pppoe-out1: LCP lowerdown
2018-05-20T19:41:19.317910+02:00 router pppoe,ppp,debug pppoe-out1: LCP down event in starting state
2018-05-20T19:41:19.318268+02:00 router pppoe,ppp,info pppoe-out1: disconnected
2018-05-20T19:41:19.318447+02:00 router pppoe,ppp,info pppoe-out1: initializing...
2018-05-20T19:41:19.319272+02:00 router pppoe,ppp,info pppoe-out1: connecting...
2018-05-20T19:41:22.285545+02:00 router interface,info ether5-WAN link up (speed 1G, full duplex)
2018-05-20T19:41:22.541811+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:22.541811+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:22.542945+02:00 router pppoe,debug,packet host-uniq=0xab0250
2018-05-20T19:41:22.542945+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:23.482903+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:23.482903+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:23.483896+02:00 router pppoe,debug,packet host-uniq=0xab0250
2018-05-20T19:41:23.483896+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:24.535275+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:24.535275+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:24.536909+02:00 router pppoe,debug,packet host-uniq=0xab0250
2018-05-20T19:41:24.536909+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:25.286929+02:00 router interface,info ether5-WAN link down
2018-05-20T19:41:25.293414+02:00 router pppoe,ppp,debug pppoe-out1: CCP close
2018-05-20T19:41:25.293414+02:00 router pppoe,ppp,debug pppoe-out1: BCP close
2018-05-20T19:41:25.293414+02:00 router pppoe,ppp,debug pppoe-out1: IPCP close
2018-05-20T19:41:25.293414+02:00 router pppoe,ppp,debug pppoe-out1: IPV6CP close
2018-05-20T19:41:25.293414+02:00 router pppoe,ppp,debug pppoe-out1: MPLSCP close
2018-05-20T19:41:25.293414+02:00 router pppoe,ppp,info pppoe-out1: terminating...
2018-05-20T19:41:25.295754+02:00 router pppoe,ppp,debug pppoe-out1: LCP lowerdown
2018-05-20T19:41:25.295754+02:00 router pppoe,ppp,debug pppoe-out1: LCP down event in starting state
2018-05-20T19:41:25.295754+02:00 router pppoe,ppp,info pppoe-out1: disconnected
2018-05-20T19:41:25.295754+02:00 router pppoe,ppp,info pppoe-out1: initializing...
2018-05-20T19:41:25.295754+02:00 router pppoe,ppp,info pppoe-out1: connecting...
2018-05-20T19:41:29.285840+02:00 router interface,info ether5-WAN link up (speed 1G, full duplex)
2018-05-20T19:41:29.462070+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:29.462070+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:29.462070+02:00 router pppoe,debug,packet host-uniq=0xab0251
2018-05-20T19:41:29.462070+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:30.362777+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:30.362777+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:30.363501+02:00 router pppoe,debug,packet host-uniq=0xab0251
2018-05-20T19:41:30.363501+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:31.244355+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:31.244355+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:31.244355+02:00 router pppoe,debug,packet host-uniq=0xab0251
2018-05-20T19:41:31.244355+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:32.366866+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:32.366866+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:32.366866+02:00 router pppoe,debug,packet host-uniq=0xab0251
2018-05-20T19:41:32.366866+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:33.448093+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:33.448093+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:33.448778+02:00 router pppoe,debug,packet host-uniq=0xab0251
2018-05-20T19:41:33.448778+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:34.459383+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:34.459383+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:34.459383+02:00 router pppoe,debug,packet host-uniq=0xab0251
2018-05-20T19:41:34.459383+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:35.561718+02:00 router pppoe,ppp,debug pppoe-out1: CCP close
2018-05-20T19:41:35.561718+02:00 router pppoe,ppp,debug pppoe-out1: BCP close
2018-05-20T19:41:35.561718+02:00 router pppoe,ppp,debug pppoe-out1: IPCP close
2018-05-20T19:41:35.561718+02:00 router pppoe,ppp,debug pppoe-out1: IPV6CP close
2018-05-20T19:41:35.561718+02:00 router pppoe,ppp,debug pppoe-out1: MPLSCP close
2018-05-20T19:41:35.561718+02:00 router pppoe,ppp,info pppoe-out1: terminating... - disconnected
2018-05-20T19:41:35.561718+02:00 router pppoe,ppp,debug pppoe-out1: LCP lowerdown
2018-05-20T19:41:35.561718+02:00 router pppoe,ppp,debug pppoe-out1: LCP down event in starting state
2018-05-20T19:41:35.561718+02:00 router pppoe,ppp,info pppoe-out1: disconnected
2018-05-20T19:41:35.561718+02:00 router pppoe,ppp,info pppoe-out1: initializing...
2018-05-20T19:41:35.561718+02:00 router pppoe,ppp,info pppoe-out1: connecting...
2018-05-20T19:41:35.602794+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:35.602794+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:35.602794+02:00 router pppoe,debug,packet host-uniq=0xab0252
2018-05-20T19:41:35.602794+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:36.612740+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:36.612740+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:36.612740+02:00 router pppoe,debug,packet host-uniq=0xab0252
2018-05-20T19:41:36.612740+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:37.545049+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:37.545049+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:37.545809+02:00 router pppoe,debug,packet host-uniq=0xab0252
2018-05-20T19:41:37.545809+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:38.656362+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:38.656362+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:38.657342+02:00 router pppoe,debug,packet host-uniq=0xab0252
2018-05-20T19:41:38.657342+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:39.295962+02:00 router interface,info ether5-WAN link down
2018-05-20T19:41:39.303382+02:00 router pppoe,ppp,debug pppoe-out1: CCP close
2018-05-20T19:41:39.303382+02:00 router pppoe,ppp,debug pppoe-out1: BCP close
2018-05-20T19:41:39.303382+02:00 router pppoe,ppp,debug pppoe-out1: IPCP close
2018-05-20T19:41:39.303382+02:00 router pppoe,ppp,debug pppoe-out1: IPV6CP close
2018-05-20T19:41:39.303382+02:00 router pppoe,ppp,debug pppoe-out1: MPLSCP close
2018-05-20T19:41:39.303987+02:00 router pppoe,ppp,info pppoe-out1: terminating...
2018-05-20T19:41:39.303987+02:00 router pppoe,ppp,debug pppoe-out1: LCP lowerdown
2018-05-20T19:41:39.303987+02:00 router pppoe,ppp,debug pppoe-out1: LCP down event in starting state
2018-05-20T19:41:39.303987+02:00 router pppoe,ppp,info pppoe-out1: disconnected
2018-05-20T19:41:39.304317+02:00 router pppoe,ppp,info pppoe-out1: initializing...
2018-05-20T19:41:39.304317+02:00 router pppoe,ppp,info pppoe-out1: connecting...
2018-05-20T19:41:43.295690+02:00 router interface,info ether5-WAN link up (speed 1G, full duplex)
2018-05-20T19:41:44.392869+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:44.392869+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:44.392869+02:00 router pppoe,debug,packet host-uniq=0xab0253
2018-05-20T19:41:44.392869+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:45.343211+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:45.343211+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:45.343211+02:00 router pppoe,debug,packet host-uniq=0xab0253
2018-05-20T19:41:45.343211+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:46.414655+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:46.414655+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:46.414655+02:00 router pppoe,debug,packet host-uniq=0xab0253
2018-05-20T19:41:46.414655+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:47.435787+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:47.435787+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:47.436546+02:00 router pppoe,debug,packet host-uniq=0xab0253
2018-05-20T19:41:47.436546+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:48.447243+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:48.447243+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:48.447243+02:00 router pppoe,debug,packet host-uniq=0xab0253
2018-05-20T19:41:48.447243+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:49.459161+02:00 router pppoe,ppp,debug pppoe-out1: CCP close
2018-05-20T19:41:49.459161+02:00 router pppoe,ppp,debug pppoe-out1: BCP close
2018-05-20T19:41:49.459161+02:00 router pppoe,ppp,debug pppoe-out1: IPCP close
2018-05-20T19:41:49.459161+02:00 router pppoe,ppp,debug pppoe-out1: IPV6CP close
2018-05-20T19:41:49.459161+02:00 router pppoe,ppp,debug pppoe-out1: MPLSCP close
2018-05-20T19:41:49.459161+02:00 router pppoe,ppp,info pppoe-out1: terminating... - disconnected
2018-05-20T19:41:49.459161+02:00 router pppoe,ppp,debug pppoe-out1: LCP lowerdown
2018-05-20T19:41:49.459161+02:00 router pppoe,ppp,debug pppoe-out1: LCP down event in starting state
2018-05-20T19:41:49.459161+02:00 router pppoe,ppp,info pppoe-out1: disconnected
2018-05-20T19:41:49.459161+02:00 router pppoe,ppp,info pppoe-out1: initializing...
2018-05-20T19:41:49.459161+02:00 router pppoe,ppp,info pppoe-out1: connecting...
2018-05-20T19:41:49.499109+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:49.499109+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:49.499109+02:00 router pppoe,debug,packet host-uniq=0xab0254
2018-05-20T19:41:49.499109+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:50.430429+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:50.430429+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:50.430429+02:00 router pppoe,debug,packet host-uniq=0xab0254
2018-05-20T19:41:50.430429+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:51.351543+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:51.351543+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:51.351543+02:00 router pppoe,debug,packet host-uniq=0xab0254
2018-05-20T19:41:51.351543+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:52.392893+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:52.392893+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:52.392893+02:00 router pppoe,debug,packet host-uniq=0xab0254
2018-05-20T19:41:52.392893+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:53.453316+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:53.453316+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:53.453316+02:00 router pppoe,debug,packet host-uniq=0xab0254
2018-05-20T19:41:53.453316+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:54.414647+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:54.414647+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:54.414647+02:00 router pppoe,debug,packet host-uniq=0xab0254
2018-05-20T19:41:54.414647+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:55.486013+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:55.486013+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:55.486013+02:00 router pppoe,debug,packet host-uniq=0xab0254
2018-05-20T19:41:55.486013+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:56.567283+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:56.567283+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:56.567283+02:00 router pppoe,debug,packet host-uniq=0xab0254
2018-05-20T19:41:56.567283+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:57.518414+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:57.518414+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:57.518414+02:00 router pppoe,debug,packet host-uniq=0xab0254
2018-05-20T19:41:57.518414+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:58.539877+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:58.539877+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:58.539877+02:00 router pppoe,debug,packet host-uniq=0xab0254
2018-05-20T19:41:58.539877+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:41:59.531627+02:00 router pppoe,ppp,debug pppoe-out1: CCP close
2018-05-20T19:41:59.531627+02:00 router pppoe,ppp,debug pppoe-out1: BCP close
2018-05-20T19:41:59.531627+02:00 router pppoe,ppp,debug pppoe-out1: IPCP close
2018-05-20T19:41:59.531627+02:00 router pppoe,ppp,debug pppoe-out1: IPV6CP close
2018-05-20T19:41:59.531627+02:00 router pppoe,ppp,debug pppoe-out1: MPLSCP close
2018-05-20T19:41:59.531627+02:00 router pppoe,ppp,info pppoe-out1: terminating... - disconnected
2018-05-20T19:41:59.531627+02:00 router pppoe,ppp,debug pppoe-out1: LCP lowerdown
2018-05-20T19:41:59.531627+02:00 router pppoe,ppp,debug pppoe-out1: LCP down event in starting state
2018-05-20T19:41:59.531627+02:00 router pppoe,ppp,info pppoe-out1: disconnected
2018-05-20T19:41:59.752303+02:00 router pppoe,ppp,info pppoe-out1: initializing...
2018-05-20T19:41:59.752303+02:00 router pppoe,ppp,info pppoe-out1: connecting...
2018-05-20T19:41:59.752303+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:41:59.752303+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:41:59.752303+02:00 router pppoe,debug,packet host-uniq=0xab0255
2018-05-20T19:41:59.752303+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:42:00.793051+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:42:00.793051+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:42:00.793406+02:00 router pppoe,debug,packet host-uniq=0xab0255
2018-05-20T19:42:00.793406+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:42:01.875506+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:42:01.875506+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:42:01.876219+02:00 router pppoe,debug,packet host-uniq=0xab0255
2018-05-20T19:42:01.876219+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:42:02.886974+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:42:02.886974+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:42:02.886974+02:00 router pppoe,debug,packet host-uniq=0xab0255
2018-05-20T19:42:02.886974+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:42:03.908224+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:42:03.908224+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:42:03.908224+02:00 router pppoe,debug,packet host-uniq=0xab0255
2018-05-20T19:42:03.908224+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:42:04.899514+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:42:04.899514+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:42:04.899514+02:00 router pppoe,debug,packet host-uniq=0xab0255
2018-05-20T19:42:04.899514+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:42:05.970813+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:42:05.970813+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:42:05.970813+02:00 router pppoe,debug,packet host-uniq=0xab0255
2018-05-20T19:42:05.970813+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:42:06.901886+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:42:06.901886+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:42:06.902766+02:00 router pppoe,debug,packet host-uniq=0xab0255
2018-05-20T19:42:06.902766+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:42:07.933146+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:42:07.933146+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:42:07.933146+02:00 router pppoe,debug,packet host-uniq=0xab0255
2018-05-20T19:42:07.933146+02:00 router pppoe,debug,packet service-name=
2018-05-20T19:42:08.865112+02:00 router pppoe,debug,packet vlan7-pppoe: sent PADI to FF:FF:FF:FF:FF:FF
2018-05-20T19:42:08.865112+02:00 router pppoe,debug,packet session-id=0x0000
2018-05-20T19:42:08.865112+02:00 router pppoe,debug,packet host-uniq=0xab0255
2018-05-20T19:42:08.865112+02:00 router pppoe,debug,packet service-name=

Things I did try to fix the problem (none of the changes helped):

Switch ethernet port on mikrotik:
As I read on port flapping for ether1 on some devices, I tried connecting the modem to
  • ether1,
  • ether3, and
  • ether5 (with and without using the POE capability of the mikrotik on ether5)

Change the cable between modem an mikrotik:
  • 1m shielded cat6 cable
  • 3m shielded cat6 cable
  • manually grounding the shielding of the cat6 cable
  • 6m unshielded cat5 cable

different power supplies for mikrotik
  • original power supply
  • 48V power supply to be able to power the modem from the mikrotik via POE (via ether5)
I did have to set the POE to force on, as it would drop the power supply for the modem on a port flap if set to auto.

different power supplies for modem
  • original power supply (of the different modems, all of them 12V, 1A)
  • POE splitter powered from mirkotik (12V, 2A)

change the ethernet settings for the modem port on the mirkotik:
  • reduce speed from 1 Gb/s to 100 Mb/s by only advertising 100 Mb/s and 10Mb/s (auto negotiation still on)
  • switch off auto negotiation and force 100 Mb/s
  • One of the modems (7412) only has a 100 Mb/s port anyway.

change the modem:
  • Fritzbox 7362
  • Fritzbox 7412
  • DrayTek Vigor 130

This is what I recall trying over the last several months.


My reasons for pointing at the routerboard:

Initially I suspected the problem to be modem or DSL line related. The Fritzboxes do not officially support the modem mode anymore (at least it was removed from the we interface). But the results of the last month lead me to point at the mikrotik:

I set up the Fritzbox 7412 to the PPPOE work with the mikrotik in DMZ (exposed host in Fritzbox), as I wanted to gather the information required to complain with my internet provider.
Exactly the same setup I had running before with the PPPOE client on the mikrotik, same wiring, same power supplies, etc. And to my surprise I had did not have a single port flap in over a month. Not a single connection drop or DSL sync error. This was with the port to the modem connected with 100 Mb/s, the maximum for the Fritzbox.

Next I wanted to make sure it was not the Fritzboxes in modem mode. I searched the forums for a recommended modem and found the Draytek Vigor 130 the be one of the favourites. Bought one and tried with that: exactly the same problems as with the Fritzboxes in modem mode.
As the documentation for the Vigor explains how to get access to the modem web interface while using it as a modem, I set this up and checked connection data. The sync speed and snr were perfectly fine, exactly the same as seen on the Fritzbox in router mode. And to my surprise, the DSL sync did not even drop if a port flap occurred at the mikrotik. This does explain the long delay for reconnect: The DSL modem it still connected and has to time out before the mikrotik can initiate the connection again. This takes 1-2 minutes (very annoying if you are currently using the internet).
I checked the same thing with the Fritzbox: modem mode, set up the mikrotik to access the modem web interface, check connection status after a port flap. Same situation, modem is still synced and connected, mikrotik tries to reconnect after the port flap.

Having a look at the log files this is reasonable:
  • ethernet port goes down on mikrotik
  • PPPOE client disconnects while ethernet port is down, hence these packets never reach the modem
  • PPPOE client starts trying to reconnect while ethernet port is still down
  • ethernet port comes up again
  • the whole process is repeated e few times until the ethernet port stays up and stable.

Conclusion:

With all the stuff I tested, I _have to_ point a the mikrotik and its port flapping as a reason for an unstable connection.

Any help / steps I might not have tried yet?
Can I supply specific data to help resolve the problem?
Is there a solution to the problem at all or do I have to ditch the mikrotik and switch the supplier?


Thank you for helping and best regards,
axc27
 
axc27
just joined
Topic Author
Posts: 7
Joined: Sat Jun 17, 2017 10:28 pm

Re: hAP ac (RB 962UiGS): Port flapping on LAN port when used for PPPOE connection

Fri May 25, 2018 10:13 am

Directly replying to myself:

I just read this thread, especially this post, stating that the hAP uses the same chipset.
Might that be related / the same problem? of course, my internet connection does not support Gb/s speed, syncing at a lower speed...

Even though I had a stable connection with this setup:
HP switch <- 1Gb/s -> Mikrotik <- 100Mb/s -> Fritzbox as router (with DMZ for mirkotik) <- 50/10Mb/s -> VDSL

and this connection was unstable (port flapping / flopping):
HP switch <- 1Gb/s -> Mikrotik <- 1Gb/s, PPPOE sync at 50/10Mb/s -> Draytek Vigor 130 <- 50/10Mb/s -> VDSL

This does support the explanation given later in that thread, that it is a software related problem. The switch chipset only saw connections with 1Gb/s in the second setup, but the port was flapping/flopping.

/axc27
 
axc27
just joined
Topic Author
Posts: 7
Joined: Sat Jun 17, 2017 10:28 pm

Re: hAP ac (RB 962UiGS): Port flapping on LAN port when used for PPPOE connection

Sun Jun 03, 2018 4:23 pm

No one?
I cannot believe no one has the same problem... There has to be someone out there using the hAP ac with a PPPOE modem.
Maybe I have something wrong in my setup? At least I seem to have covered all the "easy replies".

/axc27
 
AndreasGR
newbie
Posts: 45
Joined: Mon May 14, 2018 5:27 pm

Re: hAP ac (RB 962UiGS): Port flapping on LAN port when used for PPPOE connection

Sun Jun 03, 2018 5:33 pm

I used to have the same problem (didn't have the resources to exchange modems etc.)
It was finally solved by the ISP changing the physical connection (cabling at the DSLAM, as the reported back).
May I ask what is your lock rate at the modem when it locks the connection with the ISP. Is it the same every time it locks?
Does it drop at the same time the PPoE loses connection?
 
axc27
just joined
Topic Author
Posts: 7
Joined: Sat Jun 17, 2017 10:28 pm

Re: hAP ac (RB 962UiGS): Port flapping on LAN port when used for PPPOE connection

Tue Jun 05, 2018 12:49 am

Initially, I was hoping do blame the ISP as well...

When the ethernet connection on the mikrotik drops out an comes back, the modem does not drop the PPPOE connection. I verified this by connecting to the modem web interface during / right after the port flopping.

The DSL line is very stable when using the Fritzbox as router and has enough capacity. It always (with Fritzbox and with vigor) syncs at the 50 Mbps up and 10 Mbps down that I pay for:
downstream
DSLAM Max. kbit/s: 51392
DSLAM Min. kbit/s: 27968
line capacity kbit/s: 84425
current rate kbit/s: 51384
Latency 8 ms
snr dB: 15
line attenuation dB: 11

upstream
DSLAM Max. kbit/s: 10048
DSLAM Min. kbit/s: 2784
line capacity kbit/s: 31158
current rate kbit/s: 10047
Latency 4 ms
snr dB: 19
line attenuation dB: 9


Profile 17a
G.Vector off
B43c
Unfortunately I have to assume the problem is related to the Mikrotik, not my ISP.

/axc27
 
AndreasGR
newbie
Posts: 45
Joined: Mon May 14, 2018 5:27 pm

Re: hAP ac (RB 962UiGS): Port flapping on LAN port when used for PPPOE connection

Tue Jun 05, 2018 3:54 pm

Too bad then.
May I suggest something that might sound dumb?
Please try to place a simple switch between the modem and the mikrotik and observe the behavior for a while.
Some time ago I had a problem with auto negotiation with a router from another brand and I fixed it by manually setting the negotiation parameters.
But before you start messing with these, please try the switch-in-the-middle theory.
 
tamasv
just joined
Posts: 1
Joined: Tue Jun 12, 2018 1:20 pm

Re: hAP ac (RB 962UiGS): Port flapping on LAN port when used for PPPOE connection

Tue Jun 12, 2018 1:25 pm

Same problem here ( Germany, Vigor130, Hex - 750G r3 ).
ether1 flaps randomly, tearing down the PPPoE connection. Cables, PSUs are replaced without any noticeable change.
Software version: 6.42.3
jun/09 13:42:31 interface,info UPDOWN: ether1 link down
jun/09 13:42:33 interface,info UPDOWN: ether1 link up (speed 1G, full duplex)
jun/09 13:42:34 interface,info UPDOWN: ether1 link down
jun/09 13:42:36 interface,info UPDOWN: ether1 link up (speed 1G, full duplex)
jun/09 13:42:40 interface,info UPDOWN: ether1 link down
jun/09 13:42:43 interface,info UPDOWN: ether1 link up (speed 1G, full duplex)
jun/09 13:42:46 interface,info UPDOWN: ether1 link down
jun/09 13:42:52 interface,info UPDOWN: ether1 link up (speed 100M, full duplex)
jun/09 13:44:49 interface,info UPDOWN: ether1 link down
jun/09 13:44:51 interface,info UPDOWN: ether1 link up (speed 1G, full duplex)
 
AndreasGR
newbie
Posts: 45
Joined: Mon May 14, 2018 5:27 pm

Re: hAP ac (RB 962UiGS): Port flapping on LAN port when used for PPPOE connection

Sat Jul 21, 2018 6:26 pm

An update would be of interest in case the problems have been fixed now that we are on 6.42.6.
 
BRMateus2
Frequent Visitor
Frequent Visitor
Posts: 71
Joined: Thu Oct 26, 2017 11:18 pm

Re: hAP ac (RB 962UiGS): Port flapping on LAN port when used for PPPOE connection

Thu Aug 09, 2018 6:10 am

You can try disable hardware-offload (/interface bridge port), fixed the issue for me, but it will make processing fully CPU bound..
This seems related as the OP already saw: viewtopic.php?f=3&t=128762
Running different speed negotiations.
 
User avatar
vecernik87
Forum Veteran
Forum Veteran
Posts: 770
Joined: Fri Nov 10, 2017 8:19 am

Re: hAP ac (RB 962UiGS): Port flapping on LAN port when used for PPPOE connection

Thu Aug 09, 2018 7:36 am

I had similar flapping issue with RBD52G (hap ac2) which was flapping 1G ethernet to my NAS. After several flaps it settled on 100Mbit speed and stayed like that. In the end, different cable solved the issue. Anything else (reboot of router, reboot of nas, same cable reconnection, interface disable etc..) did not help.

It is obviously hard to debug L1 issues without proper equipment so it usually ends up with wild guesses and attempts to do random things. It may be even wrong elmag shielding in router which will affect signal from one port by signal from another port.

Who is online

Users browsing this forum: No registered users and 45 guests