Firmware 1.2.0rc4 comments

[sirhc]

Please let me know the firmware version you are using for your lab, I assume v1.1.1 or v1.2.0rc5?

I will see if Eric the programmer can lab this later today or this evening.

[Mola9850]

Hi Chris
Yes we have used v1.1.1 and v1.2.0rc5
sounds good

[sirhc]

Please email your config to Eric - eric@netonix.com

He is going to be working on this today.

He was busy last night late with another issue so he did not get to it, sorry.

we currently have 3 open support tickets and 2 of them (wistech & jjonson) and maybe Tony (wistech) all seem to be related to the renumbering of the default VLAN.

[Mola9850]

Done :)

[sirhc]

You need to work on the default VLAN stuff.

A good idea is to be able to choose management VLAN as with the TOUGHswitch (and other switches)
I know I can give the switch an IP-address on all VLANs but I don’t think that’s great way to do it…

You guys do relaize that the IP you assign to the VLANs is ONLY for doing ping test from the switch to the device on that port, the device has to be in the same subnet of this secondary IP on the VLAN as this IP is NOT routable as it has no gateway.

So if you want the switch to ping a radio connected to a port that is in a different VLAN/subnet it does not need to hit the router first, nor is this IP even capable of being routed as it has no gateway!!!!!

The default VLAN is the management VLAN, and only the IP set under the Device/Config Tab is routable, you change the VLAN ID or Name to what you want but REMEMBER ONLY the IP set on the Device/Config Tab is routable. This is why the default VLAN's little gear is grayed out as it used the management IP set in the Device/Status Tab.

If you thought the IP assigned on the the VLAN tab was routable and was relying on this IP to communicate outside it's sub-net then the switch could not get out causing certain safety routines in the switch firmware on boot up to detect that something is wrong and force a reboot which is where this reboot loop is coming from.

We were asked to put the secondary IP on the VLANs so people could set the ping watch dog to ping devices directly without needing to be routed if the device was in another sub-net.

We are adding BIG RED letters on the window that pops up where you assign the VLAN IP to convey to users that this is NOT a routable IP nor is it meant to be used as the management IP that is found under the Device/Config Tab. However you can access the UI via this IP address if you are in the same sub-net and on the same layer 2 segment and only if so, but ever outside this sub-net.

If this does not explain it then this will: viewtopic.php?f=17&t=560

[Mola9850]

anything new with our problem??

[sirhc]

anything new with our problem??

We are working on it, sorry we have nothing yet., hopefully by end of day.

[Mola9850]

Ok ty

[sirhc]

Almost ready to release a new version of 1.2.0rcX, a little more testing, maybe tomorrow! - Looks good though so far as we found the cause of the problems.

Previous version of 1.2.0rc5,4,3,2,1 has serious bugs - DO NOT USE

v1.1.0 and v1.1.1 are fine for the most part except when switch is using a DHCP address

[Hightech]

Great you catch the error, and cout reproduce the error in your test enviroment.
We are looking forward to test the upcomming release.
Keep up the good work we realy appreciate the work your team are dooing to give us WISP the Switch and all the other equipment that make our day great..... we love it!

/Carsten