General • Re: Official docs to L2TP-v3 L2TP-ETHER

I Tested this and it works fine, but the issue is that it seems to work better from Mikrotik to Mikrotik.
My test to a cisco 9K failed

Greetings, could you share the meaning of the parameters, please?

Mikrotik is really failing in Documentation. As far as I see, other brands already established in the market, such as Mikrotik, simply release documentation beforehand, or at least a publication on an official blog, etc.

I have noticed, not just in this case now of L2TPv3, but before this already happened, with LTE, with WifiAC..

Grateful for the attention

apologies for the late respond. just have been busy.
so in order to get it to work you have to make it unmanaged. between Mikrotik and Mikrotik.


[admin@MikroTik] > interface/l2tp-ether/print
Flags: X - disabled; D - dynamic; R - running; u - unmanaged
0 Ru name="l2tpv3" mtu=1500 actual-mtu=1500 connect-to=172.18.2.198
mac-address=FE:B7:65:8A:AE:8A use-ipsec=no ipsec-secret=""
allow-fast-path=no l2tp-proto-version=l2tpv3-udp circuit-id="10"
cookie-length=8-bytes digest-hash=none use-l2-specific-sublayer=no
local-address=10.13.55.253 local-tunnel-id=1 local-session-id=10
remote-tunnel-id=10 remote-session-id=1 unmanaged-mode=yes

on the managed tab set the tunnel is and session id. unfortunatly they have to be set they cant be dynamic. your remote and local id have to match especially the tunnel id

the ony way to make it work on with a cisco, is to set the session ID statically. I assume this would the same with other OEM brands too.

l2vpn
xconnect group Mikrotik
p2p cisco
interface GigabitEthernet0/0/1/15.50
neighbor ipv4 10.13.55.253 pw-id 10
pw-class Mikrotik
l2tp static
local cookie size 8 value 0x0 0xffffffff
local session 1
remote cookie size 8 value 0x0 0xffffffff
remote session 1
the only problem I have with the cisco and the Mikrotik is that my end device cant communicate and I am not learning mac

Statistics: Posted by brainlabs — Sat Feb 17, 2024 11:55 am

---