v1.5.2 Bug Reports and Comments

[jsimmons@logic.bm]

Removing VLAN's from a MSTP instance on a WS-6-mini appears to lock up the GUI, needing a reboot to recover.

[Stephen]

Added to the list.

[scracha]

Is this a problem with this particular NEW unit or the new fan mode? Fan test seems fine.

[Stephen]

From the image's you've shown, there isn't a problem at all. The fan's won't be engaged until board temp is at least 45, or if the CPU temp or PHY temp go above 100, and since this is a DC switch, the power supply temperature measurements would have to go above 80.

[scracha]

Thanks for the clarification Stephen. Might I suggest a change in the GUI so the RED isn't shown until these levels are reached?

[Stephen]

I'll see what I can do.

[ahteran]

Code: Select all

Apr 12 11:44:49 dropbear[3745]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:45:04 dropbear[3779]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:45:20 dropbear[3803]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:45:37 dropbear[3823]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:45:52 dropbear[3861]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:46:09 dropbear[3881]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:46:25 dropbear[3919]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:46:41 dropbear[3939]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:46:56 dropbear[3977]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:47:12 dropbear[3997]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:47:28 dropbear[4035]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:47:44 dropbear[4064]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:48:00 dropbear[312]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:48:16 dropbear[332]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:48:33 dropbear[367]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:48:48 dropbear[391]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:49:05 dropbear[412]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:49:20 dropbear[450]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:49:37 dropbear[470]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:49:53 dropbear[509]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:50:09 dropbear[529]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:50:24 dropbear[567]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:50:41 dropbear[587]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:50:56 dropbear[625]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:51:12 dropbear[645]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:51:28 dropbear[683]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:51:44 dropbear[703]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:52:00 dropbear[737]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:52:16 dropbear[766]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:52:33 dropbear[802]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:52:50 dropbear[840]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:53:05 dropbear[860]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:53:21 dropbear[898]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:53:37 dropbear[918]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:53:53 dropbear[958]: Exit before auth (user 'admin', 1 fails): Disconnect received
Apr 12 11:54:08 dropbear[978]: Exit before auth (user 'admin', 1 fails): Disconnect received


Hello forum
I think I have a DDOS attack looking at the log records.
So is there more CPU usage on a small load?

[sirhc]

Hello forum
I think I have a DDOS attack looking at the log records.
So is there more CPU usage on a small load?

The CPU utilization is not reflective of the switch load (packet forwarding wise), all the CPU does is run the UI/CLI and some daemons used to configure the switch core which has its own specialized processors.

However multiple login sessions or repeated attempted sessions can increase CPU load.

Now with that said if your switch is WWW accessible you should be running v1.5.2 or v1.5.3rcX and use the Device/Access Control to limit who can even see or talk to the switch management UI/CLI/AND SUCH. In fact even if not a public IP you should use it to prevent users inside your network and or hackers spring boarding off a compromised device inside your network.

[ahteran]

Hello forum
I think I have a DDOS attack looking at the log records.
So is there more CPU usage on a small load?

The CPU utilization is not reflective of the switch load (packet forwarding wise), all the CPU does is run the UI/CLI and some daemons used to configure the switch core which has its own specialized processors.

However multiple login sessions or repeated attempted sessions can increase CPU load.

Now with that said if your switch is WWW accessible you should be running v1.5.2 or v1.5.3rcX and use the Device/Access Control to limit who can even see or talk to the switch management UI/CLI/AND SUCH. In fact even if not a public IP you should use it to prevent users inside your network and or hackers spring boarding off a compromised device inside your network.

I've solved the problem by disabling SSH
Thanks sirhc

[sirhc]

I've solved the problem by disabling SSH
Thanks sirhc

A better solution would be to use the Access Control List and leave SSH enabled in case you want it plus they will also try and hit it maybe next time HTTPS or SNMP or DOS