Firmware v1.1.5 bug reports and comments

[sirhc]

I think you should add more information for VLAN via CLI since the're true bugs and not only missing feature. First, we must not use port range for tagged VLANs, only for untagged VLAN. Also, we must use capital letter to set the tagging mode on the port (T, U, E).

Mike please detail out your requests for v1.2.0 and PM Eric with your suggestion. I know Eric is putting a lot more into the CLI for VLANs in v1.2.0

[mike99]

I already reported thoses problems here :

viewtopic.php?f=17&t=570#p4049

[mike99]

There something wrong with password. I updated from 1.1.0 to 1.1.5 and since then, password is "admin" and I can't change it via WebUI or CLI. It's look like the change is accepted but when I logout/login, it's still admin/admin. I've seen issue with passworrd on several switch with several firmware but can't tell which one. I could send the config if Chris or Eric want to test it.

Edit: I juste reset it but can't do that on production. Still have the config in case somebody need it for debug.

[mike99]

Cosmetic bug on SFP port with STP. Those port always show forwarding no mater what. I tryed to unplug it, unplug SFP module, create broadcast storm, etc.

STP still seem to work since I don't have connection lost with RSTP enabled while pinging a ERL and can't ping it anymore if I disable RSTP.

The topology was my computer VLAN - Ubnt TSPro - Netonix 1 - Netonix 2 - Edgerouter (ping test device).

Edit: I also noted that STP is disabled by default (after config reset). I think it should be enabled by default to avoid possible loop problems.

[Eric Stern]

There something wrong with password. I updated from 1.1.0 to 1.1.5 and since then, password is "admin" and I can't change it via WebUI or CLI. It's look like the change is accepted but when I logout/login, it's still admin/admin. I've seen issue with passworrd on several switch with several firmware but can't tell which one. I could send the config if Chris or Eric want to test it.

Edit: I juste reset it but can't do that on production. Still have the config in case somebody need it for debug.

This is a bug in 1.1.5. The quick workaround is to set the password twice. ie filling in both passwords, click Save/Apply, fill in both passwords again, click Save/Apply and it should take.

We will have 1.1.6 out shortly to address this.

[mhoppes]

Chris,
Can you elaborate more on the password issue? Going from 1.0.10 to 1.1.0 most of my switches took fine, but one required me to reset the password in the GUI. Just curious what triggers this bug?

[sirhc]

Chris,
Can you elaborate more on the password issue? Going from 1.0.10 to 1.1.0 most of my switches took fine, but one required me to reset the password in the GUI. Just curious what triggers this bug?

Why are you going from v1.0.10 to 1.1.0 and not to v1.1.6 or maybe this is a statement from your past experience when you went to v1.1.0 probably?

I am not sure what triggers it, I have never had it happen to me personally upgrading any of my switches?

Some people experience it most do not.

There were issues upgrading from "PRE" Hashed password versions prior to 1.0.10rcX to "POST" hashed password where the password was set wrong requiring the password to be set by the console cable. This did happen to me once.


There was also the problem in more recently where after the upgrading the password was defaulted to "admin".


And the most recent issue where to change the password you need to change it twice which was fixed in v1.1.6

[sirhc]

Cosmetic bug on SFP port with STP. Those port always show forwarding no mater what. I tryed to unplug it, unplug SFP module, create broadcast storm, etc.

STP still seem to work since I don't have connection lost with RSTP enabled while pinging a ERL and can't ping it anymore if I disable RSTP.

The topology was my computer VLAN - Ubnt TSPro - Netonix 1 - Netonix 2 - Edgerouter (ping test device).

Edit: I also noted that STP is disabled by default (after config reset). I think it should be enabled by default to avoid possible loop problems.

Hi Mike, thanks for the testing and reporting.

We do have Loop Protection enabled by default to prevent loops?

So you would prefer RSTP over Loop Protection as the default or both on?

[mhoppes]

Yes. Previous upgrades. I experienced the default to admin issue on one switch but no others. Just saw the thread yesterday.