Page 1 of 1

v1.5.7 Bug Reports and Comments

Posted: Tue Mar 30, 2021 11:13 pm
by Stephen
v1.5.7 wrote:IF A SWITCH ARRIVED WITH 1.5.5 PRELOADED PLEASE CHECK THIS THREAD

FIXED/CHANGED
- Enabling/Disabling ports on MSTP could result in loss of connectivity
- updating VLANs port types was not registered with MSTP

ENHANCEMENTS

KNOWN ISSUES
- WEB UI issues when not at 100% Zoom on browser especially on VLAN TAB
- Some language templates need help - please private message Stephen Copeland to help

Released 3/30/2021

Re: v1.5.7 Bug Reports and Comments

Posted: Fri Apr 02, 2021 6:48 pm
by kkier
Upgrading from 1.5.0 (confirmed, possibly other firmware versions) to 1.5.7 breaks dropbear start.
Specifically from a reboot:
Code: Select all
Office_:/www# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:4200 0.0.0.0:* LISTEN 657/shellinaboxd
tcp 0 0 :::80 :::* LISTEN 792/lighttpd
tcp 0 0 :::443 :::* LISTEN 792/lighttpd
udp 0 0 0.0.0.0:161 0.0.0.0:* 955/snmpd
udp 0 0 0.0.0.0:42417 0.0.0.0:* 692/syslogd
udp 0 0 :::161 :::* 955/snmpd
Office_:/www# /etc/init.d/dropbear start
Unknown argument -z

This version of dropbear identifies as dropbear sshd v0.53
It appears that the init script is trying to run this:
Code: Select all
DROPBEAR_ARGS="${nopasswd:+-s }${port:+-p $port }${tarpit_attempts:+-z $tarpit_attempts }${tarpit_delay:+-T $tarpit_delay} ${log_logins:+-l }"

Note that the version of dropbear in 1.5.6 (which does recognize the -z argument) *also* identifies as v0.53.

Re: v1.5.7 Bug Reports and Comments

Posted: Sat Apr 03, 2021 2:38 am
by Stephen
Corrected in 1.5.8