Device: Netcraze Ultra (NC-1812), aarch64
Firmware: 5.02.A.11.0-1 (5.2 Alpha 11), updated from Alpha 10 on 2026-09-29. No crash records before the update.
Symptom
Every successful login to the L2TP/IPsec VPN server reboots the router, about 2 seconds after the client is connected. Reproduced at least twice. WireGuard server clients are not affected.
Steps
1. L2TP/IPsec VPN server enabled (IKEv1, PSK).
2. Connect from a phone over mobile internet (behind NAT) with a valid user.
3. IKE, ESP, L2TP, PPP and MS-CHAPv2 all complete and the client gets 172.20.0.33, then the router reboots.
Log (MSK, 2026-09-29)
23:45:40 IKE_SA VPNL2TPServer[10] established
23:45:41 CHILD_SA VPNL2TPServer{1} established
23:45:42 L2TP tunnel/session up, ppp0 connected, MS-CHAPv2 auth succeeded
23:45:43 Vpn::EventSender: "L2TPIPSECSRVVPN": user "admin" connected ... with address "172.20.0.33"
23:45:45 last log line; next boot starts 23:46:45 (mt_wdt: SoC power status: software reset)
Crash dump (/proc/mtdoops/ndm, attached)
Program : ndm
Reason : segmentation fault
Thread : Event sender
Fault address: 0x00000000000000c8 (x0 = 0, i.e. null this)
Vpn::Firewall::OnVpnClient(const Event::VpnClient&)+0x0 (/lib/libndmVpn.so+0xf920)
Event::Sender::Run()+0x258 (/lib/libndmBase.so+0x9e578)
Thread::StartRoutine_(void*)+0x2ac (/lib/libndmBase.so+0x126cac)
Likely related
Alpha 11 changelog: "fixed routing between IKEv2/IPsec VPN Server clients and networks behind other VPN connections". The handler is called with a null Vpn::Firewall (x0 = 0). Enabling the IKEv2 server as well does not prevent the crash.
Workaround
Use the WireGuard server for remote access.
Self-test available on request.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
Hiker77
Device: Netcraze Ultra (NC-1812), aarch64 Firmware: 5.02.A.11.0-1 (5.2 Alpha 11), updated from Alpha 10 on 2026-09-29. No crash records before the update. Symptom Every successful login to the L2TP/IPsec VPN server reboots the router, about 2 seconds after the client is connected. Reproduced at least twice. WireGuard server clients are not affected. Steps 1. L2TP/IPsec VPN server enabled (IKEv1, PSK). 2. Connect from a phone over mobile internet (behind NAT) with a valid user. 3. IKE, ESP, L2TP, PPP and MS-CHAPv2 all complete and the client gets 172.20.0.33, then the router reboots. Log (MSK, 2026-09-29) 23:45:40 IKE_SA VPNL2TPServer[10] established 23:45:41 CHILD_SA VPNL2TPServer{1} established 23:45:42 L2TP tunnel/session up, ppp0 connected, MS-CHAPv2 auth succeeded 23:45:43 Vpn::EventSender: "L2TPIPSECSRVVPN": user "admin" connected ... with address "172.20.0.33" 23:45:45 last log line; next boot starts 23:46:45 (mt_wdt: SoC power status: software reset) Crash dump (/proc/mtdoops/ndm, attached) Program : ndm Reason : segmentation fault Thread : Event sender Fault address: 0x00000000000000c8 (x0 = 0, i.e. null this) Vpn::Firewall::OnVpnClient(const Event::VpnClient&)+0x0 (/lib/libndmVpn.so+0xf920) Event::Sender::Run()+0x258 (/lib/libndmBase.so+0x9e578) Thread::StartRoutine_(void*)+0x2ac (/lib/libndmBase.so+0x126cac) Likely related Alpha 11 changelog: "fixed routing between IKEv2/IPsec VPN Server clients and networks behind other VPN connections". The handler is called with a null Vpn::Firewall (x0 = 0). Enabling the IKEv2 server as well does not prevent the crash. Workaround Use the WireGuard server for remote access. Self-test available on request.ndm_crash_alpha11_2026-09-29.txt
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.