Re: Autostarting NetworkManager in Fedora 8 prevents sshd to start properly

[Robert Allerstorfer <linux-ra anet at>]

On Sat, 29 Dec 2007, 09:41 GMT-05 Dan Williams wrote:

> On Sat, 2007-12-29 at 15:37 +0100, Robert Allerstorfer wrote:
>> When the NetworkManager service is set to autostart on boot in Fedora
>> 8 (using 'chkconfig NetworkManager on'), it is no more possible to
>> remotely connect via ssh on boot unless a login took place directly on
>> the machine. This problem was not present in Fedora 7. Any clues how
>> to solve this problem?
>> 
>> The official version of NM Fedora 8 currenly uses is
>> NetworkManager-0.7.0-0.6.6.svn3109.fc8.

> Sounds like sshd is binding to an IP address and not handling changes
> when your IP address changes.  You should probably set up a
> NetworkManagerDispatcher script to kick sshd in the head (ie service
> sshd restart) when the network settings change.  This functionality
> should really be in sshd itself, doing something like avahi does where
> it watches netlink link & address events and handles the changes
> automatically.

Thanks for that - so it seems the problem is caused by the default
start order of the services, where NetworkManager starts after
avahi-daemon:

[root localhost ~]# ls -l /etc/rc.d/rc5.d | grep S | egrep 'sshd|NetworkManager|avahi-daemon'
lrwxrwxrwx 1 root root 14 2007-12-29 23:39 S55sshd -> ../init.d/sshd
lrwxrwxrwx 1 root root 22 2007-12-29 23:28 S96avahi-daemon -> ../init.d/avahi-daemon
lrwxrwxrwx 1 root root 24 2007-12-29 13:48 S98NetworkManager -> ../init.d/NetworkManager

I will try to change the start priority of avahi-daemon from 96 to 99
to see if it solves the problem.

rob.