What’s new in 1.2:
*) fixed problem - reset configuration & reboot did not work;
*) fixed problem - VLAN header present/not present matcher did not work in ACL;
*) fixed problem - could not match all packets in ACL;
*) fixed problem - deleting one ACL entry did not have immediate effect;
*) fixed problem - could not enable watchdog after it was disabled;
*) added ability to connect to SwOS with VLANs;
*) added save backup & restore backup ability;
*) added support for jumbo frames (up to 9k);
Looking good.
I’ll try it on my 3 in series setup over the weekend and email support if there are any more problems.
Thanks guys!
Soo far so good..
1.2 seems stable (for what I use it for)..
I’ve got a couple of RB250’s sitting in manholes and other places that take some effort to get to.
Am I going to able to restart via software, or am I going to have to lift manhole covers to pull the power plugs?
Now that’s an underground network. 
Tom
Eben, if you are running v1.1 there should not be any problems upgrading remotely.
Don’t knock it. It works. STP is amazing stuff
Thanks. I’ll give it a shot over the weekend.
I’ve pushed this forward and the problems start…
I logged into the switch that’s at the end of the line, clicked on system, browsed for SWOS ver 1.2 and pressed the upgrade button.
After a couple of seconds the SWOS web page came refreshed the system tab and the os version is still 1.1
I then pressed the reboot button but nothing happens.
In fact, I could press the reboot button until I start growing horns out of the side of my head. It still does not work.
Am I right in assuming that I am going to have to power this lot down one switch at a time and then restart them to get the SWOS to upgrade?
Not happy…
Things are not good with this SWOS ver 1.2
First of all, my ongoing issue has not been addressed: Dude still doesn’t interpret SMNP properly.
But that’s not important now. So I went out and shut power down to the switches and the RB750’s next to them.
When I powered the network up, the fun started.
Ping times have gone from less than 3ms to around 31ms. This isn’t good. I’ve done several ping tests and there’s no doubt that it’s the switches causing the latency. No idea why.
Apart from the latency, there are plenty of ping timeouts. Dude is sending me a long list of ping failures. The units are running - ie traffic is passing through them, but you just can’t ping them.
None of these problems were evident in SWOS1.1
The question now is how do I downgrade to the old version?
The switch / RB750 combo in this picture became too much to handle.
I uploaded SWOS 1.1 onto the switch, tried to reboot, failed and used the UPS to cycle the power going to that box.
The unit is now running on 1.1 and it appears happy.
Ping times have dropped to 15/16ms and there are no more ping timeouts being reported by Dude.
Unfortunately my SNMP still doesn’t work.
Do you have problems with increased latency and ping timeouts when you ping to or through switch? Are there any transmission errors reported in statistics tab?
Both to and through.
Other information here:
Pauses 0 0 0 0 0
Total Errors 0 0 0 0 0
Underruns 0 0 0 0 0
Too Long 0 0 0 0 0
Collisions 0 0 0 0 0
Excessive Collisions 0 0 0 0 0
Multiple Collisions 0 0 0 0 0
Single Collisions 0 0 0 0 0
Excessive Deferred 0 0 0 0 0
Deferred 0 0 0 0 0
Late Collisions 0 0 0 0 0
Hi,
I confirm the issue with the Reboot button. I’m connected over vlan1 from my PC. When I press Reboot the webserver in the switch just dies off silently. The switch itself keeps on forwarding the traffic and not a single packet is lost. If I try to telnet 192.168.88.1 port 80 there is no ARP reply.
Dalimil Gala
Make sure you are running v1.2 as there were issues in previous versions.
Have any of these problems that I previously brought to your attention been addressed?
Ping times have gone from less than 3ms to around 31ms. This isn’t good. I’ve done several ping tests and there’s no doubt that it’s the switches causing the latency. No idea why.
Apart from the latency, there are plenty of ping timeouts. Dude is sending me a long list of ping failures. The units are running - ie traffic is passing through them, but you just can’t ping them.
None of these problems were evident in SWOS1.1
Please describe your network topology, configuration, how much and what type of traffic is being forwarded through switch when you experience latency issues. We were not able to reproduce any problems with SNMP (tested with Dude v3.6 and v4.0beta2).
Here’s something from Dude
Hi,
the problem was I accessed the switch via tinyproxy 1.6.3-2 (Debian Etch) where there is a bug in HTTP 1.0 vs. HTTP 1.1:
https://www.banu.com/bugzilla/show_bug.cgi?id=66
The Reboot button worked well via squid 2.6.5-6etch5.
Is there any way to fix the webserver to recover from such a deadlock? This trouble is over for me anyway as I will avoid using tinyproxy in favour of squid.
Dalimil Gala
Ping times have gone from less than 3ms to around 31ms. This isn’t good. I’ve done several ping tests and there’s no doubt that it’s the switches causing the latency. No idea why.
Apart from the latency, there are plenty of ping timeouts. Dude is sending me a long list of ping failures. The units are running - ie traffic is passing through them, but you just can’t ping them.
None of these problems were evident in SWOS1.1
I have been experiencing the same issues as the user above. I did start a trouble ticket, but was wondering if he got this solved. We are really trying to avoid having to downgrade back to SwOS1.1. Please advise if any solution has been found. Thanks.