I am disapointed

[sirhc]

I was hoping for more feedback on these early switches so I can gauge production schedules going forward?

[sirhc]

I just upgraded the tower WISP Switch that feeds my house (I am still at my office).

From v1.0.1 to v1.0.2rc3

Notice I only lost 13 pings from that tower!

Also notice that my ping times (3ms) to my house which travels as follow:
Through 2 WISP Switches here at my office
Through a Cisco 2951 for our office NAT
Through a Cisco 2951 at my office outside our NAT
1 mile fiber run to my wireless tower ring.
2 mile AF24 shot
Tower Cisco 2951 with a WISP Switch
3 miles AF24 shot
Tower Cisco 2951 with a WISP Switch
1 mile AF24 shot
Tower Cisco 2951 with a WISP Switch
3.5 mile AF24 shot
Tower Cisco 2951 with a WISP Switch
Rocket M5 AP 3 mile shot to my house NanoBridge

NICE!

We think "eventually" we can allow the switch to get a firmware upgrade without even dropping a single ping.

upgrade.png (229.56 KiB) Viewed 19296 times

[lligetfa]

I just got my switch this evening and haven't had any serious time on it yet. The first thing I did was to upgrade it to the latest (1.0.2rc3) and it hung on reboot so I had to pull the plug on it.

[sirhc]

I just got my switch this evening and haven't had any serious time on it yet. The first thing I did was to upgrade it to the latest (1.0.2rc3) and it hung on reboot so I had to pull the plug on it.

I am glad you finally got your switch Less.

Did you first try to refresh your browser?

Especially when we do major upgrades to the UI some browsers refuse to download the new UI by itself and it uses cache pages.

Also are you using Chrome as the version shipped to you only supported Chrome until you upgraded and those pages could stick in cache.

Officially we still only support Chrome but we are working hard on it.

[Magician]

Just placed on management vlan and testing cables to router. I will be upgrading firmware and moving my Airfibers over to them this evening :)

[lligetfa]

I was using Chrome. I spawned another browser but it would not connect. The link port on the TS8 showed link state. Tried pinging the WS24 from the TS8 and it timed out.

After the hard boot, I tested the reboot option from the UI and it worked. Tested ping as well from the TS8 and it responded.

[Magician]

Well firmware completed dropped about 5 pings but interface came back without issue. :)

Chrome


Vlan's tested going to Taco Bell drive through then moving AF'S,

[iggy05]

Might be getting my replacement fiber jumpers today as long as the 1 day shipping was good yesterday so should be able to let you know more. :) Love the thing so far. Probably the only regret I have now is I should of got a 24 now that I revaluted my situation. Will be needed a backup of one of these so I might do that the next go round.

[sirhc]

Might be getting my replacement fiber jumpers today as long as the 1 day shipping was good yesterday so should be able to let you know more. :) Love the thing so far. Probably the only regret I have now is I should of got a 24 now that I revaluted my situation. Will be needed a backup of one of these so I might do that the next go round.

Thanks Adam, yea that was definitely an unfortunate event with those fiber jumpers, but hey it could have been much worse, the laptop or switch could have been broken in the fall!

I hope you receive your jumpers today and that our v1.0.2rc3 fixes your VLAN issue with SFP ports 13 & 14.

Also v1.0.2rc3 fixes a lot of browsers issues, surprised no one has noticed?

[iggy05]

I will give a shot on testing that issue with firefox when unplugging and replugging in a manageable port and will let you know on that. Besides that I never really noticed any issues using firefox vs chrome.