Re: [gentoo-user] Why is dhcpcd starting by itself?

[Willie WY Wong]

On Sun, Feb 26, 2012 at 07:00:52PM -0600, Penguin Lover Dale squawked:
> You should read the thread " rfc: only the loopback interface should
> provide net" on -dev.  They were discussing the changes in this.  Maybe
> those changes had something to do with what happened here.
> 
> Dale
> 

Thanks Dale! That explains why OpenRC 0.9.9 works differently from
before. And seeing that NetworkManager provides net also, maybe so
should wicd? 

W
-- 
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire 
 et vice versa   ~~~  I. Newton

Re: [gentoo-user] Why is dhcpcd starting by itself?

[Dale]

Dan Johansson wrote:
> On Sunday 26 February 2012 17.52:13 Dan Johansson wrote:
>> On Sunday 26 February 2012 15.19:54 Willie WY Wong wrote:
>>> On Sun, Feb 26, 2012 at 10:35:35AM +0100, Penguin Lover Willie WY Wong 
>>> squawked:
 Can someone help me figure out how to find the offending initscript that 
 is 
 needlessly calling dhcpcd? 
>>>
>>> Apparently the culprit is /etc/init.d/netmount
>>> I am not sure how it got into the default run level, since I don't use
>>> any network file systems on my netbook. 
>>
>> And on my laptop the culprit seems to be /etc/init.d/sshd
> 
> At the moment I have solved it with putting "rc_dhcpcd_provide="!net"" in 
> /etc/rc.conf
> which prevents dhcpcd to start when sshd is started.
> 


You should read the thread " rfc: only the loopback interface should
provide net" on -dev.  They were discussing the changes in this.  Maybe
those changes had something to do with what happened here.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Why is dhcpcd starting by itself?

[Willie WY Wong]

On Sun, Feb 26, 2012 at 05:31:23PM +0200, Penguin Lover Alan McKinnon squawked:
> Here's what I've found after much up & down-grading and rebooting:
> 
> First, I've had netmount in the default runlevel for ages and it's
> worked for ages even though it does nothing.
> Second, openrc has been launching "dhcpcd -q" at boot time for ages and
> this has never interfered with wicd which comes along later.
> 
> openrc-0.8.* always works with any kernel version
> openrc-0.9* work with kernel-3.2.5
> 
> openrc-0.9* does not work with kernel-3.2.6, giving these errors:

snipped log-

> 
> That looks to me like avahi is all confused and tripping over what
> openrc & wicd do properly. I'd say the root cause is a change in
> kernel-3.2.6 that was not tested against.
> 

Alan: after re-reading your post, I have to retract my earlier
statement. It seems *your* problem is a separate one from the one that
Dan and I are having! 

I am running on 2.6.37. I just tried to upgrade to 3.2.6 earlier today
but ran into some other problems (there seems to be a bug in the
linux-3 kernel that breaks WEP for ath9k wireless cards, that and for
some reason `shutdown -h now' halts but does not power off; both are
known and there are patches, just haven't made it into the tree yet). 

The problem I was reporting has nothing to do with the kernel (same
kernel since last August). 

Cheers, 

W

Cheers, 

W
-- 
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire 
 et vice versa   ~~~  I. Newton

Re: [gentoo-user] Why is dhcpcd starting by itself?

[Dan Johansson]

On Sunday 26 February 2012 17.52:13 Dan Johansson wrote:
> On Sunday 26 February 2012 15.19:54 Willie WY Wong wrote:
> > On Sun, Feb 26, 2012 at 10:35:35AM +0100, Penguin Lover Willie WY Wong 
> > squawked:
> > > Can someone help me figure out how to find the offending initscript that 
> > > is 
> > > needlessly calling dhcpcd? 
> > 
> > Apparently the culprit is /etc/init.d/netmount
> > I am not sure how it got into the default run level, since I don't use
> > any network file systems on my netbook. 
> 
> And on my laptop the culprit seems to be /etc/init.d/sshd

At the moment I have solved it with putting "rc_dhcpcd_provide="!net"" in 
/etc/rc.conf
which prevents dhcpcd to start when sshd is started.

-- 
Dan Johansson, 
***
This message is printed on 100% recycled electrons!
***

Re: [gentoo-user] Why is dhcpcd starting by itself?

[Dan Johansson]

On Sunday 26 February 2012 15.19:54 Willie WY Wong wrote:
> On Sun, Feb 26, 2012 at 10:35:35AM +0100, Penguin Lover Willie WY Wong 
> squawked:
> > Can someone help me figure out how to find the offending initscript that is 
> > needlessly calling dhcpcd? 
> 
> Apparently the culprit is /etc/init.d/netmount
> I am not sure how it got into the default run level, since I don't use
> any network file systems on my netbook. 

And on my laptop the culprit seems to be /etc/init.d/sshd

-- 
Dan Johansson, 
***
This message is printed on 100% recycled electrons!
***

Re: [gentoo-user] Why is dhcpcd starting by itself?

[Alan McKinnon]

On Sun, 26 Feb 2012 15:19:54 +0100
Willie WY Wong  wrote:

> On Sun, Feb 26, 2012 at 10:35:35AM +0100, Penguin Lover Willie WY
> Wong squawked:
> > Can someone help me figure out how to find the offending initscript
> > that is needlessly calling dhcpcd? 
> 
> Apparently the culprit is /etc/init.d/netmount
> I am not sure how it got into the default run level, since I don't use
> any network file systems on my netbook. 

I believe the problem is much deeper than that and while your
observations are valid, you don't have a root cause yet. You just have
a happy symptom that works with your specific configuration.

Here's what I've found after much up & down-grading and rebooting:

First, I've had netmount in the default runlevel for ages and it's
worked for ages even though it does nothing.
Second, openrc has been launching "dhcpcd -q" at boot time for ages and
this has never interfered with wicd which comes along later.

openrc-0.8.* always works with any kernel version
openrc-0.9* work with kernel-3.2.5

openrc-0.9* does not work with kernel-3.2.6, giving these errors:

Feb 26 17:16:53 khamul dhcpcd[2661]: wlan0: leased 172.20.0.41 for
43200 seconds 
Feb 26 17:16:53 khamul avahi-daemon[2479]: Joining mDNS multicast group
on interface wlan0.IPv4 with address 172.20.0.41. 
Feb 26 17:16:53 khamul avahi-daemon[2479]: New relevant interface
wlan0.IPv4 for mDNS. 
Feb 26 17:16:53 khamul avahi-daemon[2479]: Registering new address
record for 172.20.0.41 on wlan0.IPv4. 
Feb 26 17:16:54 khamul dhcpcd[2661]: eth0: sending IPv6 Router
Solicitation
Feb 26 17:16:54 khamul dhcpcd[2661]: eth0: sendmsg: Network is
unreachable 
Feb 26 17:16:55 khamul dhcpcd[4388]: sending commands to master dhcpcd
process 
Feb 26 17:16:55 khamul dhcpcd[2661]: control command: /sbin/dhcpcd -k
wlan0 
Feb 26 17:16:55 khamul dhcpcd[2661]: wlan0: releasing lease of
172.20.0.41 
Feb 26 17:16:55 khamul avahi-daemon[2479]: Withdrawing address record
for 172.20.0.41 on wlan0. 
Feb 26 17:16:55 khamul avahi-daemon[2479]: Leaving mDNS multicast group
on interface wlan0.IPv4 with address 172.20.0.41. 
Feb 26 17:16:55 khamul avahi-daemon[2479]: Interface wlan0.IPv4 no
longer relevant for mDNS. 
Feb 26 17:16:55 khamul dhcpcd[2661]: wlan0: open_udp_socket: Cannot
assign requested address 
Feb 26 17:16:55 khamul kernel: [   58.240866] wlan0: deauthenticating
from 00:04:ed:45:65:df by local choice (reason=3)

That looks to me like avahi is all confused and tripping over what
openrc & wicd do properly. I'd say the root cause is a change in
kernel-3.2.6 that was not tested against.

So, what's the next debugging step?


-- 
Alan McKinnnon
alan.mckin...@gmail.com

Re: [gentoo-user] Why is dhcpcd starting by itself?

[Willie WY Wong]

On Sun, Feb 26, 2012 at 10:35:35AM +0100, Penguin Lover Willie WY Wong squawked:
> Can someone help me figure out how to find the offending initscript that is 
> needlessly calling dhcpcd? 

Apparently the culprit is /etc/init.d/netmount
I am not sure how it got into the default run level, since I don't use
any network file systems on my netbook. 

Cheers, 
W
-- 
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire 
 et vice versa   ~~~  I. Newton

Re: [gentoo-user] Why is dhcpcd starting by itself?

[Willie WY Wong]

On Sun, Feb 26, 2012 at 07:32:43AM -0600, Penguin Lover Dale squawked:
> This may not be it but worth taking a look at.  /etc/rc.conf  From that
> file:
> 
> # rc_hotplug is a list of services that we allow to be hotplugged.
> # By default we do not allow hotplugging.
> # A hotplugged service is one started by a dynamic dev manager when a
> matching
> # hardware device is found.
> # This service is intrinsically included in the boot runlevel.
> # To disable services, prefix with a !
> # Example - rc_hotplug="net.wlan !net.*"
> # This allows net.wlan and any service not matching net.* to be plugged.
> # Example - rc_hotplug="*"
> # This allows all services to be hotplugged
> #rc_hotplug="*"
> 
> I think that should be off by default but maybe try disabling them all
> manually just in case.
> 

Hotplug has never been turned on in my case. 

I've always had

rc_hotplug="!net.*" 

W
-- 
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire 
 et vice versa   ~~~  I. Newton

Re: [gentoo-user] Why is dhcpcd starting by itself?

[Dale]

Willie WY Wong wrote:
> On Thursday night, I emerged some packages
> 
<< SNIP >>
> Can someone help me figure out how to find the offending initscript that is 
> needlessly calling dhcpcd? 
> 
> Cheers, 
> W



This may not be it but worth taking a look at.  /etc/rc.conf  From that
file:

# rc_hotplug is a list of services that we allow to be hotplugged.
# By default we do not allow hotplugging.
# A hotplugged service is one started by a dynamic dev manager when a
matching
# hardware device is found.
# This service is intrinsically included in the boot runlevel.
# To disable services, prefix with a !
# Example - rc_hotplug="net.wlan !net.*"
# This allows net.wlan and any service not matching net.* to be plugged.
# Example - rc_hotplug="*"
# This allows all services to be hotplugged
#rc_hotplug="*"

I think that should be off by default but maybe try disabling them all
manually just in case.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"