Answer the question
In order to leave comments, you need to log in
What is Mikrotik missing for l2tp stability?
Five years have passed since I met Mikrotik. Built many local networks on this equipment. Thousands of devices faithfully serve 24/7/365. but approximately 1% of this vendor consistently refuses to work stably.
The l2tp clients on Mikrotik just stop working. Rescues of course RoMON - where without it. In Mikrotik technical support, they spread their arms and recommend Netistall, which you will agree is not always convenient, especially if the equipment is located in Murmansk, and you yourself are in Turkey.
Numerous thematic chats in Telegram do not answer the question whether everyone or almost everyone recommends Netinstall. Unfortunately, at a number of objects we have to refuse in favor of other equipment - and it's very annoying that there is not a single intelligible manual on how to defeat this Mikrotik glitch.
I sincerely believe that the Toster community will not ignore this annoying problem and the collective mind will solve the problem. I will be immensely glad to comments and advice.
Answer the question
In order to leave comments, you need to log in
In places where it falls off, is it not 2 Internet providers?
There is such a bug where there are several networks on Mikrotik and each has its own Internet. Sometimes, after a Mikrotik reboot with a client (light, update, technical work), such a problem occurs.
It is treated with a small crutch - there are 2 ip for l2tp on the central gateway, when this happens - I switch to another ip in the client settings. Appeared again - back to the first.
Also, if the situation is like mine - in such cases it helps to reduce the likelihood of a problem - allow multiple connections on the server in a pre-created connection. The problem becomes less frequent, but, unfortunately, does not disappear.
Google once, I found that in my case they know about the problem in Mikrotik, but they are in no hurry to solve it (I don’t know how accurate the info is)
According to my observations, ipsec is to blame, after the release of a number of updates, by the way, there were also clients. By the time, approximately when PPTP was cut out of OSX.
And on Linux they updated the encryption protocols and 3des stopped working.
Since then, I have noticed tangible problems.
Now there is a "working" mole with version 6.40.5 on the telera platform, if I update, ipsec will "break", followed by l2tp. This is not a call for firmware for older versions, do not try to repeat it in production! Such old firmwares have a bunch of CVEs! But ipsec works :)))
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question