hello

I have a RB133 in a mountain, I upgraded from rc6 to rc8 and I lost access to the equipment connected in the Ethernet ports.

I have access to the equipment through a wireless interface of the RB133. the equipment connected to the Ethernet ports are a couple of RB500. I had access to the other RBs by using one unused wireless interface, then I rebooted the RBs and nothing, I still have no access, just by wireless.

The weird thing in the RB133 I got the message LINK OK, but in the RB533 i got the message NO LINK, I tried to change Ethernet settings like speed but nothing.

I think there is a problem with MT because I have another RB133 with RC7 unable to talk to another rb133 with RB2.9.46, Of course all of them have the last routerboard firmware.

What is going on?

I have the same problem with RB333 and RB44G

I too had a problem this morning when I upgraded to 3.0rc8. I could get in to our RB333 thru the ethernet end. Luckly I have only one client on that AP. He called and said he could not get on the internet thru the Wireless end. I down graded to rc7 and all is working for now.
Mike

please make the support output files when you see this problem and send it to support@mikrotik.com as we jave tried to upgrade RB133,RB333 and RB44G and they are working fine with Ethernet on v3.0rc8.

Uldis,

To reproduce the problem, set the interface speed to 10mbps and disable auto-negotiation
Now make sure the other end of the Ethernet link is set to auto-negotiation.

Uldis,

To reproduce the problem, set the interface speed to 10mbps and disable auto-negotiation

Code: Select all

set ether1 auto-negotiation=no disabled=no full-duplex=yes speed=10Mbps 

Now make sure the other end of the Ethernet link is set to auto-negotiation.

On which board and which ethernet port?

Uldis,

To reproduce the problem, set the interface speed to 10mbps and disable auto-negotiation

Code: Select all

set ether1 auto-negotiation=no disabled=no full-duplex=yes speed=10Mbps 

Now make sure the other end of the Ethernet link is set to auto-negotiation.

But as fas I know - you ether use auto-negotiation in both ends ir not use auto-negotiation at all.

Auto-negotiation must negotiate only proper speed (10Mbps,100Mbps, 1Gbps) in half duplex mode - it is from RFC, it will never get you 10Mbps full duplex for example.

On the RB333, set the ethernet interface speed to 10mbps and disable auto-negotiation.

The "ethernet interface" here refers to the interface you have used to connect the RB333 to your lan.

Look at a situation where you have RB on a 80m tower connected via cat5e ftp cable to a switch on your network. Because of the length of the cable, you need to force a speed of 10mbps on the ethernet link. The only way to force 10mbps is to specify it on the RB. This works on ROS2.9.xx but not in 3.0RCx

On the RB333, set the ethernet interface speed to 10mbps and disable auto-negotiation.

The "ethernet interface" here refers to the interface you have used to connect the RB333 to your lan.

Look at a situation where you have RB on a 80m tower connected via cat5e ftp cable to a switch on your network. Because of the length of the cable, you need to force a speed of 10mbps on the ethernet link. The only way to force 10mbps is to specify it on the RB. This works on ROS2.9.xx but not in 3.0RCx

RB333 and RouterOS 2.9???? - I see something wrong here

On the RB333 we tested with ROS3.0rc6 to ROS3.0rc8 while on the RB532 we tested with versions 2.9.xx and 3.0rcx.

This problem exist on RB333 and RB532 when using ROS3.0rcx but it does not exist on RB532 running ROS2.9.xx. We couldn't test RB333 with ROS2.9.xx because RB333 can only run on ver 3.0 and above.

Uldis, were you able to reproduce the issue?

It happens with RB133c too. Basically, the downstream degrades to less then 200 kbit. Downgrade back to rc6 or 2.9.x and everything is back at 10 mbit/s.

supout.rif send to support.

/Martin

Same problem here...2.9.48 to 3.0rc8 and the ethernet is gone. I will have to go to the location and try the wireless card....

Definitely reproduceable... rc8 for 133 boards is no good on the POE interface. Huge quantities of lost packets when flood pinging that isn't there at rc7. Downgrading to rc7 fixes all. A huge step backwards.

Upgraded to rc9 and it fixed the problem with slow ethernet port on 133c

Can't get onto MT download site to download rc9. MT website has been slow for several days - anyone else seeing this? Forum and wiki domains are OK though..

The issue was resolved in ver 3.0rc9. Many thanks to the mikrotik team.

While the issue had disappeared on RB333, it appears there is still a little problem with RB150

I set ether1 to 10mbps and disabled auto-negotiation as shown below.



I checked the status of ether1 and it shows auto-negotiation disabled and link speed as 10mbps.



Now I reboot the router and checked the status of ether1. Auto-negotiation is ON and link speed had reverted to 100mbps. See image below.

this will be fixed in the next release. for now, you can disable/enable the ethernet interface and it will work corretly as you have configured.