1 |
Why not make the script back out of everything its done? I.e., rather than downing the interface, unset any networking things it has set. Unconfigure the ip, etc. |
2 |
|
3 |
A super network interface control script would be cool too, something that is kept up to date and understands all of the Linux networking features that may be applicable. Maybe like a single script that by itself is device agnostic (could configure a normal nic or a bridge interface or some other complex, abstract thing (with ipv4 and ipv6 support)) and figures out what it should do based on a plethora of directives in /etc/conf.d/net. |
4 |
|
5 |
Like right now, I've got a bridge interface on my Gentoo box, but to run it I made a copy of the init.d script and put a couple bridging commands in there. It'd be cleaner if I could just inform it about bridging information in /etc/conf.d/net and the init script would understand and do it. |
6 |
|
7 |
On Sat, 31 May 2003 23:29:27 -0400 |
8 |
Peter Johanson <latexer@g.o> wrote: |
9 |
|
10 |
> I really prefer the first method, as it provides much finer grained |
11 |
> control. I've got a net6.ethX script mostly done, but i wanted to get |
12 |
> some feedback and opinions before fully implementing. The one major |
13 |
> sticking point is how to deal with the current "do something or die and |
14 |
> bring the interface down" situation. This behavior would obviously have |
15 |
> to change. |
16 |
> |
17 |
> -pete |
18 |
> |
19 |
> |
20 |
> -- |
21 |
> Peter Johanson |
22 |
> <latexer@g.o> |
23 |
> |
24 |
|
25 |
|
26 |
-- |
27 |
|
28 |
-- |
29 |
gentoo-dev@g.o mailing list |