Hi,

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.

cannot repeat that... do you use routing or routing-test package?

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.

Be sure to e-mail support@mikrotik.com with your issue so it can get resolved.

-Louis

I just sent email to Mikrotik. Hope will be solve in the next version.

Thanks

@Chupaka

Yes I activated routing-test because I need to try BGP.

Thanks

Mikrotik support reply as follow:


Hello Adam,

The problem should be fixed in the next 3.25 version.
At least I'm not able to reproduce it the same procedure as you provided us.


Regards,
Sergejs

Letni,
Did you use the same commands sequence on the router ? Do you have anything specific on the configuration ?

Packages:
advanced-tools
calea
ntp
routing - Disabled
routing-test
system

Intel Xeon 2.1Ghz
multi-cpu: yes
2G RAM
6 NIC: 2 onboard (intel), 1 RB44G

I have been using the box to test some BGP configurations and SMP stability.
-Louis

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.

Could you verify that the same problem is present on the CLI, when /ip route print ?

What are exact steps to reproduce the same issue, as I have tried YUJOBIKA steps, as Winbox as Console display correct routes.

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