I thought I’d read a note that they’d gotten the upgrade problem fixed, but it’s still causing problems. I took a router with a very basic config, it’s a backhaul link. There is one bridge with one ethernet and one wds interface in it. After upgrading to 2.9.12 as a test, I managed to get back into the router and found that I now had two bridges, both had the same name as the original bridge but had different MAC addresses. Under ports, the ethernet port’s bridge had changed to “unknown”, the wds interface was still the bridge but there was no way to tell which one of the two duplicates it was.
Beware upgrading if you’ve got bridges defined, the configuration conversion to the new style still isn’t working right.
No, the correct answer is “fix the config conversion so that it doesn’t break things”. I got lucky with the unit I was working on, there was a secondary way to access it remotely that I could use to get into it and fix things. Most people would end up climbing the tower to swap the radio or reprogram it, and that’s unacceptable.
A software upgrade should “do no harm”, especially within the same major version of software.
I have been doing a lot of testing with 2.9x and need to upgrade one of my working 2.8.28 AP’s. The one I’m going to upgrade only has three customers on it.
The only thing is, on that unit I have two radios in a bridge, simple queues and routes. I’m thinking something is going to furk up.
What do you think?
I’d have to agree, it’ll probably be fracked royally by the upgrade. I’d probably build a replacement radio that was programmed correctly and swap it with the existing unit, rather than try to upgrade the existing one in place, if I had the hardware available.
Hey, we upgrade about 30 AP-RB from 2.9.8 and 2.9.11 to 2.9.12, and the only thing that happended was that in bridge ports was 1 or 2 “unknown” ports, but the bridge does not frurk up… And of course the bug must be fixed… … Just my experience..