1 |
Hi Michael and all, |
2 |
|
3 |
I am going to try to give some input on this also. |
4 |
|
5 |
|
6 |
On Mon, Oct 13, 2003 at 02:56:00PM -0400, Michael J. Cohen wrote: |
7 |
> After wrestling with our current net implementation to get bridged interfaces |
8 |
> and vlans working, which ended in me just setting up things in local.start, I |
9 |
> figured a rewrite of our network scripts is in order. |
10 |
> |
11 |
> I have made a primitive version of the rewrite available here: |
12 |
> http://325i.org/proposed-net-replacement |
13 |
> |
14 |
> It is useless in its current state and only provided as an example. |
15 |
> |
16 |
> The reason for this rewrite is twofold: ease of configuration and ease of |
17 |
> maintenance. |
18 |
> |
19 |
> Here are a few of my ideas for the evolution of this currently primitive |
20 |
> rewrite: |
21 |
> |
22 |
> * all networking related configuration should take place in /etc/conf.d/net, |
23 |
> thus eliminating /etc/conf.d/iptables and such |
24 |
|
25 |
I don't agree that iptables should be a part of this; I think of setting up a firewall as a separate, but related task. I do, however, like the idea of one script, and one config file that controls bring up and down all of the network interfaces. |
26 |
> * bringing interfaces up and down should be handled by one script that |
27 |
> recognizes all possible up and down configurations of an interface, for |
28 |
> example, 802.1[d,q] (bridge,vlan), netfilter, dhcp, bootp.. |
29 |
|
30 |
I agree here. it would be nice to be able to have a script or utility that would handle all of this. Don't shoot me for this, lol, but I thought that debian's ifupdown utility was pretty slick. It had a configuration file that described all of the interfaces, the default gateway and whether or not interfaces should be brought up on bootup, and it was called by a single script that brought all of the interfaces up or down. |
31 |
|
32 |
> * configuration of iptables, ipsec, routing, etc should be handled by the up/ |
33 |
> down script calling the appropriate /etc/init.d scripts with the appropriate |
34 |
> arguments. these scripts would have to parse /etc/conf.d/net or rely on some |
35 |
> of the functions in /etc/init.d/net to parse it if the user should decide to |
36 |
> start/restart/reload a script individually |
37 |
|
38 |
I think these should stay separate. I guess my thinking here is that all systems that need to be on a network don't necessarily need these functions, so why make them part of the net script? |
39 |
|
40 |
> If anyone has any input, please feel free to speak your mind. |
41 |
> |
42 |
> I would love to see gentoo become the easiest distro to configure network |
43 |
> interfaces for *any* and *all* possible configurations, and I feel that this |
44 |
> is the first step to achieve that goal. |
45 |
|
46 |
Let me know what you think. |
47 |
|
48 |
William |
49 |
|
50 |
|
51 |
-- |
52 |
gentoo-dev@g.o mailing list |