wireless and service dependencies

G'day all,

I'm having this problem.  During startup both sshd and ntpd
are not
started with a warning: "scheduled to start when
net.eth0 is started"

eth0 is my wired network interface, eth1 is my wireless
interface.

I rarely used a wired network, often use the wireless
network.

This behaviour is fine, to certain extent, because if
net.eth0 comes up
I'd be happy to have sshd and ntpd start.

However, I also want them to start if and when net.eth1
comes up.

I have searched for a dependency setting somewhere but can't
find. Can
anyone point me in the right direction?

Cheers,

W.
-- 
gentoo-laptopgentoo.org mailing list

Will Briggs wrote:
> G'day all,
>
> I'm having this problem.  During startup both sshd and
ntpd are not
> started with a warning: "scheduled to start when
net.eth0 is started"
>
> eth0 is my wired network interface, eth1 is my wireless
interface.
>
> I rarely used a wired network, often use the wireless
network.
>
> This behaviour is fine, to certain extent, because if
net.eth0 comes up
> I'd be happy to have sshd and ntpd start.
>
> However, I also want them to start if and when net.eth1
comes up.
>
> I have searched for a dependency setting somewhere but
can't find. Can
> anyone point me in the right direction?
>
> Cheers,
>
> W.
>   
Did you;
# ln -s net.lo /etc/init.d/net.eth1
# rc-update add net.eth1 default

-- 
Powered by Gentoo/Linux

-- 
gentoo-laptopgentoo.org mailing list

david wrote:
> Will Briggs wrote:
>> G'day all,
>>
>> I'm having this problem.  During startup both sshd
and ntpd are not
>> started with a warning: "scheduled to start
when net.eth0 is started"
>>
>> eth0 is my wired network interface, eth1 is my
wireless interface.
>>
>> I rarely used a wired network, often use the
wireless network.
>>
>> This behaviour is fine, to certain extent, because
if net.eth0 comes up
>> I'd be happy to have sshd and ntpd start.
>>
>> However, I also want them to start if and when
net.eth1 comes up.
>>
>> I have searched for a dependency setting somewhere
but can't find. Can
>> anyone point me in the right direction?
>>
>> Cheers,
>>
>> W.
>>   
> Did you;
> # ln -s net.lo /etc/init.d/net.eth1

Yes. (Well, on checking it wasn't /etc/init.d/net.eth1 ->
net.lo but
/etc/init.d/net.eth1 -> /etc/init.d/net.lo.  I've changed
that but I
suspect it makes no difference having the path in the
symlink)

> # rc-update add net.eth1 default
> 

No - but deliberately.  I think this may be where I, or the
system is
confused.  Because unlike a desktop it's not just a matter
of bringing
up the /etc/init.d/net.* scripts.  I don't want DHCP
timeouts etc. when
booting off-line.

net.eth0 is brought up by netplug

net.eth1 is brought up by as I understand it, the ipw3945
module being
loaded which runs the ipw3945 daemon, which runs
wpa_supplicant, which
runs the init script (maybe those last two steps are vice
versa)

So, currently:
/etc/init.d/net.eth0 status
 * status:  inactive

(which is fine, the wire isn't plugged in)

/etc/init.d/net.eth1 status
 * status:  started

which is fine, but I want sshd and ntpd to have recognised
this

In the end I want the services brought up when either or
both of
net.eth0 or net.eth1 are started (by cables being plugged in
or wireless
networks coming up etc.)

Thanks for the response,

W.




-- 
gentoo-laptopgentoo.org mailing list

On Fri, 13 Apr 2007, Will Briggs wrote:
> david wrote:
> > Will Briggs wrote:
> >> G'day all,
> >>
> >> I'm having this problem.  During startup both
sshd and ntpd are not
> >> started with a warning: "scheduled to
start when net.eth0 is started"

I get the same behaviour.
> >>
> >> eth0 is my wired network interface, eth1 is my
wireless interface.
> >>
> >> I rarely used a wired network, often use the
wireless network.

Life for the modern laptop at home  Same
here.
> >>
> >> This behaviour is fine, to certain extent,
because if net.eth0 comes up
> >> I'd be happy to have sshd and ntpd start.
> >>
> >> However, I also want them to start if and when
net.eth1 comes up.

I have the same question!
> >>
> >> I have searched for a dependency setting
somewhere but can't find. Can
> >> anyone point me in the right direction?
> >>
> >> Cheers,
> >>
> >> W.
> >
> > Did you;
> > # ln -s net.lo /etc/init.d/net.eth1
>
> Yes. (Well, on checking it wasn't /etc/init.d/net.eth1
-> net.lo but
> /etc/init.d/net.eth1 -> /etc/init.d/net.lo.  I've
changed that but I
> suspect it makes no difference having the path in the
symlink)

It makes no difference (assuming you were in /etc/init.d in
the first place).
>
> > # rc-update add net.eth1 default
>
> No - but deliberately.  I think this may be where I, or
the system is
> confused.  Because unlike a desktop it's not just a
matter of bringing
> up the /etc/init.d/net.* scripts.  I don't want DHCP
timeouts etc. when
> booting off-line.

Not only that, but there's some automagic code in the rc
scripts that will try 
to bring the interfaces up without linking it to a soft
runlevel. So 
actually, you're better off not doing it. 
>
> net.eth0 is brought up by netplug

Actually the message is that net.eth0 is invoking netplug to
wait for eth0 in 
the background. I could never work out why that doesn't work
with net.eth1.

>
> net.eth1 is brought up by as I understand it, the
ipw3945 module being
> loaded which runs the ipw3945 daemon, which runs
wpa_supplicant, which
> runs the init script (maybe those last two steps are
vice versa)
>
> So, currently:
> /etc/init.d/net.eth0 status
>  * status:  inactive
>
> (which is fine, the wire isn't plugged in)
>
> /etc/init.d/net.eth1 status
>  * status:  started
>
> which is fine, but I want sshd and ntpd to have
recognised this
>
> In the end I want the services brought up when either
or both of
> net.eth0 or net.eth1 are started (by cables being
plugged in or wireless
> networks coming up etc.)
>
> Thanks for the response,
>
> W.

I guess what we both actually want is for these network
dependent services to 
come up when *any* external network interface is functional.
But how?


Regards,

Mike
-- 
gentoo-laptopgentoo.org mailing list

Mike Benson wrote:
> 
> I guess what we both actually want is for these network
dependent services to 
> come up when *any* external network interface is
functional. But how?

Thanks for the clarification.  This is it exactly.

Here's some clue I guess:

grep -R "is scheduled to start" /etc/*
init.d/runscript.sh:                    ewarn "WARNING:
 $ is
scheduled to start when $ has started."
init.d/runscript.sh:                            ewarn
"WARNING:  $ is
scheduled to start when $ has started."

but all that looks like it is doing is handling the
dependencies - where
are they set?

W.

-- 
gentoo-laptopgentoo.org mailing list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

Study /etc/conf.d/net.example and write a postup() function
in /etc/conf.d/net ; Postup is my
preferred way of starting sshd and ntpd, because my wireless
network is managed by
wpa_supplicant. Then, when I move my laptop from an access
point to another, such services must
be restarted. Nothing better than having Gentoo restarting
such services for you.

Here goes an example:

postup () {
  /etc/init.d/ntpd restart
  /etc/init.d/sshd restart
  /etc.init.d/cupsd restart
}

For a more complicated example, including dhcp services on a
per-AP basis, email me!

Good day.

Will Briggs wrote:
> G'day all,
> 
> I'm having this problem.  During startup both sshd and
ntpd are not
> started with a warning: "scheduled to start when
net.eth0 is started"
> 
> eth0 is my wired network interface, eth1 is my wireless
interface.
> 
> I rarely used a wired network, often use the wireless
network.
> 
> This behaviour is fine, to certain extent, because if
net.eth0 comes up
> I'd be happy to have sshd and ntpd start.
> 
> However, I also want them to start if and when net.eth1
comes up.
> 
> I have searched for a dependency setting somewhere but
can't find. Can
> anyone point me in the right direction?
> 
> Cheers,
> 
> W.


- --
Fabio A. Correa D.

Physics Dept, Universidad Nacional, Bogota, Colombia
facorreadgmail.com
ffaaccddyahoo.co.uk         facorreadunal.edu.co
My webpage and OpenPGP key at http://facorread.150m.com
facorreadalexandria.cc is not working anymore!!!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFGH4NYYOZCB4zf2uQRApknAJ4zcAC+S0ZjbeZX3Ux2LChBK8sV0wCf
cjW9
tm6mzQzEWOP2Xwfg6xrT/YY=
=zRDp
-----END PGP SIGNATURE-----
-- 
gentoo-laptopgentoo.org mailing list

On Fri, Apr 13, 2007 at 08:19:20AM -0500, Fabio A Correa
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello,
> 
> Study /etc/conf.d/net.example and write a postup()
function in /etc/conf.d/net ; Postup is my
> preferred way of starting sshd and ntpd, because my
wireless network is managed by
> wpa_supplicant. Then, when I move my laptop from an
access point to another, such services must
> be restarted. Nothing better than having Gentoo
restarting such services for you.
> 
> Here goes an example:
> 
> postup () {
>   /etc/init.d/ntpd restart
>   /etc/init.d/sshd restart
>   /etc.init.d/cupsd restart
> }
> 

...

> > 
> > This behaviour is fine, to certain extent, because
if net.eth0 comes up
> > I'd be happy to have sshd and ntpd start.


Is there a specific reason why you have to restart sshd
after you
restart/change network services? I don't know about ntpd and
cupsd
because I start them only in some places, but I have sshd
running all
the time (with RC_NET_STRICT_CHECKING="lo" in
/etc/conf.d/rc) it works
correctly (it listens on 0.0.0.0 so any ip changes don't
affect it).
I suppose cupsd and ntpd should be the same (well maybe they
would have
to be configured to listen on 0.0.0.0, if they are listening
on the ip
from an interface by default...)

yoyo


-- 
      _
      |            icq: 177861806                    jabber:
yoyojabber.cz
YoYo () Siska      web: http://people.ksp.sk/~yoy
o/

-- 
gentoo-laptopgentoo.org mailing list

YoYo Siska wrote:
> 
> Is there a specific reason why you have to restart sshd
after you
> restart/change network services? I don't know about
ntpd and cupsd
> because I start them only in some places, but I have
sshd running all
> the time (with RC_NET_STRICT_CHECKING="lo" in
/etc/conf.d/rc) it works
> correctly (it listens on 0.0.0.0 so any ip changes
don't affect it).
> I suppose cupsd and ntpd should be the same (well maybe
they would have
> to be configured to listen on 0.0.0.0, if they are
listening on the ip
> from an interface by default...)
> 

Aaaah - that's where it is.  Thanks, this gives me the
answer I need.
I'll still play with Fabio's tips though - but I think they
are for a
more specific need.

W.
-- 
gentoo-laptopgentoo.org mailing list