Netonix Forums

Please post comments and bugs found in v1.1.5 - THANK YOU

FIXES
- Fixed problem with Firefox and Safari introduced in 1.1.2 - YOU KNEW WE WOULD
- Fixed problem with password after upgrading from 1.0.10


KNOWN BUGS
- If using DHCP and you change the Default/Management VLAN ID after the switch gets an address is does not get a new address.
- Not all CLI commands are present.
- In the CLI some voltages are reported incorrectly with the "sh status" command
- In the CLI not all command are present to configure VLANs

I just updated from v1.1.0rc19 to v1.1.5 and now I can't log into my switch saying invalid username/pass. Luckily the POE config is still working or I'd be on an hour long road trip in the middle of a blizzard. Anyone else having this issue? The default password isn't working ether.

Sounds like a bug that was supposed to be fixed....

Try your username with blank password.

Blank password will not work.

I just went out and upgraded one of my towers that was running v1.1.0 to v1.1.5 and it went fine?

I will LAB a v1.0.1rc19 in a few minutes to make sure it goes fine as well.

Did you change the username? If so, please try the username you used with the password "admin".

We just did a LAB from v1.1.0rc19 to v1.1.5 and it went fine.

Are you sure your were using v1.1.5 and not v1.1.4 as that would cause the password issue which we fixed in v1.1.5?

Are you also sure it was v1.1.0rc19 you upgraded from?

We want to figure out what happened but we just did v1.1.0rc19 to v1.1.5 just fine?

Didn't see the try the username I had with admin response at first. That worked! Thanks guys.

Side note that's probably answered elsewhere. Will we be able to set IPs per VLAN and allow for other and/or management interfaces? Sorry to side track my own thread.

Upgraded a switch on my desktop from 1.1.4 to 1.1.5 everything went fine until it went to reboot after the upgrade was finished. Then the switch never came out of reboot. Had to unplug it from power to get it to come back up.

After that it was fine on 1.1.5, I think I will go on site to upgrade the switches that I have in the field.

On side note on 1.1.4 the fan failures went away that I was getting in 1.1.3

Torolan wrote:Upgraded a switch on my desktop from 1.1.4 to 1.1.5 everything went fine until it went to reboot after the upgrade was finished. Then the switch never came out of reboot. Had to unplug it from power to get it to come back up.

After that it was fine on 1.1.5, I think I will go on site to upgrade the switches that I have in the field.

On side note on 1.1.4 the fan failures went away that I was getting in 1.1.3

How long did you wait, most times it is fast to come up but sometimes on occasion it may take a minute or two.

I think you sould 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).