- Direct link route lost bug
Description:
After the interface is configured with an IP address, a direct connection route will be automatically generated in the routing table. However, under unknown circumstances, the direct connection route will be lost, resulting in the inability to communicate with the host in the same network segment. If a static route is added and the next hop points to an IP in the same network segment, the route will turn blue, that is, it will not be in effect
Solution:
If the IP address of this interface is disabled, it will be re configured
Manufacturing reproduction:
It can’t be reproduced
- OSPF filter causes static route not to be redistributed
Description:
After the ospf network is created, static routes are imported into a node, but in order not to publish all the static routes, we can use OSPF filter chain = OSPF_ Out, we need to create a stop all, action = discard. However, when we add the prefix that allows publishing, the routes that want to be published are not published. Of course, we have determined that the items to be published are before discard
Solution:
Disable the OSPF out discard entry, and then enable it
Manufacturing reproduction:
It can be reproduced
- L2TP fault
Description:
The L2TP server or client of the same router may not work normally due to abnormal network disconnection, policy adjustment, disable and re enable. Sometimes it may take a few minutes or hours to recover. At the extreme, the L2TP server and client functions of this router are completely broken. I have a ccr1009 Both 2tp-server and l2tp-client are broken
Solution:
I didn’t find a solution. I also posted a post about L2TP bugs, but I didn’t find a solution. In the LAN environment, the constant disable enable L2TP also failed to reproduce the bug, but it often happens in the Internet environment
http://forum.mikrotik.com/t/a-l2tp-bug-of-ten-years/142954/7
Manufacturing reproduction:
Medium probability recurrence