Modify

Opened 3 years ago

Last modified 3 years ago

#18095 new defect

Dropbear problem 42857 for trunk

Reported by: anonymous Owned by: developers
Priority: normal Milestone:
Component: packages Version: Trunk
Keywords: Cc:

Description

This update cause serious problem if interface using DHCP.
The interface doesn't have IP after device bootup,
then the script will exit and dropbear not started.
Why not just list to 127.0.0.1 ?

Attachments (0)

Change History (4)

comment:1 Changed 3 years ago by openwrt@…

I'm the author of the mentioned patch and I'm sure you have a configuration error on your side.

How should dropbear listen on an interface/ip which does not exists? It worked all the time because of a bug (see https://lists.openwrt.org/pipermail/openwrt-devel/2014-October/028467.html for more details)

What you want, is a dropbear that listens on any ip-address. To archive this, do not bind dropbear to a particular interface.

A even better solution would be to use a dropbear hotplug script as described in http://wiki.openwrt.org/doc/uci/dropbear. I'm doing it this way and it works like a charm.

comment:2 Changed 3 years ago by anonymous

After bootup, dropbear not working, luci still working,
so restart service then ssh work again.

dropbear working before the patch, I haven't change the settings.
so I'm not sure how to fix it.

comment:3 Changed 3 years ago by openwrt@…

Please attach the following files from your openwrt device to the ticket:

/etc/config/network
/etc/config/dropbear

comment:4 Changed 3 years ago by anonymous

I edited the dropbear, just two line left,
it seems ok now.

config dropbear
        option Port '22'
        option PasswordAuth 'on'

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.