v1.4.0 Bug Reports and Comments

[sirhc]

I still have issues with IGMP which simply doesn't work with tagged VLANs

-G

Work with Eric on this as we will continue to investigate this issue, there will always be the next version.

[cbl]

#1. One mini shortly after upgrading decided to stop responding to SNMP. An snmpwalk on the IP would result in "Timeout: No response from ". Changing the version to 1 on the switch, would allow a -v1 snmpwalk to complete, and then changing back to v2c on the switch would allow a v2c snmpwalk to complete again.

I do not know, maybe this was an anomaly? See if you can re-create it.

Found a 1.3.9 that was experiencing the same issue. Appears the snmpd on it died earlier this morning. Nothing in logs. I'm not sure how to reproduce it, I've only seen a couple in the last 6 months that've had it happen.

#2. On one Ws-24-2400A we have a bunch of UBNT Titaniums. We've experienced the port lockup on these when set to Auto and have forced to 100FD on both the switch and AP to get around the AP deciding to become unreachable. One AP on this switch after update (from 1.3.9) was showing Tx Drops/Collisions incrementing, whereas before the upgrade it was not.

I thought they fixed this issue in their firmware?
I think remember talking to several people that said they now use Auto again?
Try a port bounce to cause the Ethernet link on the radio to re-negotiate.
Nothing has changed that would affect Ethernet Communications as the core code has not been touched.

I have another Ti AP forced that is showing incremental Tx Drops/Collissions since upgrading to 1.4.0. Appears when it's under heavier load. These didn't appear prior to the 1.4.0 upgrade. Power cycle shows the same thing. However, going to Auto (which links at 1G) they go away.

Anybody else still forcing 100FD on Ti's? I've looked through the UBNT forums posting on the lockups and havent found anybody saying a firmware has fixed it yet.

#3. On these 100FD forced ports, it looks like flow control icons on the Status page were displaying. They were not prior to 1.4.0 as from what I remember reading from the spec you can't have flow control with a non-Auto port. Just wondering if it's perhaps showing the icon regardless of if it's negotiated flow control with the other side?

Most devices will not negotiate Flow Control if not set to Auto some will. If we are indicating Flow Control is active then it is which you should be able to tell if Pause Frames are recorded under port stats.

I have a Ti on a mini that's on 1.4.0 which is forced to 100FD and it shows flow control active (Given it is enabled in the port config), but zero pause frames in/out on the port. On 1.3.9 these 100FD ports did not show it was active. Sounds like a possible bug to me.

[sirhc]

I have a Ti on a mini that's on 1.4.0 which is forced to 100FD and it shows flow control active (Given it is enabled in the port config), but zero pause frames in/out on the port. On 1.3.9 these 100FD ports did not show it was active. Sounds like a possible bug to me.

Not necessarily, log into the Ti Radio and disable Flow Control in the Ti and see what we report then and report back.

Also you can specify Auto and setup a Ping Watch Dog to reboot then unit if it loses connection / Ti locks up.

[sirhc]

Well, what about some of the new features?

The Discovery Tab, I think this is a cool tool.

SMART DC models now have new graphs on the Device/Status Tab you guys asked for (up to 24 hours).

CLICK IMAGE TO VIEW FULL SIZE

[IntL-Daniel]

There is some bug with view on Google Chrome. First load shows each line per two lines...reload the page solve the bug. Not seen on IE or Firefox. I am on RC25, are there any changes in final 1.4.0?

[sirhc]

There is some bug with view on Google Chrome. First load shows each line per two lines...reload the page solve the bug. Not seen on IE or Firefox. I am on RC25, are there any changes in final 1.4.0?

Daniel if you notice this is the thread for v1.4.0 not v1.4.0rc25.

Yes, that bug was already fixed in v1.4.0.

[IntL-Daniel]

Thanks! Any other changes between rc25 and final?

[sirhc]

Thanks! Any other changes between rc25 and final?

Yes, mostly minor changes such as UI layouts

I would upgrade any RC version to FINAL

[tcknudson]

quite unstable since installing newest firmware two days ago,

[sirhc]

Considering that NOTHING has changed as far as switch core functions (the actual switching of packets) I have no idea.

I have it on all my switches at my WISP and they run GREAT?

I doubt your issues are with the firmware but feel free to downgrade if you like but personally I think v1.4.0 is our best firmware to date.