Hi,

I want to have clients coming in from adsl into our core with l2tp or pptp to our mpls cloud where we can put them into diffrent vrf's

I can put the l2tp-client1 into a vrf, but as it reconnect the vrf interface is unknown, is there a way MT can pick up the l2tp interface on reconnect?

Thanks

S

I haven't tried it, but you should be able to add a bridge and add your dynamic interfaces to it, and add that bridge to the vrf instead. That should make it work...

Thanks

Tried adding the lt2p interface to the bridge, doesnt seem to be possible

S

you can't add l2tp interface directly to bridge.

Instead in /ppp profile specify which bridge to use when l2tp interface is created. Also note that l2tp interfaces must be bridged on both ends, otherwise it won't work.

I've been testing my vrf's with dynamic interfaces and works beautifully, i need this for a client with 60 sites coming in on 3g and their main co-located server with us,

i however using scripting to keep the interfaces in the vrf up peroidlicy buts it very ugly, is there no way MT can remember the dynamic interfaces ? is this a coding limitation on MT side or something?

when u set your client 3g routerOS to gateway=pppoe-out1, it remembers it, what so diffrent from the dynamic interfaces on the l2tp-server side?

If this works, its pretty much on par with how cisco mpls providers does it

S

any news from anyone how i can do it better? I can l2tp to the client and it remembers the interface in the VRF but 3g clients i can't connect to as their ips not visible on the internet

Thanks

S

hi,

i´am struggling with the same problem this moment. it would be great if there were a radius-attribute like 'Mikrotik-VRF' or 'Routing-Mark'

is this planned for the future?

Clemens

is there no way MT can remember the dynamic interfaces

Don't use dynamic interfaces
You can create static l2tp-server interfaces for each client (or copy a dynamic one) which will stay there.

I also vote for the radius-attribute like 'Mikrotik-VRF' or 'Routing-Mark'. We need it for PPPoE.

I also vote for the radius-attribute like 'Mikrotik-VRF' or 'Routing-Mark'. We need it for PPPoE.

+1

You could always add a routing mark using a mangle rule and match on the IP range or ranges that are being handed out for the dynamic connections.

If done in prerouting, that should keep you from having to script it.