[gentoo-dev] net.eth0

[gentoo-dev] net.eth0

[Frederick Reeve]

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

Hey guys.

I have made some small changes to the default /etc/inid.d/net.eth0 and
/etc/conf.d/net.  These changes simply add functionality alowing for an
alternate ip config should dhcpcd fail to find a server.  I made these
small changes because I use a labtop and when I would boot away from my
network apache, fam, and other needed daemons would fail causing poblems
for many programs (at least ones I run) and this prevents this.  Anyway
I have included the files.  Please look at them and tell me what you
think.  I have CLEARLY marked what I changed.

I'm very sorry if this is the wrong place to submit this.  I looked for
a good place honest and this is what I ended up with.

Also I have a question to put out.  Does anyone have a good reason not
to add a force option to emerge.  The way I see it the worst that can
happen is the package fails to build.  I have had a couple our users ask
for this in #gentoo irc the last couple of days and I wouldn't mind
seeing it my self.  It wouldn't be hard to do maybe I could 'try' if no
one objects.  It may also be needed to include a note with this function
that states using it could cause conflicks.  I have been editing my
/usr/portage/profiles/package.mask and that get old fast when over
writen every sync.

Well thanks for listening.

Frederick <sabin>



[-- Attachment #2: net-update.tar.gz --]
[-- Type: application/x-gzip, Size: 2309 bytes --]

[-- Attachment #3: Type: text/plain, Size: 37 bytes --]

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] net.eth0

[Martin Schlemmer]

On 08 Mar 2003 21:46:10 +0100
Frederick Reeve <frederick@woodland-i.org> wrote:

> Hey guys.
> 
> I have made some small changes to the default /etc/inid.d/net.eth0 and
> /etc/conf.d/net.  These changes simply add functionality alowing for
> an alternate ip config should dhcpcd fail to find a server.  I made
> these small changes because I use a labtop and when I would boot away
> from my network apache, fam, and other needed daemons would fail
> causing poblems for many programs (at least ones I run) and this
> prevents this.  Anyway I have included the files.  Please look at them
> and tell me what you think.  I have CLEARLY marked what I changed.
> 
> I'm very sorry if this is the wrong place to submit this.  I looked
> for a good place honest and this is what I ended up with.
> 

Well, looks good.  Maybe add it as a bug at bugs.gentoo.org.  And if
possible rather add the diffs of the files (diff -u net.eth0.orig
net.eth0).


Regards,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] net.eth0

[Frederick Reeve]

> Isn't the --nodeps options that what you are looking for?
> 
>        --nodeps (-O short option)
>               Merge specified packages, but don't merge any dependencies.
>               Note that the build may fail if deps aren't satisfied.
> 

No nodeps doesn't ignore the fact a package is masked allowing a merge
of a package that is masked.  Many masked packages will install and
correctly especially when you are talking about whats masked out for
alpha.  a force option would allow users to easily test the masked out
packages for themselves (without changing there package.mask file) and
they in return could give you reports.

Frederick <sabin>




--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] net.eth0

[Frederick Reeve]

> With force option, you mean an option that installs the package, even if
> it is masked?
> 
> We're looking at ways to eliminate package.mask for portage 2.1, but it'd be 
> done without using 'force'.

This is exactly what I meant.

Good well I guess you are a few steps ahead of me.

Frederick <sabin>




--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] net.eth0

[Sven Vermeulen]

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

On Sat, Mar 08, 2003 at 09:46:10PM +0100, Frederick Reeve wrote:
> Also I have a question to put out.  Does anyone have a good reason not
> to add a force option to emerge.  The way I see it the worst that can
> happen is the package fails to build. 

Isn't the --nodeps options that what you are looking for?

       --nodeps (-O short option)
              Merge specified packages, but don't merge any dependencies.
              Note that the build may fail if deps aren't satisfied.

Wkr,
	Sven Vermeulen

-- 
	Fighting for peace is like fucking for virginity.

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

Re: [gentoo-dev] net.eth0

[Joseph Carter]

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

On Sun, Mar 09, 2003 at 11:02:07AM +0100, Frederick Reeve wrote:
> > With force option, you mean an option that installs the package, even if
> > it is masked?
> > 
> > We're looking at ways to eliminate package.mask for portage 2.1, but it'd be 
> > done without using 'force'.
> 
> This is exactly what I meant.
> 
> Good well I guess you are a few steps ahead of me.

I don't think this is quite enough actually.  It's one thing to fall to a
usable state on failure to find a DHCP server, and I think it's good that
this has been done finally, this only handles half the problem.  Once the
interface is brought up using a random IP, it is necessary to be able to
rescan for DHCP servers after, say, you plug the cable in.  Once you do
that, you probably would want to restart a set of services such as apache
to get them listening on the new port.

I'd suggest setting a few environment vars and throwing run-parts at a
directory after the interface is brought up.  These can, eg, check to see
if apache has been started yet and restart it if necessary.  They could
also, for wireless links, start aphopper (probably only appropriate when
that program matures a little more), or other things like that.  Really
there are lots of possibilities here.

For those interfaces which support it (e100 does at least), you could use
ifplugd (not yet in portage because I've gotten too busy of late to finish
the ebuild and submit it) and it would then automatically recheck for a
DHCP server and restart necessary services upon plugging in the network
cable.

-- 
Joseph Carter <knghtbrd@efn.org>                  SCO must cease to exist!
 
<Espy> I invoke Espy's law, which states that you all suck :P


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

Re: [gentoo-dev] net.eth0

[Sven Vermeulen]

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

On Sun, Mar 09, 2003 at 10:58:53AM +0100, Frederick Reeve wrote:
> No nodeps doesn't ignore the fact a package is masked allowing a merge
> of a package that is masked.  Many masked packages will install and
> correctly especially when you are talking about whats masked out for
> alpha.  a force option would allow users to easily test the masked out
> packages for themselves (without changing there package.mask file) and
> they in return could give you reports.

You mean the equivalent of
~# emerge /usr/portage/<categorie>/<package>/<package>-<version>.ebuild
but without having to type everything? Because the above will not check if
the package is masked or not...

Mvg,
	Sven Vermeulen

-- 
	Fighting for peace is like fucking for virginity.

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

Re: [gentoo-dev] net.eth0

[Wout Mertens]

On Sun, 9 Mar 2003, Joseph Carter wrote:
> On Sun, Mar 09, 2003 at 11:02:07AM +0100, Frederick Reeve wrote:
> I'd suggest setting a few environment vars and throwing run-parts at a
> directory after the interface is brought up.  These can, eg, check to see
> if apache has been started yet and restart it if necessary.  They could
> also, for wireless links, start aphopper (probably only appropriate when
> that program matures a little more), or other things like that.  Really
> there are lots of possibilities here.

I guess Azarah could add support for a /etc/net.d/ directory with scripts
that are called with the arguments <interface> <state>. Or something along
those lines. I know I would like something that reconfigures my wwwoffle
for the current network automatically.

> For those interfaces which support it (e100 does at least), you could use
> ifplugd (not yet in portage because I've gotten too busy of late to finish
> the ebuild and submit it) and it would then automatically recheck for a
> DHCP server and restart necessary services upon plugging in the network
> cable.

Well, I've been playing with mii-tool, and I made a script that did this,
but I had some problems with daemonization, and in the end I just wrote
the ebuild for ifplugd. I just committed it, so give it a whirl.
(it's in ~x86)

It's really easy, just start it with the init script and it will bring up
the interface if possible.

Cheers,

Wout.

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] net.eth0

[Joseph Carter]

[-- Attachment #1: mutt-galen-12253-15 --]
[-- Type: text/plain, Size: 2041 bytes --]

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

On Mon, Mar 17, 2003 at 04:35:30PM +0100, Wout Mertens wrote:
> I guess Azarah could add support for a /etc/net.d/ directory with scripts
> that are called with the arguments <interface> <state>. Or something along
> those lines. I know I would like something that reconfigures my wwwoffle
> for the current network automatically.

I rather like Debian's ifupdown more than the net.iface scripts.  It does
not yet integrate ifplugd's functions, but I would not mind seeing Gentoo
able to work with that at some point.  ifupdown is especially nice for
PCMCIA and other hot-pluggable network interfaces.  I won't suggest that
Gentoo move from the net.iface scripts to it until such time as it can do
PPP links of various sorts.  I'm pretty sure it can do PPPoE, but not
PPPoA or standard {a,}sync PPP (modem and ISDN) connections.


> Well, I've been playing with mii-tool, and I made a script that did this,
> but I had some problems with daemonization, and in the end I just wrote
> the ebuild for ifplugd. I just committed it, so give it a whirl.
> (it's in ~x86)
> 
> It's really easy, just start it with the init script and it will bring up
> the interface if possible.

I've known how to use ifplugd since it was first put into Debian.  Thanks
for making it work on a Gentoo box, I've been up to my eyeballs in other
obligations.

- -- 
Joseph Carter <knghtbrd@efn.org>                  SCO must cease to exist!
 
<Knghtbrd> Internet censorship.  Because your children need to be
           protected from naked women, medical procedures, diverse
	   cultures, and violent video games.
<knghtbrd> (but information on building bombs, stealing cable, and
           manufacturing drugs is okay...)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: 1024D/20F62261F1857A3E79FC44F98FF7D7A3DCF9DAB3

iEYEARECAAYFAj52jcwACgkQj/fXo9z52rOtKACgha3GMJHh3DXjfeCcZePmZDKs
I3MAn0vNzAy84zVlsC8shxpBwR1/l0M+
=0QNx
-----END PGP SIGNATURE-----

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] net.eth0

[Martin Schlemmer]

On Mon, 17 Mar 2003 16:35:30 +0100 (CET)
Wout Mertens <wmertens@gentoo.org> wrote:

> I guess Azarah could add support for a /etc/net.d/ directory with
> scripts that are called with the arguments <interface> <state>. Or
> something along those lines. I know I would like something that
> reconfigures my wwwoffle for the current network automatically.
> 

I have been thinking about this in the past (think there is a bug
about ipv6 that I suggested that we make it much more modular),
but I have been too busy, and I do not want to rush it and do
an half backed job that have to be redone/bandaged at some stage
in the future again.


Regards,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] net.eth0

[Wout Mertens]

Argh, wrong again :(

---------- Forwarded message ----------
Date: Wed, 19 Mar 2003 16:47:07 +0100 (CET)
From: Wout Mertens <wmertens@gentoo.org>
To: gentoo-dev@gentoo.com
Cc: Joseph Carter <knghtbrd@efn.org>,
     Frederick Reeve <frederick@woodland-i.org>,
     Alain Penders <alain@gentoo.org>, Martin Schlemmer <azarah@gentoo.org>
Subject: Re: [gentoo-dev] net.eth0

(People in Cc: Sorry for the repost, I used the wrong email-address)

On Tue, 18 Mar 2003, Martin Schlemmer wrote:
> On Mon, 17 Mar 2003 16:35:30 +0100 (CET)
> Wout Mertens <wmertens@gentoo.org> wrote:
>
> > I guess Azarah could add support for a /etc/net.d/ directory with
> > scripts that are called with the arguments <interface> <state>. Or
> > something along those lines. I know I would like something that
> > reconfigures my wwwoffle for the current network automatically.
>
> I have been thinking about this in the past (think there is a bug
> about ipv6 that I suggested that we make it much more modular),
> but I have been too busy, and I do not want to rush it and do
> an half backed job that have to be redone/bandaged at some stage
> in the future again.

Well, maybe we can kick off a conversation?
Some issues:
- Some people have static networks. It would be nice if there was a set
  way to detect and configure those. They can always hand-roll their own
  network scripts, but those will not be the same quality that we all can
  do.
- Some services bind on specific interfaces, and need to be notified when
  one comes up. (apache, squid, ...)
- Some services only need to know if there is network connectivity or not,
  and they need to be notified when the first interface comes up and the
  last interface goes down (ntp daemons, wwwoffle, ...)
- Some services would like to know when the ip address changes (dynamic
  dns, etc)
- There is currently no fixed way to setup your wireless interfaces. They
  have extra parameters that can be set by iwconfig (wireless-tools),
  which needs to be done before dhcpcd is called. A simple matter of
  adding iwconfig_${IFACE}, I think.
- At my company, we use LEAP authentication for wireless. This is a
  proprietary extension, but it's used by thousands of people. I'm not
  claiming that they are all using gentoo, but it would be cool to have
  support for this. How I do it, I first let dhcpcd fail, then set up the
  card for LEAP, run interactive authentication (xterm for the console
  user), and if it succeeded, run dhcpcd again.
- Some people want to use a different dhcp client
- Some interfaces have media detection. These could be automatically
  brought up when a cable is inserted. (See sys-apps/ifplugd)

So here is a modular approach:
- To bring an interface up, try a list of "activation" scripts that try to
  bring it up and test the outcome. Examples: a list of ips with an ip
  that should be active when up, dhcpcd, pump, leap-auth+dhcp, ... . The
  user chooses the order by setting up a net/activate.d directory, and
  several standard scripts are included (and they get info from
  /etc/conf.d/net). Scripts that just set up interfaces, like iwconfig,
  always fail after doing their stuff.
  These scripts also provide the command that needs to be run to shut down
  the interface again. This could be the script itself with different
  parameters.
- Any time networking parameters change, scripts in a net/event.d get
  called in order. They get the following parameters:
  - interface that changed
  - What happened to it: up, down, ipchange, linkup, linkdown
  - ip address of that interface
  - the "global" networking state: netup, netdown, netsame. This is for
    scripts that only care about the networking state and not about
    interfaces.
  If possible, the dhcp clients should also call these scripts when the
  ip address changed.
  Ifplugd could notify these script that the link went down, but wait a
  little while before actually bringing the interface down. This could be
  used to set wwwoffled or chronyd in offline mode without impacting
  running tcp connections. And when the link goes up again before the
  interface is brought down, this could be used to kick dhcpcd to verify
  the lease (dhcpcd -n).

A similar, and maybe cleaner approach would not use directories but just
strings with functions/scripts to be called, defined in /etc/conf.d/net.
(The rest stays the same)
Something like

activate_eth0="dhcp static"
activate_eth1="iwconfig static dhcp leap"
activate_ppp0="ppp" # Extra parameters in net.ppp0
events_eth0="apache"
events_ppp0="dyndns"
events_global="wwwoffled chronyd"

What do you think? I think this would be able to take all the things I
tried to do over the last few years :)

We could start prototyping something in a separate ebuild,
sys-apps/gentoo-net or something, and when it is stable, merge it back in
baselayout.

Comments?

Wout.

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] net.eth0

[Martin Schlemmer]

On Wed, 19 Mar 2003 15:46:37 +0100 (CET)
Wout Mertens <wmertens@cisco.com> wrote:

> activate_eth0="dhcp static"
> activate_eth1="iwconfig static dhcp leap"
> activate_ppp0="ppp" # Extra parameters in net.ppp0
> events_eth0="apache"
> events_ppp0="dyndns"
> events_global="wwwoffled chronyd"
> 
> What do you think? I think this would be able to take all the things I
> tried to do over the last few years :)
> 

Err, mind explaining a bit over here ?

> We could start prototyping something in a separate ebuild,
> sys-apps/gentoo-net or something, and when it is stable, merge it back
> in baselayout.
> 

Could work


Regards,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] net.eth0

[Wout Mertens]

On Fri, 21 Mar 2003, Martin Schlemmer wrote:

> On Wed, 19 Mar 2003 15:46:37 +0100 (CET)
> Wout Mertens <wmertens@cisco.com> wrote:
>
> > activate_eth0="dhcp static"
> > activate_eth1="iwconfig static dhcp leap"
> > activate_ppp0="ppp" # Extra parameters in net.ppp0
> > events_eth0="apache"
> > events_ppp0="dyndns"
> > events_global="wwwoffled chronyd"
> >
> > What do you think? I think this would be able to take all the things I
> > tried to do over the last few years :)
>
> Err, mind explaining a bit over here ?

Well, instead of hard-coding a few ways (ifconfig parameters or dhcp) of
bringing up the network interfaces, I propose a modular approach, where a
few functions/scripts are defined that can bring up the interface, and you
can define which ones you like in what order. To bring up the interface,
they will be called in order until one succeeds.

On top of that, I propose the same thing, but for events about network
interfaces. That way, you can add in dyndns clients, reconfigure
applications etc.

Configuration is still done through /etc/conf.d/net.

I have done a lot of weird stuff with my network scripts over the last few
years, and this approach would be able to do all the things I can
remember, in a way that can be automated and clean.

> > We could start prototyping something in a separate ebuild,
> > sys-apps/gentoo-net or something, and when it is stable, merge it back
> > in baselayout.
>
> Could work

Well, if there are no takers, I think I'll give that approach a whirl and
see what happens.

Wout.

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] net.eth0

[Paul de Vrieze]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 837 bytes --]

On Friday 21 March 2003 16:42, Wout Mertens wrote:
> Well, instead of hard-coding a few ways (ifconfig parameters or dhcp) of
> bringing up the network interfaces, I propose a modular approach, where a
> few functions/scripts are defined that can bring up the interface, and you
> can define which ones you like in what order. To bring up the interface,
> they will be called in order until one succeeds.
>

I like this idea, I personally did a hack that took the cache of my dhcpcd to 
bring my interface up. At the time the dhcp server of my ISP was failing 
every now and then. The IP did never change, but I wanted to be up without 
the dhcpd. It workes well, and I think other people might want similar 
things.

Paul

-- 
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.cs.kun.nl/~pauldv

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

Re: [gentoo-dev] net.eth0

[Martin Schlemmer]

On Fri, 21 Mar 2003 16:42:00 +0100 (CET)
Wout Mertens <wmertens@cisco.com> wrote:

> Well, instead of hard-coding a few ways (ifconfig parameters or dhcp)
> of bringing up the network interfaces, I propose a modular approach,
> where a few functions/scripts are defined that can bring up the
> interface, and you can define which ones you like in what order. To
> bring up the interface, they will be called in order until one
> succeeds.
> 
> On top of that, I propose the same thing, but for events about network
> interfaces. That way, you can add in dyndns clients, reconfigure
> applications etc.
> 
> Configuration is still done through /etc/conf.d/net.
> 
> I have done a lot of weird stuff with my network scripts over the last
> few years, and this approach would be able to do all the things I can
> remember, in a way that can be automated and clean.
> 

Yes, but I wanted a bit more specifics.

> Well, if there are no takers, I think I'll give that approach a whirl
> and see what happens.
> 

To be honest, my resources networks wise is very limited, and I would
appreciate it if somebody with enough pcmcia/wireless/dhcp/whatever
knowledge will take the network bit off my hands.

I do have one requirement though:  Please keep it sane, and me in
the loop for at least the initial stuff until we agree that it is
a workable solution.


Regards,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] net.eth0

[Nick Matthews]

On Sat, 22 Mar 2003 01:03:46 +0200
Martin Schlemmer <azarah@gentoo.org> wrote:

> On Fri, 21 Mar 2003 16:42:00 +0100 (CET)
> Wout Mertens <wmertens@cisco.com> wrote:
> 
> > Well, instead of hard-coding a few ways (ifconfig parameters or dhcp)
> > of bringing up the network interfaces, I propose a modular approach,
> > where a few functions/scripts are defined that can bring up the
> > interface, and you can define which ones you like in what order. To
> > bring up the interface, they will be called in order until one
> > succeeds.
> > 
> > On top of that, I propose the same thing, but for events about network
> > interfaces. That way, you can add in dyndns clients, reconfigure
> > applications etc.
> > 
> > Configuration is still done through /etc/conf.d/net.
> > 
> > I have done a lot of weird stuff with my network scripts over the last
> > few years, and this approach would be able to do all the things I can
> > remember, in a way that can be automated and clean.
> > 
> 
> Yes, but I wanted a bit more specifics.
> 
> > Well, if there are no takers, I think I'll give that approach a whirl
> > and see what happens.
> > 
> 
> To be honest, my resources networks wise is very limited, and I would
> appreciate it if somebody with enough pcmcia/wireless/dhcp/whatever
> knowledge will take the network bit off my hands.

Well, lets see here, I have a pcmcia setup, with both wireless and wired connections, I use dhcp most of the time, but need to use static ips as well. (My laptop at times needs to be used for static testing purposes on the same lan as an entirely different dhcp network)

I can certainly help test any network script changes. 

I need to have a look again as to whats currently going on, and then I might have some ideas and suggestions.

> 
> I do have one requirement though:  Please keep it sane, and me in
> the loop for at least the initial stuff until we agree that it is
> a workable solution.
> 
> 
> Regards,
> 
> -- 
> 
> Martin Schlemmer
> Gentoo Linux Developer, Desktop/System Team Developer
> Cape Town, South Africa
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
> 

--
gentoo-dev@gentoo.org mailing list