Community discussions

MikroTik App
 
dksoft
Member Candidate
Member Candidate
Topic Author
Posts: 148
Joined: Thu Dec 06, 2012 8:56 am
Location: Germany

Reboot right after PPP login when EOIP (7.1b6,7.1b7,7.1rc1)

Mon Aug 23, 2021 3:17 pm

Hi,

may someone have a clue why my CCR1009 (also RB4011 and CCR2004) reboots right after a l2tp login?
I can see on the log:
Aug 23 14:07:55 router.intra l2tp,ppp,info INFO: <l2tp-router-esp>: authenticated
Aug 23 14:07:55 router.intra l2tp,ppp,info INFO: <l2tp-router-esp>: connected
Aug 23 14:07:55 router.intra l2tp,ppp,info INFO: <l2tp-router-esp>: using encoding - MPPE128 stateless
Then it reboots.

The PPP profile looks like:
/ppp profile
add local-address=10.2.0.1 name=ROUTER-ESP-profile remote-address=10.2.0.2 use-encryption=required use-ipv6=default
And so far I found that if I do not set the local/remote address. The login is successfull without an reboot.

I have no clue at things work very well in 6.48.3 and below.

Thanks for any input,
dksoft


Updated logging information:
Aug 23 16:50:18 router.intra l2tp,info INFO: first L2TP UDP packet received from 85.31.134.30
Aug 23 16:50:18 router.intra l2tp,debug DEBUG: tunnel 2 entering state: wait-ctl-conn
Aug 23 16:50:18 router.intra l2tp,debug DEBUG: tunnel 2 entering state: estabilished
Aug 23 16:50:18 router.intra l2tp,debug DEBUG: session 2 entering state: wait-connect
Aug 23 16:50:18 router.intra l2tp,debug DEBUG: session 2 entering state: established
Aug 23 16:50:18 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: LCP lowerup
Aug 23 16:50:18 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: LCP open
Aug 23 16:50:18 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: LCP opened
Aug 23 16:50:19 router.intra l2tp,ppp,info,account INFO: router-esp logged in, 10.2.0.2 from 85.31.134.30
Aug 23 16:50:19 router.intra l2tp,ppp,info INFO: <l2tp-router-esp>: authenticated
Aug 23 16:50:19 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: IPCP lowerup
Aug 23 16:50:19 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: IPCP open
Aug 23 16:50:19 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: IPV6CP lowerup
Aug 23 16:50:19 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: IPV6CP open
Aug 23 16:50:19 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: MPLSCP lowerup
Aug 23 16:50:19 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: MPLSCP open
Aug 23 16:50:19 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: BCP open
Aug 23 16:50:19 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: CCP lowerup
Aug 23 16:50:19 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: CCP open
Aug 23 16:50:19 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: IPV6CP opened
Aug 23 16:50:19 router.intra l2tp,ppp,info INFO: <l2tp-router-esp>: connected
Aug 23 16:50:19 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: MPLSCP opened
Aug 23 16:50:19 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: CCP opened
Aug 23 16:50:19 router.intra l2tp,ppp,info INFO: <l2tp-router-esp>: using encoding - MPPE128 stateless
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 1.3.1 Tag updated routes for merging
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 1.3.3 Loading new prefix values
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 1.3.4 Merge route updates
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 2.2 Merge forwarding path updates
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 3 Main publish
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 6.1 Cleanup merge
Aug 23 16:50:19 router.intra l2tp,ppp,debug DEBUG: <85.31.134.30>: IPCP opened
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 1.3.1 Tag updated routes for merging
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 1.3.4 Merge route updates
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 2.2 Merge forwarding path updates
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 3 Main publish
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 6.1 Cleanup merge
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 1.3.1 Tag updated routes for merging
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 1.3.4 Merge route updates
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 2.2 Merge forwarding path updates
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: Prepare queued LINK/%*f00001/10-5/0/SRC10.2.0.1%*f00001
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: Set initial reachability for interface LINK/%*f00001/10-5/0/SRC10.2.0.1%*f00001
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: Apply reachability to LINK/%*f00001/10-5/0/SRC10.2.0.1%*f00001
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: Resolving LINK/%*f00001/10-5/0/SRC10.2.0.1%*f00001
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 3 Main publish
Aug 23 16:50:19 router.intra route,debug,calc DEBUG: 6.1 Cleanup merge
 
dksoft
Member Candidate
Member Candidate
Topic Author
Posts: 148
Joined: Thu Dec 06, 2012 8:56 am
Location: Germany

Re: Reboot right after PPP login when EOIP (7.1b6,7.1b7,7.1rc1)

Mon Aug 23, 2021 7:08 pm

I spent some more hours to trace the problem and it looks like existing EOIP channels are causing the problem.

E.g. I can have multiple L2TP dialups from clients to the CCR1009 and creating an EOIP tunnel over that connection: Works fine.

I can have an IPSEC or wireguard tunnel from the CCR1009 to another CHR and setting up an EOIP tunnel over that connection: Works fine.

But if I setup the tunnel to the CHR and after that a client dials in, the CCR1009 reboots.
More interesting if I disable the dialup based EOIP, it also reboots. Just the L2TP login is causing the reboot.

I might do something wrong but I would never expect that the router just reboots without any error message in the log.
As support is not responding I stop further investigation and wait till someone else runs into the problem.
 
oreggin
Member Candidate
Member Candidate
Posts: 172
Joined: Fri Oct 16, 2009 9:21 pm

Re: Reboot right after PPP login when EOIP (7.1b6,7.1b7,7.1rc1)

Tue Sep 14, 2021 4:56 pm

On ROSv6 I was using L2VPN/VPLS over L2TP over IPSec and when I upgraded my RB4011s to ROS7 I experienced the crash too. Then I tried EoIP over L2TP over IPSec instead but it cause the same crash so now I haven't L2 pipe possibility over global internet...
 
oreggin
Member Candidate
Member Candidate
Posts: 172
Joined: Fri Oct 16, 2009 9:21 pm

Re: Reboot right after PPP login when EOIP (7.1b6,7.1b7,7.1rc1)

Thu Sep 16, 2021 10:37 pm

Moreover my RB1100AHx2 (PPC) crashing with 7.1RCx when I add EoIP interface to any type of bridge.
 
KILLPC
just joined
Posts: 2
Joined: Thu Apr 29, 2021 5:19 pm
Location: Greece

Re: Reboot right after PPP login when EOIP (7.1b6,7.1b7,7.1rc1)

Mon Dec 27, 2021 1:01 am

I am facing similar issues with an RB4011iGS+5HacQ2HnD at 7.1.1 with ipip, eoip, pppoe over eoip ( tunnels are established via ikev2 aes128gcm with rb4011 as responder). In 6.48.6 i do not face them. The other end is a rb750r2.

In 7.1.1 the router reboots from time to time (and i performed a reset and manually configured the 4011 once again).
If i disable the tunnel interfaces the operation of the 4011 remains stable.
For testing I even used a separate hex rb 750gl (ver 7.1.1 and 6.48.6) and created the same tunnel interfaces (traffic from the rb750gl go through the 4011 and was not esp encapsulated) where i dedicated one of its LAN interfaces as secondary wan gw for the rb4011. Then i passed some traffic from my computer with a mangle rule with mark routing action to that secondary wan. The 4011 still reboots randomly.

Due to the above i downgraded back to 6.48.6.

Who is online

Users browsing this forum: No registered users and 24 guests