On Wed, Apr 23, 2008 at 10:04:38PM +0100, Roy Marples wrote:
> On Wednesday 23 April 2008 21:46:18 Robin H. Johnson wrote:
> > On Wed, Apr 23, 2008 at 04:21:27PM +0100, Roy Marples wrote:
> > > OK, it seems that hard lines in multipart configs seem to be an issue, so
> > > I'm doing this now.
> > >
> > > For a summary of why we're using hard lines you can read this thread
> > > http://thread.gmane.org/gmane.linux.gentoo.devel/45756/focus=45765
> >
> > Do you plan to reimplement parsing of the complete ip syntax for
> > addresses and routes?
> 
> Not at all. If I did then we're back to using newlines.
> Basically we need something like
> ipaddrs=address1 address2 address3
> for addresses, and
> routes=dest gateway dest gateway dest gateway
> or
> routes=route1 route2 route3
> route1=dest gateway
> route2=dest gateway
> route3=dest gateway
> for routes
The problem in this is that you cannot set the properties for each
address or route. Please don't take us back to the stoneage of writing
the advanced networking configuration manually.

As an example of an ip address line with properties:
${ext}.30/32 broadcast - scope host

An an example of a route with properties:
${int}.192/27 dev bond0 mtu 1500 table internal scope link
(my normal mtu on the internal link is 9k, but part of the subnet runs
at 1500 for netbooting on dumb cards)

Doing these in {pre,post}{up,down} means we basically end up
reimplementing the baselayout1 array-based config manually in the
blocks. I already do that for the ip_rule_runner block.

> No, we won't support that. However, we will bring back ip ranges for the last 
> ocet like so
> 1.2.3.4-10/24
I care about the address ranges far less than the additional properties.

> After seeing that I take it you'ed vote for the BSD named routing style?
I'm ambivalent about the naming scheme - I do care greatly about the
easy of configuration for the properties.

-- 
Robin Hugh Johnson
Gentoo Linux Developer & Infra Guy
E-Mail     : [EMAIL PROTECTED]
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

Attachment: pgpFz0PgcO6WO.pgp
Description: PGP signature

Reply via email to