Post your export.Has anyone successfully deployed L2TP/IPSec for Road Warrior?
After two weeks of testing I'm giving up
Situation:
1. Central point. Almost default config Mikrotik router (ROS v.:6.10) with NAT'ed LAN behind it.
2. Clients. Win7, iOS, Android behind NAT'ed Mikrotik. All L2TP users and devices are configured to have their own names/passw. There is no situation same username on separate devices.
3. Configuration was made based on this example: http://www.nasa-security.net/mikrotik/m ... ith-ipsec/
Problem:
Any ONE of clients can successfully connect to central point (access remote LAN resources, etc.)
Second client also successfully connects, but then first client stop working (no internet, no ping to remote LAN resources).
If second client disconnects, first client starts working.
Tried to look at l2tp/ipsec logs but with no luck.
IPsec and PPP or L2TP?Post your export.
/exportand then put the output into Syntax tags here.
/interface bridge add arp=proxy-arp l2mtu=1598 name=bridge1 protocol-mode=rstp /interface ethernet set 0 comment=WAN set 1 disabled=yes set 2 disabled=yes set 3 disabled=yes set 4 comment="LAN Switch" /interface wireless set 0 band=2ghz-b/g/n l2mtu=2290 ssid=MikroTik /ip neighbor discovery set ether1 comment=WAN set ether5 comment="LAN Switch" /interface wireless security-profiles set [ find default=yes ] supplicant-identity=MikroTik /ip hotspot user profile set [ find default=yes ] idle-timeout=none keepalive-timeout=2m \ mac-cookie-timeout=3d /ip pool add name=LAN_pool ranges=192.168.0.180-192.168.0.235 /ip dhcp-server add address-pool=LAN_pool disabled=no interface=ether5 name=dhcp1 /ppp profile add bridge=bridge1 change-tcp-mss=yes dns-server=8.8.8.8 local-address=\ 192.168.0.254 name=L2TP_IN_Profile only-one=no remote-address=LAN_pool \ use-encryption=yes use-ipv6=no /queue simple add max-limit=128k/1M name=Zydrunas2_speed_limit target=192.168.0.3/32 time=\ 8h-19h,mon,tue,wed,thu,fri /tool user-manager customer add backup-allowed=yes disabled=no login=admin password="" \ paypal-accept-pending=no paypal-allowed=no paypal-secure-response=no \ permissions=owner signup-allowed=no time-zone=-00:00 /certificate scep client add server=0.0.0.0 /interface bridge port add bridge=bridge1 interface=ether2 add bridge=bridge1 interface=ether3 add bridge=bridge1 interface=ether4 add bridge=bridge1 interface=ether5 /interface l2tp-server server set authentication=mschap2 default-profile=L2TP_IN_Profile enabled=yes \ max-mru=1460 max-mtu=1460 /ip address add address=WAN_IP/24 interface=ether1 network=WAN_Network add address=192.168.0.254/24 interface=ether5 network=192.168.0.0 add address=192.168.0.42/24 interface=bridge1 network=192.168.0.0 /ip dhcp-server network add address=192.168.0.0/24 dns-server=212.59.0.1,212.59.1.1,8.8.8.8 gateway=\ 192.168.0.254 /ip dns set servers=212.59.0.1,212.59.1.1 /ip firewall filter add action=drop chain=input dst-port=53 in-interface=ether1 protocol=udp add chain=input connection-state=new dst-port=500 in-interface=ether1 \ protocol=udp add chain=input connection-state=new dst-port=1701 in-interface=ether1 \ protocol=udp add chain=input connection-state=new dst-port=4500 in-interface=ether1 \ protocol=udp add chain=input connection-state=new in-interface=ether1 protocol=ipsec-esp add chain=input connection-state=new in-interface=ether1 protocol=ipsec-ah add action=log chain=forward content=youtube.com disabled=yes log-prefix=\ youtube.com src-address=192.168.0.0/24 add action=log chain=forward content=.mp3 log-prefix=mp3 src-address=\ 192.168.0.0/24 add action=drop chain=forward content=.mp3 src-address=192.168.0.0/24 /ip firewall nat add action=masquerade chain=srcnat out-interface=ether1 /ip firewall service-port set ftp disabled=yes set tftp disabled=yes set irc disabled=yes set h323 disabled=yes set sip disabled=yes set pptp disabled=yes /ip ipsec peer add dpd-interval=disable-dpd dpd-maximum-failures=1 exchange-mode=main-l2tp \ generate-policy=port-override hash-algorithm=sha1 nat-traversal=yes \ secret=SECRET add /ip route add distance=1 gateway=WAN_GW add disabled=yes distance=1 dst-address=WAN_IP/32 gateway=ether5 \ pref-src=192.168.0.254 /ip service set telnet disabled=yes set ftp disabled=yes set www port=9587 set ssh disabled=yes set api disabled=yes /ppp secret add name=testas password="PASSWORD" profile=L2TP_IN_Profile service=l2tp add name=NAME password="PASSWORD" profile=\ L2TP_IN_Profile service=l2tp add name=NAME2 password="PASWORD" profile=L2TP_IN_Profile service=l2tp /snmp set contact=Name enabled=yes location=Ofisas trap-community=\ public trap-target=192.168.0.64 /system clock set time-zone-name=Europe/Vilnius /system identity set name=Router /system lcd set contrast=0 enabled=no port=parallel type=24x4 /system lcd page set time disabled=yes display-time=5s set resources disabled=yes display-time=5s set uptime disabled=yes display-time=5s set packets disabled=yes display-time=5s set bits disabled=yes display-time=5s set version disabled=yes display-time=5s set identity disabled=yes display-time=5s set bridge1 disabled=yes display-time=5s set wlan1 disabled=yes display-time=5s set ether1 disabled=yes display-time=5s set ether2 disabled=yes display-time=5s set ether3 disabled=yes display-time=5s set ether4 disabled=yes display-time=5s set ether5 disabled=yes display-time=5s /system leds set 0 interface=wlan1 /system logging set 1 action=disk set 2 action=disk set 3 action=disk add topics=l2tp add topics=ipsec /system ntp client set enabled=yes primary-ntp=84.15.121.61 secondary-ntp=212.59.0.1 /system scheduler /system script /tool e-mail /tool graphing interface add interface=ether1 add interface=ether5 /tool graphing resource
Yes, clients are on the same network.Are your clients behind the same gateway using nat-traversal or they connect from different IP?
JF
Thats your problem then...Yes, clients are on the same network.Are your clients behind the same gateway using nat-traversal or they connect from different IP?
JF
If this true, its is very bad.As far as I know there can be only one L2TP/IPSEC tunnel behind the same NATed internet connection.
Works only in case if PPTP helper enabled (Mikrotik). In hotels you cannot configure routers. So in real world it is useless.PPTP works with multiple clients behind same NAT..
If it is 2-3 clients it maybe work around. But when you have 50+ it will not work.If you have multiple static IPs on gateway (L2tp Server) you can make clients connect each to specific static IP.. Yes I know its a stupid work around but it works
Did not tried yet. What is wrong with TCP why all wants UDP?Or you can use OpenVPN via TCP.. it also works for multiple Natted clients..
I tried to google, but could not find SSTP clients for iOS and Androids.Since you need IOS and Droid I am not sure if SSTP will work (I haven't tried that)..
If you want to use OpenVPN on android device you have to root it. It is not a procedure everyone is comfortable with and it can also cause waranty problems with some mobile operators.PPTP works with multiple clients behind same NAT..
If you have multiple static IPs on gateway (L2tp Server) you can make clients connect each to specific static IP.. Yes I know its a stupid work around but it works
Or you can use OpenVPN via TCP.. it also works for multiple Natted clients..
Since you need IOS and Droid I am not sure if SSTP will work (I havent tried that)..
Is mikrotik supports ovpn udp?One more thing I just remembered Mikrotik have enabled IPSEC XAUTH support..
This is on my try list
See here:
http://wiki.mikrotik.com/wiki/Manual:IP ... _Mode_Conf
Also no mention of Droid or IOS support.. For Windows you have Shrew VPN Client..
ON PPTP VPN Passthrough I have good experience (in Europe). Most hotels I stayed at have PPTP contrack enabled (VPN Passthrough) on their Routers/Firewalls.
For OpenVPN udp is faster but tcp is more reliable. Most vendors prefer udp (no transmision control) and thus faster and more suitable for VoIP and Gaming. OpenVPN has its own transmision protocol. But I must say if you have enough bandwidth (upload) on VPN server it should also work with tcp and Mikrotik.
Today received answer from Mikrotik support:I'm interested to see if you get this working.
How to do it correct/best way, if i have ~10 L2TP/IPSEC clients and 5 useable Publik IP-s?If you have multiple static IPs on gateway (L2tp Server) you can make clients connect each to specific static IP.. Yes I know its a stupid work around but it works
If it is 2-3 clients it maybe work around. But when you have 50+ it will not work.
Pushing this thread a little bit... Is there any news from MikroTik? i have looked changelog from latest releases but there aren't fixes for that issue. Can anyone direct me to do workaround to resolve this issue? I really appreciate that!Today received answer from Mikrotik support:I'm interested to see if you get this working.
Currently we are working on a L2tp/ipsec to support more than one client behind nat.
....
Maybe month, maybe a little longer.
i googled a bit but seems like same issue.Still no news.
I solved my RW case with softether.org.
Very powerful VPN server software. Spend 2 days for setting up, but works like a charm. Very flexible. Open Source.
Thank you so much for this suggestion. It is unfortunate that I had to, but I setup SoftEther VPN on a server behind my MikroTik router.Still no news.
I solved my RW case with softether.org.
Very powerful VPN server software. Spend 2 days for setting up, but works like a charm. Very flexible. Open Source.
Has Mikrotik fixed this? I can only have one L2TP connection at a time if coming from the same natted lan.....Has anyone successfully deployed L2TP/IPSec for Road Warrior?
After two weeks of testing I'm giving up
Situation:
1. Central point. Almost default config Mikrotik router (ROS v.:6.10) with NAT'ed LAN behind it.
2. Clients. Win7, iOS, Android behind NAT'ed Mikrotik. All L2TP users and devices are configured to have their own names/passw. There is no situation same username on separate devices.
3. Configuration was made based on this example: http://www.nasa-security.net/mikrotik/m ... ith-ipsec/
Problem:
Any ONE of clients can successfully connect to central point (access remote LAN resources, etc.)
Second client also successfully connects, but then first client stop working (no internet, no ping to remote LAN resources).
If second client disconnects, first client starts working.
Tried to look at l2tp/ipsec logs but with no luck.
generate-policy=port-override
/interface l2tp-server server
set default-profile=default enabled=yes
/ip ipsec proposal
set [ find default=yes ] enc-algorithms=aes-256-cbc,aes-128-cbc,3des
/ip ipsec peer
add address=0.0.0.0/0 exchange-mode=main-l2tp generate-policy=port-override secret=xxx
/ppp secret
add local-address=192.168.61.1 name=xxx password=xxx remote-address=192.168.61.11 remote-ipv6-prefix=::/64
/ip firewall filter
add action=accept chain=input dst-port=1701 protocol=udp
add action=accept chain=input dst-port=4500 protocol=udp
add action=accept chain=input dst-port=500 protocol=udp
add action=accept chain=input protocol=ipsec-esp
add action=accept chain=input protocol=ipsec-ah
No, this is a serverside bug and can be fixed by just changing the serverside.One thing here caught my attention: "ROS 7 will remove the restriction for having more than one L2TP/IPSEC user behind the same NATed network".
My understanding is that the router on the client side (road warrior) side of the equation is the one that cannot distinguish the traffic, not the server side router. Therefore, nothing can be done on the server side to remedy the situation.
Microsoft had the same bug with Windows 2008 R2 server but repaired it:One thing here caught my attention: "ROS 7 will remove the restriction for having more than one L2TP/IPSEC user behind the same NATed network".
My understanding is that the router on the client side (road warrior) side of the equation is the one that cannot distinguish the traffic, not the server side router. Therefore, nothing can be done on the server side to remedy the situation.
Dynamic IP is not a problem and It is not a question to ask here. Mikrotik L2TP/ipsec works very well clients with dynamics IP-s. Problem comes when two or more Windows clients tries to connect from same nated network with same dynamic or static ip.Mrz,
Can you confirm that mikrotik L2TP/ipsec server can't work behind NAT (i.e.NATted by ISP DSL router) when clients (road warriors) have dynamic IP addresses ??
All incoming internet traffic forwarded transparently to MikroTik WAN (that is a LAN for ISP router)And of course, a prerequisite is that you have the ability to manage firewall on your ISP's router and configure port forwarding to your MikroTik...
Mikrotik as L2TP/IPsec client suffers from the same limitation like any other client in terms that it must be the only one connecting to a given server from behind the same public IP address. Rumour has it that some servers can overcome this limitation which Mikrotik attributes to the protocol specification.Hi all,
is this problem related to the Mikrotik as a VPN Server or as a client?
Say for example i want my RouterBoard to act as a client that connects to a remote VPN service,
i want more than one device to use the tunnell simultaneously, not just one!
Thanks for the replies.
Now wait a bit A month ago there was a topic which dealt with that among other things, and Emils has explained that the information about the UDP port on client side NAT is lost at some stage of processing at server side, and from the ESP in transport mode the clients cannot be distinguished from each other. If it can be solved in such a simple way as randomizing the L2TP port at client side, why the client implementation in ROS doesn't have such option yet? That should be ways simpler than modification of the server side handling where you would have to let the remote UDP port bubble to the next processing stage somehow.Some clients can also overcome this problem, by randomizing source L2TP port.
Agreed that it won't help users using their RB as a VPN server but it would be beneficial for the "centralized bypass of censorwall" setups where I've seen numerous requirements to route part of traffic of LAN clients of the RB through a VPN in another country. And it is not a rule that the RBs used this way have public IPs.It is in TODO list, however that will solve problem only if client is RouterOS. But such setups mostly are done where clients are laptops and mobile devices.
It is in TODO list, however that will solve problem only if client is RouterOS. But such setups mostly are done where clients are laptops and mobile devices.
Nailed it,Now wait a bit A month ago there was a topic which dealt with that among other things, and Emils has explained that the information about the UDP port on client side NAT is lost at some stage of processing at server side, and from the ESP in transport mode the clients cannot be distinguished from each other. If it can be solved in such a simple way as randomizing the L2TP port at client side, why the client implementation in ROS doesn't have such option yet? That should be ways simpler than modification of the server side handling where you would have to let the remote UDP port bubble to the next processing stage somehow.Some clients can also overcome this problem, by randomizing source L2TP port.
For @gargiulo5000, this is likely not an option as it is not available instantly, and my suggestion may not be an option too if the "VPN" is actually used for censorship bypass so the VPN server is not his own one.
Can you diagram what you want in a new topic as it seems to be only loosely related to the current topic? I am using a client μTik connected to a μTik AP and was using EoIP connection over that to connect two cAPs to a cAPsMAN running on the AP, and there was no trouble in that. I've migrated to VPLS since then but for no particular reason.Can a mAP be used to tunnel to a Mikrotik using IPIP or EOIP with the mAP letting multiple users in?
I tried this about a year ago but never did get it to work. I think my stumbling point was trying to get the mAP into a motel wifi for the WAN side.
I did it with cap lites, the little hockey puck looking things. I gave them to friends to use for stretching layer 2 for old games.Can a mAP be used to tunnel to a Mikrotik using IPIP or EOIP with the mAP letting multiple users in?
I tried this about a year ago but never did get it to work. I think my stumbling point was trying to get the mAP into a motel wifi for the WAN side.
When digging into something else, I've realized and tested that with Mikrotik as an L2TP/IPsec client, there actually is a way that several these Mikrotik clients hidden behind the same public address could access a remote VPN server. @gargiulo5000 or anyone else, are you still interested?Hi all,
is this problem related to the Mikrotik as a VPN Server or as a client?
Say for example i want my RouterBoard to act as a client that connects to a remote VPN service,
i want more than one device to use the tunnell simultaneously, not just one!
On which sub-topic? "Mikrotik as server for 3rd party clients" or "Mikrotik as a client"?some fix ? any update ?