I have problem with ROS v3.24 x86. Seems it is a bug in v3.24.
Please try this…
First:
Add any subnet IP Address in your ether. (/ip address add…)
Second:
Disable that IP Address you made for 10 seconds, then enable it again.
And wait 10 seconds…then Disable that IP Address you made for 10 seconds, then enable it again.
And wait 10 seconds…then Disable that IP Address you made for 10 seconds, then enable it again.
Third:
See inyo your IP Route list, then you will see 3 Dynamic IP which you disable-enable 3 times.
Because of this, some of my network which belong to that IP Subnet is down.
Please anybody try it. Is this only happend to me or to all of you.
Regards
PS:
This bug does not happen with my RB411A. Just happen with x86. I try it with 2 of my x86 system.
I am able to semi-repeat this on our X86, 3.24 Routing-Test. I was able to get the routing entry to show up twice. One of them being a stale record that would not update.
I think the easier test is though.
BUG: When you disable an IP address, the route still shows up in the routing table.
Got the same problem here, but it looks like the bug is just with 3.24 and winbox because
if I use print command thru a terminal window route table is correctly.
To reproduce that, configure any dynamic protocols and let routes go down e up some times.
I was using 3.24 with routing-test package and configuring BGP routes with VPNV4.
I am using YUJOBIKA’s steps to recreate. Enable IP, wait 10-15s, disable IP (route will still be in winbox), wait 10-15s, enable IP(new identical route will appear in winbox), repeat. It appears to be a winbox issue though. Through CLI it is correct.
-Louis