RouterOS 3.0 VPDN?

RouterOS General
1

Bell Canada uses the following model for reselling its DSL high-speed service:

  1. Customer establishes PPPoE connection to local Access Concentrator (LAC).
  2. LAC forwards customer session in form of L2TP session over established L2TP tunnel to L2TP Network Server (LNS) on reseller’s network.
  3. Reseller’s LNS authenticates customer session via radius, and assigns connection information (IP, DNS, routes, etc) to the customer session.

The end result is the customer’s connection appears to terminate directly on the reseller’s network, with Bell’s intermediary nodes being transparent.

My question is, will RouterOS 3.0 support this kind of VPDN configuration, as either the LAC or the LNS?

I work for a small ISP which both resells Bell’s high speed service and wireless access. I would like to utilize Mikrotik systems to build a wireless access model which mirrors that of Bell’s wholesale DSL services. IE:

PPPoE_Client->CPE->AP->Mikrotik_LAC->Routed_Infrastructure_Cloud->Mikrotik_LNS
<-----------PPPoE----------><--------------------L2TP----------------------------->
Remote_Client_IP<------------------------------------------------------>Local_Router_IP

2

Resurrecting this one from the dead; does RouterOS support, or any plans to support, LAC/LNS VPDN connections?

3

Have added as a v4 feature request, please vote on it http://wiki.mikrotik.com/wiki/MikroTik_RouterOS/v4/Feature_Requests

4

Currently the feature is not support. It might be that support will be added in the future for it.

5

That would be fantastic if it could be sergejs.

From what I can tell people have been asking for it since early in the 2.9 series of releases.

6

Any updates on this request?

7

We’re also waiting for this … so we could replace a lot of Cisco Routers by MT if VPDN would be possible …

8

This is a feature which would be extremely useful, I currently have to resort to using cisco devices to accomplish this which is a shame, as they are much more expensive and use more power too.

9

I check back periodically to see if there is any progress on this functionality. This is the last feature required before our company (and many others, it seems) could fully replace all Cisco devicese in our infrastructure with Mikrotiks. We’re a little disappointed this hasn’t been implemented…it seems like a relatively quick-win for Mikrotik.

10

Indeed, this would be nice. However, I don’t think Mikrotik is even working on it. So it’s back to Cisco for LAC functionality.

11

We’re all still waiting.

12

Time for our update pleading that this happen!

13

Still waiting…

14

We are waiting for this too…

15

What are you all waiting for :slight_smile: ? Did you send this question to support ?

16

I assume you read the whole thread, so you know we’re waiting for LAC functionality.

Do you have some news on current developments in this direction?

17

I don’t think anyone ever requested this at mikrotik. This is just a user forum, it’s easy to miss these threads.

18

We could try to add support for it, but we would need testers

19

Well, in this forum you can find testers, I’ll be one of them!

Basic functionality requested:

  1. Respond to PADI requests. These requests are sent by PPPoE - this can be a computer or a DSL router, the request is the same (arriving on the ethernet port)

  2. Inspect the packet, strip the realm and forward to a endpoint (LNS) with L2TP. It would be perfect if the RouterOS could send the realm to a radius server which will answer with the IP address of the LNS.

Most of us now use this functionality on a Cisco router. It works on the 2600 series, but a 4Mbps data flow will drive the processor usage up to 99%. Way better performance is possible with a 7200 series router - and that’s where the money starts.
If you guys can get this functionality going on RouterOS, and performance is fair, this would be a a real competitor for Cisco!

20

We’ll be a tester, too!

(and given sergejs’s response earlier, we’d assumed you guys were aware of the request, but were choosing not to implemented for whatever reason. :slight_smile: