I’m looking forward to be part of the test aswell!!! 
ok, thanks. we will let you know if we need your help. at first we have to make something, to be able to test it. it’s not the highest priority project though.
Hi there,
yes LAC/LNS functionality would be a great addition to RouterOS!
If ppl for tests are needed I could stick together a Routerboard with a cisco LAC/LNS.
Glad to get to see some response on this. I can also setup a test environment to test this if needed, i have an extra cisco around i can use for testing. Would be nice to eliminate the cisco router in the network that only has 1 purpose to terminate the L2TP connections from the phone company.
Is the LNS/LAC feature any closers yet ?.. Fingers crossed 
Hope so, been running into problems with current configuration of cisco, want to eliminate it from the network. Especially so as will be moving the data center and making new router.
Performance problems?
Want to be able to better control DSL customers, also getting more and more customers we are providing subnets to for hosting their own content, they are normally connected by DSL as a backup and wireless as their primary link. And have automatic failover.
It’s slightly off-topic, but adding subnets can be handled by the LNS: add a Framed-route in the radius account configuration and tell the LNS to propagate this route into the routing protocol.
The LAC won’t be aware of any subnets, nor needs to be, as it’s just switching packets between layer-2 and a L2TP connection.
Since MikroTik is not showing any signs of progress, I’d like to suggest a software option: mpd5 and FreeBSD.
I have installed FreeBSD on a machine, added the mpd5 software package (all opensource) and configured it as a LAC. The performance is amazing! For those of you looking for Cisco alternatives, give this combination a try. I’d like to test more, but my network isn’t large enough. Sofar, the box handles a throughput of over 40Mbps and the cpu is still 99% idle.
FreeBSD can be configured to use 802.1q VLANs, the LAC can be setup using only 1 ethernet interface. If anyone is going to give it a try, I’d like to hear some results on performance. The user-comments on the web are sparse (and mostly in Russian).
mpd5 is open-source, so maybe it’s interesting for MikroTik to have a look into the source code?
Where did you find config information for MPD5+Radius+FreeBSD? The pkg docs are not very helpful (and as you note, most information is in Russian).
Could I contact you privately?
PM function doesn’t work for me on this board, but the discussion of MPD5 might be interesting for others as well, although slightly off-topic.
I tested with a very simple LAC configuration, which receives PPPoE connections from DSLAMs over two 802.1q VLANs, and then forwards these to a Cisco LNS:
mpd.conf
default:
load simple_lac
simple_lac:
# L1 receives PPPoE calls from vlan2 and forwards them to L3
create link template L1 pppoe
set pppoe iface vlan2
set link action forward L3
set link enable incoming
# L2 receives PPPoE calls from vlan10 and forwards them to L3
create link template L2 pppoe
set pppoe iface vlan10
set link action forward L3
set link enable incoming
# L3 sets up an L2TP connection to the LNS
create link template L3 l2tp
set l2tp self 172.25.31.10
set l2tp peer 172.25.31.4
set l2tp hostname LAC
set l2tp secret cisco
set l2tp enable length
I haven’t tested radius yet. The FreeBSD version I used was straight from CD, no kernel recompiling (yet), only installed MPD5 from the ports collection and configured the ethernet interface for 802.1q VLANs (which is supported in the default kernel).
Have a look at the documentation and man pages included with the package, use the debug function on the Cisco router and you’ll figure it out!
This 7 year old thread deserves a bump.
Oh yes. we’re still waiting for it …
If there is RouterOS support for LAC/LNS, I would use it too (actually it’s running on cisco).
bump…still waiting on this
me too 
Hi All,
Old Thread, just thought I’d bring it back to life. I was a little worried as I was setting my Mikrotik up as an LNS without doing the appropriate Background checks, just figured it would work as L2TP server why not..
Anyways, good news is it works. I’m now terminating DSL into my existing Wireless Network using RADIUs for auth.
Very happy about that.!
Basically —
Bridge DSL → Mikrotik PPPoE Client → user@myrealm.co.nz → L2TP on VLAN to my CCR → Auth via RADIUS and IP assigned → Off to world.
Had to set MTU to 1452 on the PPPoE Client otherwise wasn’t really getting any routing anything over was too much due to header size.
Happy Camper.
Hi chimaster. I’m not certain this is what other folks on here are discussing. If you are a wholesale partner with a DSL carrier/telco, they will typically forward PPP frames in L2TP tunnels (or something similar) so although the configuration you described is working, that configuration will not necessarily work when dealing with a telco that is providing PPPoE based service and tunneling the frames back to the network aggregation device. You are ‘lucky’ in that you own the DSLAM and have configured it in bridge mode.
+1 for me wanting mikrotik to support LNS/LAC
Bump