#15425: dropbear interface option
------------------------+----------------------------------
Reporter: anonymous | Owner: developers
Type: defect | Status: reopened
Priority: normal | Milestone: Chaos Calmer (trunk)
Component: packages | Version: Trunk
Resolution: | Keywords:
------------------------+----------------------------------
Comment (by openwrt@…):
This is a definite challenge for me. I am starting two instances of
dropbear, one on the internal LAN with password auth enabled and one on
the external with only key authentication enabled and on same port. On
Barrier Breaker r42625 the WAN is comes up after dropbear. Unfortunately,
what this means is that the internal (LAN only) dropbear instance is now
available on all interfaces including the WAN.
My expectation is that, if the interface is not up, the instance should
not start, particularly on the "wrong" interface.
This is also a regression from my previous version of Attitude Adjustment
r34185
Yes, I know that, if I were using different ports, I could partially work
around the issue by blocking the internal port on the external interface
with the firewall.
--
Ticket URL: <https://dev.openwrt.org/ticket/15425#comment:9>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
