[gentoo-user] Disabling net.ath0 backgrounding

[gentoo-user] Disabling net.ath0 backgrounding

[Grant]

How can I keep net.ath0 from "backgrounding" at boot?  I like to see
the ouput and the backgrounding causes ntp-client, ntpd, and netmount
to display a warning.

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Disabling net.ath0 backgrounding

[darren kirby]

quoth the Grant:
> How can I keep net.ath0 from "backgrounding" at boot?  I like to see
> the ouput and the backgrounding causes ntp-client, ntpd, and netmount
> to display a warning.
>
> - Grant

I could of course be wrong, but I think you will need to 'unbackground' 
everything. Ie: RC_PARALLEL_STARTUP="no" in /etc/conf.d/rc

-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
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Disabling net.ath0 backgrounding

[Boyd Stephen Smith Jr.]

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

On Wednesday 04 October 2006 11:38, Grant <emailgrant@gmail.com> wrote 
about '[gentoo-user] Disabling net.ath0 backgrounding':
> How can I keep net.ath0 from "backgrounding" at boot?

This is ifplugd or netplug waiting until link is established before 
configuring the device.  They are also responsible for bring the device up 
and down is response to link failure and reestablishment.  Normally, this 
is a desired behavior because it, for example, only brings up your 
laptop's wired connection if it is actually plugged in and automatically 
brings it down when you unplug.

If you want to disable one or the other for a particular device, you can 
add !netplug or !ifplugd to the modules list of that interface 
(see /etc/conf.d/net.example for details).  You can also disable link 
detection entirely by adding !plug to the modules list of that interface.

An alternative that may be closer to what you want, is to let 
ifplugd/netplug wait for some period of time before backgrounding.  This 
still allows the interface to be started and stopped in response to link 
status, but when explicitly started, it will perform configuration in the 
foreground if link is detecting before timeout.  To establish such a 
timeout add:plug_timeout="<seconds>" to your network configuration

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

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

Re: [gentoo-user] Disabling net.ath0 backgrounding

[Grant]

> > How can I keep net.ath0 from "backgrounding" at boot?
>
> This is ifplugd or netplug waiting until link is established before
> configuring the device.  They are also responsible for bring the device up
> and down is response to link failure and reestablishment.  Normally, this
> is a desired behavior because it, for example, only brings up your
> laptop's wired connection if it is actually plugged in and automatically
> brings it down when you unplug.
>
> If you want to disable one or the other for a particular device, you can
> add !netplug or !ifplugd to the modules list of that interface
> (see /etc/conf.d/net.example for details).  You can also disable link
> detection entirely by adding !plug to the modules list of that interface.
>
> An alternative that may be closer to what you want, is to let
> ifplugd/netplug wait for some period of time before backgrounding.  This
> still allows the interface to be started and stopped in response to link
> status, but when explicitly started, it will perform configuration in the
> foreground if link is detecting before timeout.  To establish such a
> timeout add:plug_timeout="<seconds>" to your network configuration

I tried the following in /etc/conf.d/net :

modules_ath0=( "!plug" )

but it still goes into "backgrounding".  When ath0 won't connect to
the wireless network I need to be able to see more about what is
happening when it's trying to connect.  Is that still possible?

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Disabling net.ath0 backgrounding

[Boyd Stephen Smith Jr.]

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

On Sunday 22 October 2006 12:01, Grant <emailgrant@gmail.com> wrote 
about 'Re: [gentoo-user] Disabling net.ath0 backgrounding':
> I tried the following in /etc/conf.d/net :
>
> modules_ath0=( "!plug" )
>
> but it still goes into "backgrounding".

That shouldn't happen.

Please post the output of:
equery b /etc/init.d/net.lo
equery l baselayout
equery k baselayout
ls -ld /etc/init.d/net.*
grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net
grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net
if /etc/init.d/net.ath0 status | grep -q started; then
    /etc/init.d/net.ath0 restart
else
    /etc/init.d/net.ath0 start
fi

> When ath0 won't connect to 
> the wireless network I need to be able to see more about what is
> happening when it's trying to connect.  Is that still possible?

Should be, unless it is something peculiar about wireless (don't use 
wireless much) or atheros cards specifically.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

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

Re: [gentoo-user] Disabling net.ath0 backgrounding

[Grant]

> > I tried the following in /etc/conf.d/net :
> >
> > modules_ath0=( "!plug" )
> >
> > but it still goes into "backgrounding".
>
> That shouldn't happen.
>
> Please post the output of:

I upgraded to the masked version of baselayout this morning to try and
fix this, but the stable version worked exactly the same way as far as
not connecting and backgrounding.

> equery b /etc/init.d/net.lo

sys-apps/baselayout-1.13.0_alpha2-r1 (/etc/init.d/net.lo ->
../../lib64/rcscripts/sh/net.sh)

> equery l baselayout

sys-apps/baselayout-1.13.0_alpha2-r1

> equery k baselayout

113 out of 150 files good, with a list of "has wrong mtime"

> ls -ld /etc/init.d/net.*

/etc/init.d/net.ath0 -> net.lo
/etc/init.d/net.eth0 -> net.lo
/etc/init.d/net.lo -> ../../lib64/rcscripts/sh/net.sh

> grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net

modules="wpa_supplicant"
wpa_supplicant_ath0="-Dmadwifi"
config_ath0=( "192.168.0.3 netmask 255.255.255.0 broadcast 192.168.0.255" )
routes_ath0=( "default via 192.168.0.1" )
essid_ath0="network2"
modules_ath0=( "!plug" )

> grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net
> if /etc/init.d/net.ath0 status | grep -q started; then
>     /etc/init.d/net.ath0 restart
> else
>     /etc/init.d/net.ath0 start
> fi

How can I execute this from the command line?

> > When ath0 won't connect to
> > the wireless network I need to be able to see more about what is
> > happening when it's trying to connect.  Is that still possible?
>
> Should be, unless it is something peculiar about wireless (don't use
> wireless much) or atheros cards specifically.

Please also let me know if you see anything that looks like it might
be preventing net.ath0 from connecting.  It's been slowly getting less
and less reliable, and now it won't connect no matter how many times I
ask.  net.ath0 on my laptop connects perfectly every time.

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Disabling net.ath0 backgrounding

[Boyd Stephen Smith Jr.]

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

On Sunday 22 October 2006 14:12, Grant <emailgrant@gmail.com> wrote 
about 'Re: [gentoo-user] Disabling net.ath0 backgrounding':
> > equery b /etc/init.d/net.lo
>
> sys-apps/baselayout-1.13.0_alpha2-r1 (/etc/init.d/net.lo ->
> ../../lib64/rcscripts/sh/net.sh)

Hrm, that's new.
My net.lo is not a symlink.

> > equery l baselayout
>
> sys-apps/baselayout-1.13.0_alpha2-r1

But I'm still on baselayout-1.12

> > equery k baselayout
>
> 113 out of 150 files good, with a list of "has wrong mtime"

You can confirm those are all configuration files?  If not, please provide 
the list...

> > grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net
>
> modules="wpa_supplicant"
> wpa_supplicant_ath0="-Dmadwifi"
> config_ath0=( "192.168.0.3 netmask 255.255.255.0 broadcast
> 192.168.0.255" ) routes_ath0=( "default via 192.168.0.1" )
> essid_ath0="network2"
> modules_ath0=( "!plug" )

It's possible, albeit unlikely, that the two modules lines are conflicting, 
try removing both of them and adding:
modules_ath0=( "wpa_supplicant" "!plug")
above your config_ath0 line.

This may also be some behavior that is wpa_supplicant specific and I've 
never used that particular piece of software.

> > grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net

Sorry, that should have been:
grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/wireless

> > if /etc/init.d/net.ath0 status | grep -q started; then
> >     /etc/init.d/net.ath0 restart
> > else
> >     /etc/init.d/net.ath0 start
> > fi
>
> How can I execute this from the command line?

You should just be able to type it in or cut/copy and paste from my 
original email.  bash (and indeed most shells) don't interpret the input 
from the command line significantly different than the content of a script 
file.

> Please also let me know if you see anything that looks like it might
> be preventing net.ath0 from connecting.  It's been slowly getting less
> and less reliable, and now it won't connect no matter how many times I
> ask.  net.ath0 on my laptop connects perfectly every time.

:(
Sorry, I'm just not that wireless savvy, but everything looks fine to me.  
Again, keep in mind that I've never used wpa_supplicant so I don't know if 
that changes things.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

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

Re: [gentoo-user] Disabling net.ath0 backgrounding

[Grant]

> > > equery b /etc/init.d/net.lo
> >
> > sys-apps/baselayout-1.13.0_alpha2-r1 (/etc/init.d/net.lo ->
> > ../../lib64/rcscripts/sh/net.sh)
>
> Hrm, that's new.
> My net.lo is not a symlink.
>
> > > equery l baselayout
> >
> > sys-apps/baselayout-1.13.0_alpha2-r1
>
> But I'm still on baselayout-1.12
>
> > > equery k baselayout
> >
> > 113 out of 150 files good, with a list of "has wrong mtime"
>
> You can confirm those are all configuration files?  If not, please provide
> the list...

They are all in /etc/ (including many init.d) except for:

/sbin/runscript.sh
/sbin/functions.sh
/lib64/rcscripts/sh/net.sh
/sbin/depscan.sh

Some of them show incorrect md5sum instead of wrong mtime.

> > > grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net
> >
> > modules="wpa_supplicant"
> > wpa_supplicant_ath0="-Dmadwifi"
> > config_ath0=( "192.168.0.3 netmask 255.255.255.0 broadcast
> > 192.168.0.255" ) routes_ath0=( "default via 192.168.0.1" )
> > essid_ath0="network2"
> > modules_ath0=( "!plug" )
>
> It's possible, albeit unlikely, that the two modules lines are conflicting,
> try removing both of them and adding:
> modules_ath0=( "wpa_supplicant" "!plug")
> above your config_ath0 line.

I changed that with no luck.

> This may also be some behavior that is wpa_supplicant specific and I've
> never used that particular piece of software.
>
> > > grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net
>
> Sorry, that should have been:
> grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/wireless

I actually don't have that file at all.

> > > if /etc/init.d/net.ath0 status | grep -q started; then
> > >     /etc/init.d/net.ath0 restart
> > > else
> > >     /etc/init.d/net.ath0 start
> > > fi
> >
> > How can I execute this from the command line?
>
> You should just be able to type it in or cut/copy and paste from my
> original email.  bash (and indeed most shells) don't interpret the input
> from the command line significantly different than the content of a script
> file.

If I use spaces instead of line breaks so I can put it all on one line
it doesn't seem to work out.  I'm missing something here.

- Grant

> > Please also let me know if you see anything that looks like it might
> > be preventing net.ath0 from connecting.  It's been slowly getting less
> > and less reliable, and now it won't connect no matter how many times I
> > ask.  net.ath0 on my laptop connects perfectly every time.
>
> :(
> Sorry, I'm just not that wireless savvy, but everything looks fine to me.
> Again, keep in mind that I've never used wpa_supplicant so I don't know if
> that changes things.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Disabling net.ath0 backgrounding

[Grant]

> Sorry, I'm just not that wireless savvy, but everything looks fine to me.
> Again, keep in mind that I've never used wpa_supplicant so I don't know if
> that changes things.

I'm using wpa_supplicant so I can connect via WPA encryption.  Do you
know if I should be able to do that with wireless-tools instead?

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Disabling net.ath0 backgrounding

[Boyd Stephen Smith Jr.]

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

On Sunday 22 October 2006 16:07, Grant <emailgrant@gmail.com> wrote 
about 'Re: [gentoo-user] Disabling net.ath0 backgrounding':
> > > How can I execute this from the command line?
> > You should just be able to type it in or cut/copy and paste from my
> > original email.  bash (and indeed most shells) don't interpret the
> > input from the command line significantly different than the content
> > of a script file.
> If I use spaces instead of line breaks so I can put it all on one line
> it doesn't seem to work out.  I'm missing something here.

You should be able to use linebreaks; bash will, appropriately, wait for 
more input if you are in the middle of a larger construct (if/while/etc.).

You should also be able to use spaces, but you have to add a semi-colon 
after each simple command.  If I was to do it as a one-liner it would be:
if /etc/init.d/net.ath0 status | grep -q started; then /etc/init.d/net.ath0 
restart; else /etc/init.d/net.ath0 start; fi

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

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

Re: [gentoo-user] Disabling net.ath0 backgrounding

[Boyd Stephen Smith Jr.]

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

On Sunday 22 October 2006 16:07, Grant <emailgrant@gmail.com> wrote 
about 'Re: [gentoo-user] Disabling net.ath0 backgrounding':
> > > > equery b /etc/init.d/net.lo
> > >
> > > sys-apps/baselayout-1.13.0_alpha2-r1 (/etc/init.d/net.lo ->
> > > ../../lib64/rcscripts/sh/net.sh)
> >
> > Hrm, that's new.
> > My net.lo is not a symlink.
> >
> > > > equery l baselayout
> > >
> > > sys-apps/baselayout-1.13.0_alpha2-r1
> >
> > But I'm still on baselayout-1.12
> >
> > > > equery k baselayout
> > >
> > > 113 out of 150 files good, with a list of "has wrong mtime"
> >
> > You can confirm those are all configuration files?  If not, please
> > provide the list...
>
> They are all in /etc/ (including many init.d) except for:
>
> /sbin/runscript.sh
> /sbin/functions.sh
> /lib64/rcscripts/sh/net.sh
> /sbin/depscan.sh
>
> Some of them show incorrect md5sum instead of wrong mtime.

Hrm, I can't think of a good reason those files should have the wrong 
md5sum.  A wrong mtime could be caused by mtime fixups done by the init 
system, but an incorrect md5sum is most likely breakage.

> > > > grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net
> > Sorry, that should have been:
> > grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/wireless
> I actually don't have that file at all.

Hrm, I know wireless-tools uses (or used) the configuration in that file; I 
would imagine wpa_supplicant would as well, but I've never used it.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

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

Re: [gentoo-user] Disabling net.ath0 backgrounding

[Boyd Stephen Smith Jr.]

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

On Sunday 22 October 2006 16:09, Grant <emailgrant@gmail.com> wrote 
about 'Re: [gentoo-user] Disabling net.ath0 backgrounding':
> > Sorry, I'm just not that wireless savvy, but everything looks fine to
> > me. Again, keep in mind that I've never used wpa_supplicant so I don't
> > know if that changes things.
> I'm using wpa_supplicant so I can connect via WPA encryption.  Do you
> know if I should be able to do that with wireless-tools instead?

From the documentation in wireless.example (which is only used with 
iwconfig / wireless-tools) you can do WPA on certain drivers, like the 
rt2500.

I believe you will need to use wpa_supplicant with your atheros chipset.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

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

Re: [gentoo-user] Disabling net.ath0 backgrounding

[Boyd Stephen Smith Jr.]

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

On Sunday 22 October 2006 14:12, Grant <emailgrant@gmail.com> wrote 
about 'Re: [gentoo-user] Disabling net.ath0 backgrounding':
> > > I tried the following in /etc/conf.d/net :
> > >
> > > modules_ath0=( "!plug" )
> > >
> > > but it still goes into "backgrounding".
> > That shouldn't happen.
> >
> > Please post the output of:
> > grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net
>
> modules="wpa_supplicant"
> wpa_supplicant_ath0="-Dmadwifi"
> config_ath0=( "192.168.0.3 netmask 255.255.255.0 broadcast
> 192.168.0.255" ) routes_ath0=( "default via 192.168.0.1" )
> essid_ath0="network2"
> modules_ath0=( "!plug" )

Around line 159 in my net.example says:
# By default don't wait for wpa_suppliant to associate and authenticate.
# If you would like to, so can specify how long in seconds
#associate_timeout_eth0=60
# A value of 0 means wait forever.

It may be possible that you need to set this variable to 0 to prevent 
backgrounding, independent of the ifplugd/netplug quashing.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

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

Re: [gentoo-user] Disabling net.ath0 backgrounding

[Grant]

> > > > I tried the following in /etc/conf.d/net :
> > > >
> > > > modules_ath0=( "!plug" )
> > > >
> > > > but it still goes into "backgrounding".
> > > That shouldn't happen.
> > >
> > > Please post the output of:
> > > grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net
> >
> > modules="wpa_supplicant"
> > wpa_supplicant_ath0="-Dmadwifi"
> > config_ath0=( "192.168.0.3 netmask 255.255.255.0 broadcast
> > 192.168.0.255" ) routes_ath0=( "default via 192.168.0.1" )
> > essid_ath0="network2"
> > modules_ath0=( "!plug" )
>
> Around line 159 in my net.example says:
> # By default don't wait for wpa_suppliant to associate and authenticate.
> # If you would like to, so can specify how long in seconds
> #associate_timeout_eth0=60
> # A value of 0 means wait forever.
>
> It may be possible that you need to set this variable to 0 to prevent
> backgrounding, independent of the ifplugd/netplug quashing.

I set that variable and it does seem to stop the backgrounding, but
I'm not given any more information than I was with backgrounding
unless it connects.  I could be wrong, but I thought I was getting
more information before.

Incidentally, I am able to connect to the AP this morning.  The next
time I can't connect I'll try different channels as I do live in an
apartment.

For some reason, I don't seem to have DNS service although I am
connected to the network and Internet.  DNS comes from my Gentoo
router (dnsmasq), and my other system connected to it is getting
lookups just fine.  I have added:

nameserver 192.168.0.1

to /etc/resolv.conf and restarted net.ath0 to no avail.  I suppose
baselayout -1.13* could be causing this problem somehow.  Downgrading
back to a stable baselayout caused all kinds of errors to pop up in
different places.  I believe they were net.lo errors, so maybe they
have to do with the net.lo symlink you noticed?

/etc/init.d/net.lo -> ../../lib64/rcscripts/sh/net.sh

I'd like to get back on a stable baselayout if possible.

- Grant
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Disabling net.ath0 backgrounding

[Grant]

> > > > I tried the following in /etc/conf.d/net :
> > > >
> > > > modules_ath0=( "!plug" )
> > > >
> > > > but it still goes into "backgrounding".
> > > That shouldn't happen.
> > >
> > > Please post the output of:
> > > grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net
> >
> > modules="wpa_supplicant"
> > wpa_supplicant_ath0="-Dmadwifi"
> > config_ath0=( "192.168.0.3 netmask 255.255.255.0 broadcast
> > 192.168.0.255" ) routes_ath0=( "default via 192.168.0.1" )
> > essid_ath0="network2"
> > modules_ath0=( "!plug" )
>
> Around line 159 in my net.example says:
> # By default don't wait for wpa_suppliant to associate and authenticate.
> # If you would like to, so can specify how long in seconds
> #associate_timeout_eth0=60
> # A value of 0 means wait forever.
>
> It may be possible that you need to set this variable to 0 to prevent
> backgrounding, independent of the ifplugd/netplug quashing.

I found this that mentions disabling backgrounding:

http://gentoo-wiki.com/HARDWARE_wg511t

but the quoted portion of net.lo doesn't seem to exist in the latest
stable version.

- Grant
-- 
gentoo-user@gentoo.org mailing list