Just posting AFTER finishing my download of that - not to get into the crowd jumping to poor MikroTiks’ webserver
…
Best regards,
Christian Meis
Just posting AFTER finishing my download of that - not to get into the crowd jumping to poor MikroTiks’ webserver
…
Best regards,
Christian Meis
BEWARE:
Updated a home AP (RB532) and rebooted
Device came back without an IP address. Had to reconfigure, starting with MAC-telnet
Reason: my interfaces were bridged (ether, wlan) and 2.9.9 has a new way of setting up bridges.
Be careful upgrading any routers that are “live”.
Regards
PS changelog:
What’s new in 2.9.9:
*) removed write-sect display from RB500 version. it is not supported on
this version and was showing zeros;
*) changed bridge configuration approach;
*) improved handling of arbitrary characters in console completions;
*) fixed check-gateway in routing-test;
*) improved Simple Queues in WinBox;
*) allowed bypassed hotspot hosts to talk directly with each other even
if address-pool is set for hotspot server;
I asked about an issue with bridge vlans. When I bridge my ethernet interface, bridged vlan interfaces stops working.
What is the nature of this change ? The changelog isn’t clear enough for me …
I’m curious to know if you had the IP address assigned to the bridge, wlan or ether? Wonder if that would even matter? I would hope that if you assigned the IP address to the “reachable” interface before upgrading that address would remain on the interface. If this is the case then you could at least reach the unit and rebuild the bridge.
Stephen, you got a minute to chat on Skype?
Best,
Brad
I upgraded a RB500 2.9.7 to 2.9.9 and I lost the IP address on ether1. Had to connect with winbox via MAC address. Remove IP address and resetup, still no good. I reconfig the IP address for the ether2 and it works : ![]()
Hi Brad,
Yes our default “out of the box” config is bridged with a single IP address on the bridge.
Putting a separate IP address on the ether port should have made it easier to recover, but the bridge function would have been lost, which is not helpful. Not sure why you lost the IP on the interface, Matt. I will try to investigate this.
MT: strongly suggest you put some “release notes” against each version, or open a WIKI section for known issues.
This version upgrade is going to be a big “bump in the road” for unaware users…
[Brad: welcome to talk in Skype, drop me a mail to say when etc. ]
Regards