I upgraded routerboot last night on a ~6 month old RB112 which seems to have broken its ability to connect to Ethernet. Is there a way around this problem? I can reach it via radio, and when connecting ethernet the link light blinks on for aproximately 2 seconds then goes out...

Tested with a switch and two laptops... same results.

any advice? Alternative involves a 150 ft (45m) tower climb on a saturday evening, and that sounds expensive...

Same unit shows 2%-100%-2%-100%-2%-100% CPU load in winbox.. every other refresh shows 100%.

when did the ethernet stop working? Sounds like a hardware problem.

when did the ethernet stop working? Sounds like a hardware problem.

The ethernet quit when I upgraded routerboot on the unit. '/system routerboard upgrade' then rebooted... never came back. 900 radio kept working. This was my first unit I ran /system routerboard upgrade from within 3.2. Since then I've downgraded all the units I've upgraded back to 2.9.50 before doing the routerboot update.

I attempted downgrading it back to 2.9.50 via radio, which did not bring the ethernet back and disabled the SR9 (normal for the 3.x -> 2.9 downgrade, it was a long shot...)

We're going out within the next half hour to swap the 112 in that unit with a 411 w/ L4 (this is a single-card SR9-based AP). I'll know more when its in my hands.

Is there any compelling reason to update the firmware if everything is working OK to begin with?

Is there any compelling reason to update the firmware if everything is working OK to begin with?

Who said it was working OK to begin with?

I've been chasing a random wireless client disconnect problem with MT gear for over a year. Also, unless you've got a good 40 dB SNR, AP+WDS isn't exactly what I'd call reliable. 3.x (3.2 especially) is considerably more reliable on the wireless end of things, its just the upgrade procedure thats broken (IMHO) at this point.

The only ways I can see MT correcting the routerboot problem:

add a checkpoint to the installation script to ensure the routerboot. You could handle it two ways after this:

A> just flash it and move on with life

B> stop the rest of the installation from occurring (similar to loading the wrong architecture to the routerboard)

Either way, I see this situation easily correctable. It'd also help if MT didn't 'misrepresent' very experimental builds as 'stable releases'. I don't consider 3.x 'release quality' by any means, and I can't understand why MT rushed the release other than to be able to finally ship their 3.x-only hardware without telling their customers all they have available is 'release candidate' firmware.

As to answer the original question: I upgraded the routerboot because the unit would no longer recognize its installed SR9 after the 3.x upgrade.

Ah, I wasn't aware routerboot did more than just initialize hardware and boot.

I agree with the 3.x sentiments though, it does feel rushed and the people who deploy it in production are really just filling in for the lack of testing it got under beta / RC.

Please send us a supout.rif file and also write what routerboot version you had before.
note that you can downgrade the firmware via FTP if you wish. just email support and i will send you the version of your choice, if you are REALLY sure that it's the RouterBOOT that caused the ethernet problem

we just tested a very old RB112 and did the same things you did - there is no problems with the etherner after upgrade to 3.2 and then upgrade the RouterBOOT from 2.1 to 2.12

I have some issues with my 112 that was upgraded from 2.9.50 to 3.1, then to 3.2

I have a XR5 card in this rb112. The signal was great before (on 2.9.50) -70 DB with 95 % CCQ, when I upgraded to 3.1 and even on 3.2 the singals are roughly the same, but the CCQ dropped down to 25 - 40%. I can run bandwidth test from the AP, being a 532A running 3.2 and with an XR 5 card as well, and the SEND test from ap to 112 gets 150k/s, where the recieve rates get up to 8 - 9Mbit. I have another RB 112 but it has a R52H and running 3.2 connected to the same AP ( also in WdS bridge mode/Station WDS) and I get the same transfer rates as I did before the upgrade from 2.9.50, and but the CCQ dropped to 70% recieved, and 50 - 60 % transmitted (On the RB 112)

I thought the alignment may of gone out, so I checked that. Its at its best signals, and the antenna's never moved.

I wish I could of downgraded back to 2.9.50, but it can't unless you Netinstall, and that is alot of work!

There has to be more bugs then we are told of. I used to be able to watch live tv over the RB112 from a media center extender, now I can barley read text e-mails since its so slow.

To be honest, I thought it was another RB 532A that had an upgrade issue that did not reboot properly, and I thought the two radio's were brodcasting junk/noise and I though that would of been a source of interference since the antenna's were facing the right way to each others stations, but I have since pulled down that RB532A and it is on my desk, and off, and the other links have problems. I have no clue what is going on, but there is tooooomany problems with 3.x so far.

Not a happy camper.

I have some issues with my 112 that was upgraded from 2.9.50 to 3.1, then to 3.2

I have a XR5 card in this rb112. The signal was great before (on 2.9.50) -70 DB with 95 % CCQ, when I upgraded to 3.1 and even on 3.2 the singals are roughly the same, but the CCQ dropped down to 25 - 40%. I can run bandwidth test from the AP, being a 532A running 3.2 and with an XR 5 card as well, and the SEND test from ap to 112 gets 150k/s, where the recieve rates get up to 8 - 9Mbit. I have another RB 112 but it has a R52H and running 3.2 connected to the same AP ( also in WdS bridge mode/Station WDS) and I get the same transfer rates as I did before the upgrade from 2.9.50, and but the CCQ dropped to 70% recieved, and 50 - 60 % transmitted (On the RB 112)

I thought the alignment may of gone out, so I checked that. Its at its best signals, and the antenna's never moved.

I wish I could of downgraded back to 2.9.50, but it can't unless you Netinstall, and that is alot of work!

There has to be more bugs then we are told of. I used to be able to watch live tv over the RB112 from a media center extender, now I can barley read text e-mails since its so slow.

To be honest, I thought it was another RB 532A that had an upgrade issue that did not reboot properly, and I thought the two radio's were brodcasting junk/noise and I though that would of been a source of interference since the antenna's were facing the right way to each others stations, but I have since pulled down that RB532A and it is on my desk, and off, and the other links have problems. I have no clue what is going on, but there is tooooomany problems with 3.x so far.

Not a happy camper.

please make a supout.rif file and send to support, maybe you have overdriven the wireless card or there is some other settings issue.

Actually I was going to post an update to my own post.

The ONLY thing I did was download 3.2 again, and upgrade that single 112 board. THis seems to fix the problem of the dropped connection, but the CCQ is still quite low, but still a little higher then what it was before.

The settings are still all defualt, defualt power etc. To be honest with you that one particular XR 5 card was originally bought when they forst came out, and there was NO mention anywhere about the 10 DB ofset. The card was set at 23 DB for a few months ( This is back early 2007) I then found that documentation of the 10 DB offset, and then changed it to defualt. At the time that XR 5 was in this same RB112, and running all versions up to 2.9.50 and had near perfect CCQ all the time. but literally, after the upgrade was when there was issues.

Is it possible that this second time I downloaded the 3.2 was actually a different one? Was there any changes made, but not considered a new release?

Crap -forgot to update this thread after our tower climb.

The problem ended up being the cat5 cable itself - that tower had taken a lightning strike (I was about 60m from the 45m tower at the time, *very* impressive thunder) a couple months ago and apparently some of the surge current decided to hop 'through' the cat5 - there were stiff spots and a couple spots with burned through insulation *BUT* the problem only shows up on newer routerboot versions.

Installed a tri-slot 133 in the same location, preupgraded to 3.2 and modern routerboot. Same scenario. An ancient non-upgraded 2.9.38 RB112 came up and moved data (but not very quickly/smoothly) over the wire. Very weird stuff.

We replaced it all with gel-filled cat5e, hung properly (I hope!). We'll see how this works (or if my power box at the base of the tower eventually ends up half full of ickypick as gravity does its natural thing.

I'm still having some other problems, mostly SR9 interfaces being intermittantly hidden after reboots... There doesn't seem to be a pattern to this problem, so far.

Had similar problem on RB133C, auto-upgraded from LAN side so I don't know if wireless was still working.
Power-cycled 5-10min after upgrade made it come back up working 100% with 3.3 installed.