| 1 |
After wrestling with our current net implementation to get bridged interfaces |
| 2 |
and vlans working, which ended in me just setting up things in local.start, I |
| 3 |
figured a rewrite of our network scripts is in order. |
| 4 |
|
| 5 |
I have made a primitive version of the rewrite available here: |
| 6 |
http://325i.org/proposed-net-replacement |
| 7 |
|
| 8 |
It is useless in its current state and only provided as an example. |
| 9 |
|
| 10 |
The reason for this rewrite is twofold: ease of configuration and ease of |
| 11 |
maintenance. |
| 12 |
|
| 13 |
Here are a few of my ideas for the evolution of this currently primitive |
| 14 |
rewrite: |
| 15 |
|
| 16 |
* all networking related configuration should take place in /etc/conf.d/net, |
| 17 |
thus eliminating /etc/conf.d/iptables and such |
| 18 |
* bringing interfaces up and down should be handled by one script that |
| 19 |
recognizes all possible up and down configurations of an interface, for |
| 20 |
example, 802.1[d,q] (bridge,vlan), netfilter, dhcp, bootp.. |
| 21 |
* configuration of iptables, ipsec, routing, etc should be handled by the up/ |
| 22 |
down script calling the appropriate /etc/init.d scripts with the appropriate |
| 23 |
arguments. these scripts would have to parse /etc/conf.d/net or rely on some |
| 24 |
of the functions in /etc/init.d/net to parse it if the user should decide to |
| 25 |
start/restart/reload a script individually |
| 26 |
|
| 27 |
If anyone has any input, please feel free to speak your mind. |
| 28 |
|
| 29 |
I would love to see gentoo become the easiest distro to configure network |
| 30 |
interfaces for *any* and *all* possible configurations, and I feel that this |
| 31 |
is the first step to achieve that goal. |
| 32 |
|
| 33 |
------ |
| 34 |
Michael J. Cohen |
| 35 |
|
| 36 |
|
| 37 |
-- |
| 38 |
gentoo-dev@g.o mailing list |
Archives