Summary: | sshd does not start with ifplugd on eth0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sebastian Bergmann (RETIRED) <sebastian> |
Component: | [OLD] baselayout | Assignee: | Roy Marples (RETIRED) <uberlord> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 143887 | ||
Bug Blocks: | |||
Attachments: |
/etc/conf.d/net
/etc/conf.d/rc /var/log/boot.msg |
Description
Sebastian Bergmann (RETIRED)
2006-08-19 09:43:02 UTC
post your /etc/conf.d/net and /etc/conf.d/rc files Created attachment 94666 [details]
/etc/conf.d/net
Created attachment 94667 [details]
/etc/conf.d/rc
Are both net.eth0 and net.eth1 in the default runlevel? Also, ifplugd is very bad with wireless - use wpa_supplicant instead. No, I have neither net.eth0 nor net.eth1 in the default runlevel. I thought that this was not needed. No, it's not needed. I myself don't have any net.xxx scripts in any runlevel (except for net.lo). Is sshd in the default runlevel? Does it work if you use wpa_supplicant to manage your wireless interface? Yes, sshd is in the default runlevel. I don't know about wpa_supplicant as I don't use it. (In reply to comment #7) > Yes, sshd is in the default runlevel. I don't know about wpa_supplicant as I > don't use it. Have you got wireless-tools installed? Of course. So you're using the ifplugd init script? Created attachment 94771 [details]
/var/log/boot.msg
No, I am not using the ifplugd init script. net.eth1 is not in any runlevel and is not being picked up by udev/coldplug to add it to the default runlevel. Solution - add net.eth1 to the default runlevel. Adding net.eth1 to the default runlevel makes the situation currently worse for me: at the time when net.eth1 is started the ipw3945d has not yet been started (because I currently start it via conf.d/local.start). Will try again once the ipw3945d issue has been solved. If ipw3945d creates the actual interface then we have a problem. At present, ipw3945d doesn't even have an init script to my knowledge. I think the only viable solution is to add net.eth1 to the default runlevel, follow the advice in bug #143887 to get net.eth1 to depend on ipw3945d AND - this is the important part - use wpa_supplicant. wpa_supplicant is important as it makes net.eth1 re-entrant so it supports the inactive status. This means that during a normal boot services that require net will be scheduled to start once a net device becomes active - you are already seeing this with ifplugd. |