If dropbear is configured to listen on a logic interface which does not (yet)
results in a physical interface when dropbear is (re)started, the init script
bind the particular instance to 0.0.0.0.
The same happens if the physical interface exists but does not have an
ip-address
assigned.
All following dropbear instances refuse to start because of an "already in use
address" and a particular unwanted dropbear configuration is bound to global.
The impact of this error depends hardly on the instance definition order.
The following configuration results in a PasswortAuth enabled instance
reachable from WAN:
config dropbear
option PasswordAuth 'on'
option Port '22'
option Interface 'lan'
config dropbear
option Port '22'
option Interface 'nonexistent'
option PasswordAuth 'on'
config dropbear
option Port '22'
option Interface 'wan'
option PasswordAuth 'off'
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
