i try to connect using l2tp3 client on 7.19.6 to sever on mikrotik 7.19.6 and constantly get on client "v3 packet is not accepted by server configuration, drop" but server log say that all ok.
If try to use l2tpv2 then all works ok. Is it broken ?
Hey,
Yeah, it looks like L2TPv3 is broken in 7.19.6. The “v3 packet is not accepted by server configuration” message happens even when both sides are on 7.19.6. L2TPv2 still works fine, so it’s likely a bug. Try downgrading to 7.18.5 or wait for the next release where they fix it.
Support confirmed that it is broken but they not plan to fix it.
PS: Basically if was told by Oskars K. support representation . As for me he quite often not undertand about what he say. So i suggest to create another tickets untill it will go to somebody else more skifull .
can we get export file?
client
/interface l2tp-ether
add allow-fast-path=no circuit-id=12 connect-to=server_ip cookie-length=0 digest-hash=sha1 disabled=no l2tp-proto-version=l2tpv3-ip
mac-address=FE:30:0D:3D:04:3C mtu=auto name=l2tp-ether1 use-ipsec=no use-l2-specific-sublayer=no
server :
/interface l2tp-server server
set accept-proto-version=l2tpv3 default-profile=l2tp_in enabled=yes
l2tpv3-circuit-id=12 l2tpv3-digest-hash=sha1 max-mru=1300 max-mtu=1300
and on client you will see :
2025-12-12 13:43:22 l2tp,debug v3 packet is not accepted by server configuration, dropping
2025-12-12 13:43:22 l2tp,debug v3 packet is not accepted by server configuration, dropping
i'm experiencing the same, have you tried unmanaged-mode ?
The way you're doing it, I honestly can't see anything wrong. In some V7 versions, it worked really well, unlike the new one (v7.20.4).
unmanaged-mode has never disappointed me so far.