[gentoo-user] eth0 and eth1 unwanted autoconfiguration

[gentoo-user] eth0 and eth1 unwanted autoconfiguration

[darren kirby]

[-- Attachment #1: Type: text/plain, Size: 844 bytes --]

Hello all,

Does anyone know why my eth0 (wired) and eth1 (wireless) interfaces are 
getting started and autoconfigured at boot despite not being present at any 
runlevel in rc-update?

They are getting configured with the settings in conf.d/net, whether or not 
eth0 has a cable plugged in, and whether or not the firmware is loaded for 
eth1 (it is a PCMCIA device). Obviously, these settings are bunk...

I am not sure what info I should put here to diagnose this:
gentoo-sources-2.6.14-r5
baselayout-1.12.0_pre16-r3

Again, net.eth0 and net.eth1 are not shown at _any_ runlevel when I run 
'rc-update -s'.

thanks,
-d
-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-user] eth0 and eth1 unwanted autoconfiguration

[Teresa and Dale]

darren kirby wrote:

>Hello all,
>
>Does anyone know why my eth0 (wired) and eth1 (wireless) interfaces are 
>getting started and autoconfigured at boot despite not being present at any 
>runlevel in rc-update?
>
>They are getting configured with the settings in conf.d/net, whether or not 
>eth0 has a cable plugged in, and whether or not the firmware is loaded for 
>eth1 (it is a PCMCIA device). Obviously, these settings are bunk...
>
>I am not sure what info I should put here to diagnose this:
>gentoo-sources-2.6.14-r5
>baselayout-1.12.0_pre16-r3
>
>Again, net.eth0 and net.eth1 are not shown at _any_ runlevel when I run 
>'rc-update -s'.
>
>thanks,
>-d
>  
>

Is it possible that you are running something that needs net and that is
starting it?  I know some things, like ivman and such, will start other
services if they must be running for them to work.

Just a thought.  Is strange though.

Dale

:D :D :D
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] eth0 and eth1 unwanted autoconfiguration

[darren kirby]

[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]

quoth the Teresa and Dale:
> darren kirby wrote:
> >Hello all,
> >
> >Does anyone know why my eth0 (wired) and eth1 (wireless) interfaces are
> >getting started and autoconfigured at boot despite not being present at
> > any runlevel in rc-update?
> >
> >They are getting configured with the settings in conf.d/net, whether or
> > not eth0 has a cable plugged in, and whether or not the firmware is
> > loaded for eth1 (it is a PCMCIA device). Obviously, these settings are
> > bunk...
> >
> >I am not sure what info I should put here to diagnose this:
> >gentoo-sources-2.6.14-r5
> >baselayout-1.12.0_pre16-r3
> >
> >Again, net.eth0 and net.eth1 are not shown at _any_ runlevel when I run
> >'rc-update -s'.
> >
> >thanks,
> >-d
>
> Is it possible that you are running something that needs net and that is
> starting it?  I know some things, like ivman and such, will start other
> services if they must be running for them to work.

I don't think so...

The only network related script in the default runlevel is 'net.lo'. syslog-ng 
doesn't need network does it? 

Could this be from hotplug or udev? I really don't see why they would start?!

> Just a thought.  Is strange though.
>
> Dale
>
> :D :D :D

-d
-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-user] eth0 and eth1 unwanted autoconfiguration

[Renat Golubchyk]

[-- Attachment #1: Type: text/plain, Size: 514 bytes --]

On Fri, 14 Apr 2006 19:17:06 -0700 darren kirby
<bulliver@badcomputer.org> wrote:
> syslog-ng doesn't need network does it? 

It can need it if configured approprietly.
Run "egrep '(use|need|after).*net' /etc/init.d/*" and read the
Gentoo handbook at
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=4#doc_chap4


Cheers,
Renat

-- 
Probleme kann man niemals mit derselben Denkweise loesen,
durch die sie entstanden sind.
                                              (Einstein)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] eth0 and eth1 unwanted autoconfiguration

[Richard Fish]

On 4/14/06, darren kirby <bulliver@badcomputer.org> wrote:
> > Is it possible that you are running something that needs net and that is
> > starting it?  I know some things, like ivman and such, will start other
> > services if they must be running for them to work.
>
> I don't think so...
>
> The only network related script in the default runlevel is 'net.lo'. syslog-ng
> doesn't need network does it?

Yes, it does.

1. Check your setting and the comments for RC_NET_STRICT_CHECKING in
/etc/conf.d/rc.  This should probably be set to 'lo' for your system.

2. Hotplug can also activate network interfaces.  See
/etc/hotplug/net.agent.  I'm not sure how this affects cardbus
adapters however...

3. For eth0, merge the ifplugd package and the interface will not be
activated until a cable is plugged in.  However you might need a 1.12
baselayout for this functionality...

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] eth0 and eth1 unwanted autoconfiguration *Resolved* I think...

[darren kirby]

[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]

quoth the Richard Fish:
> On 4/14/06, darren kirby <bulliver@badcomputer.org> wrote:
> > > Is it possible that you are running something that needs net and that
> > > is starting it?  I know some things, like ivman and such, will start
> > > other services if they must be running for them to work.
> >
> > I don't think so...
> >
> > The only network related script in the default runlevel is 'net.lo'.
> > syslog-ng doesn't need network does it?
>
> Yes, it does.

Really? Following Renat's advice I checked all my initscripts called from 
'boot' or 'default'. Not a single one relies on net working. syslog-ng has a 
case statement that checks if you have tcp/udp logging in your syslog-ng.conf 
but this does not apply to my laptop (the machine in question).

> 1. Check your setting and the comments for RC_NET_STRICT_CHECKING in
> /etc/conf.d/rc.  This should probably be set to 'lo' for your system.

Ok, it was 'no'. I changed to 'lo'. Rebooted and now only eth0 starts?!

> 2. Hotplug can also activate network interfaces.  See
> /etc/hotplug/net.agent.  I'm not sure how this affects cardbus
> adapters however...

Ok, I added 8139too to /etc/hotplug/blacklist, rebooted and it seems to be 
behaving now.

> 3. For eth0, merge the ifplugd package and the interface will not be
> activated until a cable is plugged in.  However you might need a 1.12
> baselayout for this functionality...

A welcome suggestion, but not really what I am after. I just don't want the 
interface starting automatically at boot.

> -Richard

Thanks for the help everyone! Resolved for now...
-d
-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-user] eth0 and eth1 unwanted autoconfiguration *Resolved* I think...

[Richard Fish]

On 4/14/06, darren kirby <bulliver@badcomputer.org> wrote:
> > Yes, it does.
>
> Really? Following Renat's advice I checked all my initscripts called from
> 'boot' or 'default'. Not a single one relies on net working. syslog-ng has a

Oops, I didn't actually read the script, just saw the output from
"grep"...sorry.

-Richard

-- 
gentoo-user@gentoo.org mailing list