Torontobob, MTU can be troubleshot with the ping command line utility. You set a size along with the DF bit set.I do have an issue with not being able to browse all sites and my provider says it's an MTU of 1622 on the interface but is not sure about VLAN2020 and L2TP tunnel. I am assuming I am having an MTU issue so how can I go about proving this is the issue and setting the proper MTU?
ping -4 -f -n 2 -l 1472 184.108.40.206
Pinging 220.127.116.11 with 1472 bytes of data: Reply from 18.104.22.168: bytes=64 (sent 1472) time=31ms TTL=46 Reply from 22.214.171.124: bytes=64 (sent 1472) time=30ms TTL=46 Ping statistics for 126.96.36.199: Packets: Sent = 2, Received = 2, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 30ms, Maximum = 31ms, Average = 30ms
Pinging 188.8.131.52 with 1482 bytes of data: Packet needs to be fragmented but DF set. Packet needs to be fragmented but DF set. Ping statistics for 184.108.40.206: Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
/ip firewall mangle add new-mss=clamp-to-pmtu ...
update: sorry, only Mikrotik as LNSCan anyone post a working config for using a Mikrotik as an LAC to a Cisco LNS?
I realise this isn't currently feature ready.
/ip pool add name=pool-dsl ranges=10.50.50.100-10.50.50.200 /ppp profile add change-tcp-mss=yes dns-server=220.127.116.11,18.104.22.168 local-address=10.50.50.255 \ name=dsl_ppp only-one=no remote-address=pool-dsl use-compression=no \ use-encryption=no use-ipv6=no use-mpls=no use-upnp=no /interface l2tp-server server set authentication=pap,chap default-profile=dsl_ppp enabled=yes /ppp l2tp-secret add add address=xxx.xxx.xxx.xxx secret=L2LTSHAREDSECRET
Hi there,I can confirm that MikroTik works with L2TP/LNS/LAC fully and as expected.
I do have an issue with not being able to browse all sites and my provider says it's an MTU of 1622 on the interface but is not sure about VLAN2020 and L2TP tunnel. I am assuming I am having an MTU issue so how can I go about proving this is the issue and setting the proper MTU?
They can't also tell me anything if they are using L2 MTU or not. This is Bell Canada by the way. Here is my settings:
Torontobb, you mind sharing your email contact? I have a few questions, wondering if you'd be kind enough to help us out.Yes, we got it done and working well. Quiet a bit of work though. However, I can confirm it works.
Hey thereHey sorry I was not watching this email.
I can post our configs here once you ask your specific questions.
How many users are going to support and what model of MT are you using?
Back to waiting for v7...LAC feature is moved to RouterOS v7 as new Linux Kernel will make implementation much more easier, so currently LAC is not supported. Sorry.
Regards v7, yes, we are working on it, no dates atm.
Hi NTB.Sorry to pitch in on a 10 (yes 10!) year old thread but can Mikrotik give us ANY indication of v7 or LAC function being implemented?
/ppp l2tp-secret add address=22.214.171.124/29 secret=12345
/interface l2tp-server add name=l2tp-in1 /interface l2tp-server server set allow-fast-path=yes default-profile="Customer PPPoE" enabled=yes max-mru=1500 max-mtu=1500
ATM I've been playing with a couple of virtual instances of bsdrp followng the example below and using a CHR instance to generate 50 pppoe client connections. Is anyone able to share a working Mikrotik LNS configuration please?
default: load simple_lac
simple_lac: # # This is a simple L2TP access concentrator which receives PPPoE calls # and forwards them to LNS on 126.96.36.199 # create link template L1 pppoe set pppoe iface fxp0 set link action forward L2 set link enable incoming create link template L2 l2tp set l2tp secret freebsdlac set l2tp peer 188.8.131.52