v1.4.8 Bug reports and Comments

[gunther_01]

So has the RC chain gone away, and the 1.4.8 download is the absolute latest stable???

[sirhc]

So has the RC chain gone away, and the 1.4.8 download is the absolute latest stable???

RC has gone away as far as public releases go.

We will release RC versions to select few people privately.

When we released RC versions before they were not Release Candidates but rather BUG FIXES.

The reason we used "RC" was we had made provisions for RC in the firmware way back when we started.

Had we done over we would have also made the provisions for "BF" which would stand for BUG FIX.

So now we will not be as quick to release BUG FIXES as people could not get into their heads that RC did not mean RELEASE CANDIDATE to us but rather more BUG FIX.

So it used to be if we released a new version such as v1.4.8 on Monday and someone found a bug on Tuesday we would fix the bug and release v1.4.8rc1 on Tuesday.

Now we will have to wait awhile unless it is a MAJOR BUG as we will not use RC in the public anymore.

[Eric Stern]

PING WATCHDOG

We are having issues with ping watchdog where it seems that the start up interval is not happening.

Settings are to ping an address Startup = 300 Interval = 10 Failures = 3 Action =Bounce

Upon testing I ping an address that I can turn off, and first port bounce happens at about 30 seconds, but then it bounces again about every 30 seconds. Watchdog is not waiting the 300 second startup interval.

Seems to have been working on 1.4.2.

Please Assist.

this has been duplicated and is being looked into.

Tested on 1.4.8, seems to work fine.

Code: Select all

Dec 31 19:00:06 netonix: 1.4.8 on WS-12-250-AC
Dec 31 19:00:10 system: Setting MAC address from flash configuration: EC:13:B2:FF:FF:BB
Dec 31 19:00:12 system: starting ntpclient
Dec 31 19:00:13 admin: adding lan (eth0) to firewall zone lan
Nov 23 10:27:32 dropbear[742]: Running in background
Nov 23 10:27:35 switch[783]: Detected warm boot
Nov 23 10:33:03 switch[777]: Watchdog 'Port 3' failure checking 192.168.2.12, watchdog triggered on port 3 (Port 3), action is Bounce
Nov 23 10:33:42 switch[777]: Watchdog 'Port 3' failure checking 192.168.2.12, watchdog triggered on port 3 (Port 3), action is Bounce
Nov 23 10:34:21 switch[777]: Watchdog 'Port 3' failure checking 192.168.2.12, watchdog triggered on port 3 (Port 3), action is Bounce
Nov 23 10:35:00 switch[777]: Watchdog 'Port 3' failure checking 192.168.2.12, watchdog triggered on port 3 (Port 3), action is Bounce


What is in your log?

[ste]

I try to make SIAE Alfoplus Link work for a week now. Now it looks my problems does not come from the new equipment but from one of the two netonix switches I connect this link to.

On one side I have a WS-12-250AC on the other side a WS-8-150AC.

Problem is that traffic going through WS-8-150AC to the link is not forwarded. I see packets through the link on a Mikrotik at the WS-8-150 coming in but no packet from this Mikrotik reaches the other side of the link. The discovery packets of the WS-8-150 pass through the link to the other side. The Mikrotik discovery packet in the same direction do not.

Looking at the ethernet I see a lot of RX-Filtered Packets from the ethernet port where the Mikrotik is attached.

Config of WS-8-150 is simple. I have Vlan2 configured and untagged at the Port the link is attached and at the port the Mikrotik is attached. To watch the WS-8-150 I connect on a third port which is in VLAN1 (managed). I removed all other ports from vlan table.

To cross check this I used a POE-Adapter instead of the WS-8-150 and everything is fine.

I have a lot of Netonix Switches and never seen such a behavior. So what is happening here?

[sirhc]

Please upgrade to latest firmware v1.4.8 then post up the following TABs

Status, Ports, VLANs, Device Status

I am suspecting possibly your MTU on the Netonix is too small?

[ste]

Please upgrade to latest firmware v1.4.8 then post up the following TABs

Status, Ports, VLANs, Device Status

I am suspecting possibly your MTU on the Netonix is too small?

Running on 1.4.8. MTU is set to 1600. I post the screens tomorrow.

[sirhc]

What is the MTU set on the radios in the bridge and the MT ?

[ste]

What is the MTU set on the radios in the bridge and the MT ?

Default settings. I look tomorrow. But as the Mikrotik Discovery packets aren't that big I guess this could not be the problem.

[sirhc]

You have multicast turned ON for these ports I assume?

Will look at your screen grabs tomorrow

[alexivie]

What happened to the "Watts" information for each port that use to be on the Status page?

I use that to diagnose if our equipment is booting and taking proper power.