| 1 |
Tobias Klausmann dixit (2010-09-20, 20:34): |
| 2 |
|
| 3 |
> On Mon, 20 Sep 2010, Benedikt Böhm wrote: |
| 4 |
> > On Mon, Sep 20, 2010, Tobias Klausmann <klausman@g.o> wrote: |
| 5 |
> > > who runs servers: DHCP is uncommon there, WLAN is very unusual, |
| 6 |
> > > as a result, they would not only have to switch the way they |
| 7 |
> > > configure their nets (people don't like that kind of stuff if the |
| 8 |
> > > machine is 400 miles away); they would also have to find a way to |
| 9 |
> > > build their setups in the new "language". Servers tend to have |
| 10 |
> > > more complicated setups network-wise than workstations (think |
| 11 |
> > > firewalls, VPN endpoint, traffic observation, ...). |
| 12 |
> > |
| 13 |
> > the same is true for everyone who already runs newnet (like me). in |
| 14 |
> > fact, i do not even use the newnet conf.d stuff, but rather take |
| 15 |
> > advantage of support for /etc/ifup.eth* in /etc/init.d/network. that |
| 16 |
> > way i can configure the networking with iproute2 or any other tool |
| 17 |
> > that i already know the syntax of. no need to learn ridiculously |
| 18 |
> > convoluted array syntax foo for /etc/init.d/net.eth*. |
| 19 |
> > |
| 20 |
> > so please just keep the network init script as a use flag or extra |
| 21 |
> > package or something, so that one is not forced to use the old net |
| 22 |
> > stuff (again). |
| 23 |
> > |
| 24 |
> > P.S.: newnet does not in any way force you to use DHCP or WLAN or |
| 25 |
> > anything like that, so please stop spreading misinformation. |
| 26 |
> |
| 27 |
> Still, newnet is geared towards such setups and it is reflected |
| 28 |
> in the way it handles things. /This/ I meant by "language". And |
| 29 |
> yes, going from complicated arrays to iproute2 syntax *is* a |
| 30 |
> change that may blow up in your face, if you don't use those |
| 31 |
> tools every day. |
| 32 |
|
| 33 |
As far as I can see, oldnet (at least if you do modules="iproute2" |
| 34 |
which most sane users probably do) is *also* basically iproute2 |
| 35 |
syntax, only wrapped in some arrays: |
| 36 |
|
| 37 |
routes_Okno=( "default via 192.168.0.254" |
| 38 |
"default via 2001:foo:bar::1" ) |
| 39 |
|
| 40 |
I could add other typical iproute2 clauses to that config, like src |
| 41 |
<ip>, or metric <n>. Same with the IP address clause. |
| 42 |
|
| 43 |
Flexible, already documented. +1 for keeping oldnet. |
| 44 |
|
| 45 |
-- |
| 46 |
[a] |
Archives