v1.5.25 Bug Reports and Comments

[sirhc]

Oh and WS4 will offer a MUCH faster CPU and nan flash verses spy flash over the WS and WS3 so boot time will be very fast.

However WS3 and WS4 are in same SOC family so when a new firmware is released for WS4 a WS3 version will be released with same software features just not 2.5G copper and slower CPU and flash.

[RebusCom]

What about the switch event logs not including login events (success or failure)?

I'll ask Stephen to look at that next time he revisits WS or when he needsxa break from WS4.

I consider this event as minor albeit should be fixed you are correct.

While at it the other missing error reports should be resurrected as well, such as watchdog events.

[sakita]

What about the switch event logs not including login events (success or failure)?

I'll ask Stephen to look at that next time he revisits WS or when he needsxa break from WS4.

I consider this event as minor albeit should be fixed you are correct.

We are pushing hard to catch up with WS4 pre production sale.

So existing models have been finalized.

WS4-14- 600-AC / 600-DC / 400-IDC
(2) SFP+ ports
(12) 2.5G POE ports
We dropped External temp humidity sensor, door open sensor, and external relay to control external device such as fans AC or DC

WS4-6-MINI
Same as WS-6-MINI except no barrel connector POE power in on port 1 only but if powered by WS4-14 you have 200 watts. Almost same size but 1 inch longer. Will still fit in same box.

WS4-8-250-AC or DC
(2) SFP+
(6) 2.5G POE ports

WS4-14-TOWER
(2) SFP+ ports
(12) 2.5G POE ports
In an all weather metal chassis tower mountable.
Meant to be fiber/composit fed for data/power

WS4-6- 600-AC / 600-DC / 400-IDC
(2) SFP+ ports
(4) 2.5G POE ports

Used to power tower switch(s) and or up to 4 other devices including WS4-6-MINI(s)

These unit initially will have same feature set as WS line but will get via firmware upgrade routing including OSPF / BGP (not capable of world routes)

Extensive bandwidth control ability via rules sets.

They fearure isolated power supplies, upgraded current sensors and MOSFETS to better harden against ground current and poor grounding.

Tenitive pre sales release small run of WS4-14 and WS4-6 is set for end of April beginning of May.

We dropped the external sensors to keep costs down as Dave thought not many would use

If you disagree speak now or forever hold your peace.

I think Dave is right For those locations that need temperature, inputs, and relays I just use a Control by Web X-410 that I can power off of a port on the Netonix switch (for example, we have 3 solar-powered sites we are redoing and that's what they're getting: an X-410 powered by an WS-8-150-DC). The many other sites? They don't need that feature.

[sdwisp]

After upgrading from 1.5.15rc2 or older firmware the email stops sending.

Can someone review the log and let me know what I'm missing. Looks like the change is in the user name. I have double checked all settings in more than one router test.





Thanks for the help







Harbison 1 test good FW 1.5.17 rc2 email test good





[<-] 220 and/or bulk e-mail.





[->] EHLO mail.wispadmin.net





[<-] 250 HELP





[->] AUTH LOGIN





[<-] 334 VXNlcm5hbWU6





[->] c3dpdGNoQHdpc3BhZG1pbi5uZXQ=





[<-] 334 UGFzc3dvcmQ6





[<-] 235 Authentication succeeded





[->] MAIL FROM:<switch@wispadmin.net>





[<-] 250 OK





[->] RCPT TO:<netsupport@sdwisp.com>





[<-] 250 Accepted





[->] DATA





[<-] 354 Enter message, ending with "." on a line by itself





[->] Received: by mail.wispadmin.net (sSMTP sendmail emulation); Tue, 18 Mar 2025 05:21:33 -0700





[->] From: "Harbison1 AC v1.5.17rc2" <switch@wispadmin.net>





[->] Date: Tue, 18 Mar 2025 05:21:33 -0700





[->] To: netsupport@sdwisp.com





[->] Subject: test email from Harbison1 AC v1.5.17rc2





[->]





[->] This is a test email





[->] .





[<-] 250 OK id=1tuVx9-000000022ss-19D2





[->] QUIT





[<-] 221 batmobile.websitewelcome.com closing connection





Harbison 1 after upgrade to 1.5.25...... NO more email ...workey





[<-] 220 and/or bulk e-mail.





[->] EHLO wispadmin.net





[<-] 250 HELP





[->] AUTH LOGIN





[<-] 334 VXNlcm5hbWU6





[->] c3dpdGNoQHdpc3BhZG1pbi5uZXQ=





[<-] 334 UGFzc3dvcmQ6





[<-] 235 Authentication succeeded





[->] MAIL FROM:<sd_wisp@wispadmin.net>





[<-] 250 OK





[->] RCPT TO:<netsupport@sdwisp.com>





[<-] 550 Sender verify failed





ssmtp: RCPT TO:<netsupport@sdwisp.com> (550 Sender verify failed)

[Dawizman]

At first I thought I was crazy and thought I changed a switch password, but actually didn't after the upgrade. But now I am not so sure.

I seem to be having random reversion to the default admin password.

I have had this happen several times now, when I change a switch password post upgrade to 1.5.25. Some time later I go to login, and get incorrect password. I login with admin/admin, and it works. I then update the password, and it takes. Although I am sure I have had to do this more than once on the same switch now.

A log excerpt below showing me having to change it twice...

Code: Select all

Mar 20 12:30:33 UI[798]: Configuration changed by admin (192.168.251.2)
Mar 20 12:30:33 UI[798]: Config_Version: 13 => 14
Mar 20 12:30:33 UI[798]: Credentials_Password => Updated
Mar 20 12:30:35 passwd: Password for admin changed by admin
Mar 20 12:30:36 monitor: restarting shellinaboxd
Mar 20 12:39:04 UI[798]: Configuration changed by admin (192.168.251.2)
Mar 20 12:39:04 UI[798]: Config_Version: 14 => 15
Mar 20 12:39:04 UI[798]: IPv4_Address: 10.254.18.12 => 10.254.18.2
Mar 20 12:39:06 admin: removing lan (eth0) from firewall zone lan
Mar 20 12:39:09 admin: stopped ntp daemon
Mar 20 12:39:09 admin: started ntp daemon
Mar 20 12:39:10 admin: sync time via ntp
Mar 20 12:39:11 admin: adding lan (eth0) to firewall zone lan
Mar 20 12:39:11 STP: msti 0 set port 1 to discarding
Mar 20 12:39:11 STP: msti 0 set port 5 to discarding
Mar 20 12:39:11 STP: msti 0 set port 6 to discarding
Mar 20 12:39:11 STP: msti 0 set port 7 to discarding
Mar 20 12:39:11 STP: msti 0 set port 8 to discarding
Mar 20 12:39:11 STP: msti 0 set port 9 to discarding
Mar 20 12:39:12 STP: msti 0 set port 10 to discarding
Mar 20 12:39:12 STP: msti 0 set port 11 to discarding
Mar 20 12:39:12 admin: stopped ntp daemon
Mar 20 12:39:12 admin: started ntp daemon
Mar 20 12:39:12 STP: MSTI0: New root on port 5, root path cost is 20000, root bridge id is 32768.DC-2C-6E-EE-B6-67
Mar 20 12:39:12 STP: msti 0 set port 5 to learning
Mar 20 12:39:12 STP: msti 0 set port 5 to forwarding
Mar 20 12:39:12 admin: sync time via ntp
Mar 20 12:39:12 STP: MSTI0: New root on port 1, root path cost is 20000, root bridge id is 32768.02-B4-A8-02-D4-8C
Mar 20 12:39:12 STP: msti 0 set port 5 to discarding
Mar 20 12:39:12 STP: msti 0 set port 1 to learning
Mar 20 12:39:12 STP: msti 0 set port 1 to forwarding
Mar 20 12:39:12 STP: msti 0 set port 5 to learning
Mar 20 12:39:12 STP: msti 0 set port 5 to forwarding
Mar 20 12:39:15 STP: msti 0 set port 11 to learning
Mar 20 12:39:15 STP: msti 0 set port 11 to forwarding
Mar 20 12:39:15 STP: msti 0 set port 10 to learning
Mar 20 12:39:15 STP: msti 0 set port 10 to forwarding
Mar 20 12:39:15 STP: msti 0 set port 9 to learning
Mar 20 12:39:15 STP: msti 0 set port 9 to forwarding
Mar 20 12:39:15 STP: msti 0 set port 8 to learning
Mar 20 12:39:15 STP: msti 0 set port 8 to forwarding
Mar 20 12:39:15 STP: msti 0 set port 7 to learning
Mar 20 12:39:15 STP: msti 0 set port 7 to forwarding
Mar 20 12:39:15 STP: msti 0 set port 6 to learning
Mar 20 12:39:15 STP: msti 0 set port 6 to forwarding
Mar 20 12:40:53 UI[798]: Configuration changed by admin (192.168.251.2)
Mar 20 12:40:53 UI[798]: Config_Version: 15 => 16
Mar 20 12:40:53 UI[798]: Credentials_Password => Updated
Mar 20 12:40:55 passwd: Password for admin changed by admin
Mar 20 12:41:07 monitor: restarting shellinaboxd


[Brenda]

Thanks for the firmware!

[jfrawley]

This is my first attempt at radius auth with Netonix, so far I am striking out. Response in ssh is Access Denied, I added the line to my clients.conf file and I also enabled require_message_authenticator for my global rule as well. I guess where I am lacking the experience/knowledge on this is what kind of reply should radius be sending?


Freeradius 3.0
# allowed values: yes, no
require_message_authenticator = yes
client private-network-1 {
### I also tried just the ip of the switch rather than a range yyy.yyy.yyy/32
ipaddr = 10.0.0.0/8
secret = somethingsecret
require_message_authenticator = yes


Currently I have a user in my database- (not real info here)
Check Attributes
user User1
Cleartext-Password := User1234

Reply Attributes
Auth-Type := Accept

## I also tried with a GROUP reply with Auth-type := Accept

I have the switch ip in my NAS as well with correct secret, radius port is also default and correct 1812

Netonix v 1.5.25
"RADIUS_Enable":true,
"RADIUS_Host":"xxx.xxx.xxx.xxx",
"RADIUS_Port":"1812",
"RADIUS_Secret":"somethingsecret",
My tiks all auth just fine, granted they use a different reply though such as FULL or READ

When I run radclient from the Netonix-
admin@T222:/etc/freeradius2# echo "User-Name = validuser,User-Password=validpass" | radclient xxx.xxx.xxx.xxx auth somethingsecret
Received response ID 144, code 2, length = 20

[sirhc]

This is my first attempt at radius auth with Netonix, so far I am striking out. Response in ssh is Access Denied, I added the line to my clients.conf file and I also enabled require_message_authenticator for my global rule as well. I guess where I am lacking the experience/knowledge on this is what kind of reply should radius be sending?


Freeradius 3.0
# allowed values: yes, no
require_message_authenticator = yes
client private-network-1 {
### I also tried just the ip of the switch rather than a range yyy.yyy.yyy/32
ipaddr = 10.0.0.0/8
secret = somethingsecret
require_message_authenticator = yes


Currently I have a user in my database- (not real info here)
Check Attributes
user User1
Cleartext-Password := User1234

Reply Attributes
Auth-Type := Accept

## I also tried with a GROUP reply with Auth-type := Accept

I have the switch ip in my NAS as well with correct secret, radius port is also default and correct 1812

Netonix v 1.5.25
"RADIUS_Enable":true,
"RADIUS_Host":"xxx.xxx.xxx.xxx",
"RADIUS_Port":"1812",
"RADIUS_Secret":"somethingsecret",
My tiks all auth just fine, granted they use a different reply though such as FULL or READ

When I run radclient from the Netonix-
admin@T222:/etc/freeradius2# echo "User-Name = validuser,User-Password=validpass" | radclient xxx.xxx.xxx.xxx auth somethingsecret
Received response ID 144, code 2, length = 20

This is not really where you should post this as Free Radius has been proven to work so not a bug,. and you state this is your first attempt at using so guessing its something in your configuration or setup.

I would like to help you, but I don't use Radius Auth and testing was done by Stephen on this.

Stephen may catch this and help and or another user using Radius but if it's not a bug should find a similar thread on radius with search function or even start a new thread. If you read this thread you can determine that it does work if configured correctly so not a bug.

[oeyre]

We just saw ~20 units at multiple sites unexpectedly reboot within a 2-3 hour window. In the logs we see this message:

Code: Select all

Jan 1 10:31:30 switch[931]: Detected cold (watchdog) boot

All running 1.5.25, no particular pattern regarding voltage or model. There were not any known power issues or other factors that could explain this.

Is there any additional debugging available? Anybody else see this?

[Flo]

We just saw ~20 units at multiple sites unexpectedly reboot within a 2-3 hour window. In the logs we see this message:

Code: Select all

Jan 1 10:31:30 switch[931]: Detected cold (watchdog) boot

All running 1.5.25, no particular pattern regarding voltage or model. There were not any known power issues or other factors that could explain this.

Is there any additional debugging available? Anybody else see this?

Oeyre, are you running a large scale L2-network using RSTP to protect against network loops?
We have seen a similar behavior during network loops running older firmware versions if RSTP does not detect a network loop situation promptly.
Try to set up Device -> Configuration: "Storm Control" if that's the case.
i.e. 1K, 4K, 8K (Broadcast, Multicast, Unicast)