PPPOE log: terminating... - spurios reauthentication

I’m activating a new PPPoE server, a CCR1009, and for the first time i saw this message, when pppoe clients where connecting:

18:51:16 pppoe,info PPPoE connection established from EC:08:6B:XX:XX:XX
18:51:16 pppoe,info PPPoE connection established from EC:08:6B:XX:XX:XX
18:51:16 pppoe,ppp,info,account xxx-yyy logged in, 146.247.ab.cd 
18:51:16 pppoe,ppp,info <pppoe-xxx-yyy>: authenticated 
18:51:16 pppoe,ppp,info <pppoe-xxx-yyy>: connected 
18:51:17 pppoe,ppp,info <pppoe-xxx-yyy>: terminating... - spurios reauthentication 
18:51:17 pppoe,ppp,info,account xxx-yyy logged out, 0 54 72 3 5 
18:51:17 pppoe,ppp,info <pppoe-xxx-yyy>: disconnected

This happen only with two clients, the other 60 reconnected without problems

The setup is:

  • the CCR has two interfaces, ether5 and ether6, bonded toghether with LACP;
  • on bond1 there are 3 VLAN: wan (internet), lan (server), ptp (wireless link to the network);
  • from the CCR to the RB750, where there are 4 sectors, there are 4 VPLS tunnels, one for each sector;
  • pppoe connections are encapsulated in VLAN, ID 10, but, for legacy configuration, there is also pppoe servers on “native” interfaces, the VPLSs
  • VPLS interfaces are unique port for bridges (workaround to avoid mass disconnection from VPLS disconnection)

So, a default configuration is something like this

/ interface vpls
add name=vpls1 ...
/ interface bridge
add name=vpls1-bridge
/ interface bridge port
add bridge=vpls1-bridge interface=vpls1
/ interface vlan
add name=vlan_pppoe-vpls1 interface=vpls1-bridge
/ interface pppoe-server server
add interface=vlan_pppoe-vpls1
add interface=vpls1-bridge

My workaround was to disable pppoe server on native interfaces, because I noticed

18:51:16 pppoe,info PPPoE connection established from EC:08:6B:XX:XX:XX
18:51:16 pppoe,info PPPoE connection established from EC:08:6B:XX:XX:XX

and enabling pppoe debug I saw PADI e PADO packet both from native and VLAN interfaces.

Tomorrow I’ll downgrade the CCR (but then I’ll have to disable bonding interface).

Any idea?

did you ever get a solution to this? I’m seeing the same error message with a pptp-client connection

PPTP server is on CCR1009-7G-1C-1S+ (tile) 6.49.8

Forget about pptp, there are a lot better alternatives.
It can be anything, from poor implementation to issues with CGNAT, which didn’t existed when pptp was designed.