VLAN support in rcNG [PATCH]

[Brooks Davis]

On Sat, Apr 17, 2004 at 11:21:23PM -0400, Adam C. Migus wrote:
> Quoting Brooks Davis <brooks at one-eyed-alien.net>:
> 
> > On Sat, Apr 17, 2004 at 08:20:17PM -0400, Matthew N. Dodd wrote:
> > > On Sat, 17 Apr 2004, Brooks Davis wrote:
> > > > It works by doing a major overhaul of the device cloning support
> > so you
> > > > can create interfaces of the form <etherif>.<vlantag> and get an
> > vlan
> > > > interface with the appropriate parent and tag.
> > > 
> > > Please make this behavior optional.
> > 
> > The entire patch has exactly one change which is visiable to the
> > userland unless the user changes their behavior.  That change is
> > that
> > when you do "ifconfig stf create" ifconfig does not output "stf0"
> > and
> > the interface created is named "sft" instead of "stf0".  This is a
> > result of a minor change that allows you to create "6to4" a more
> > aptly named interface.  This change is mostly an example of how to
> > write
> > new style interface cloners that's easier to understand then the
> > vlan
> > version which was the motivation for this overhaul.
> > 
> > The vlan change allows vlan interfaces to work exactly like they did
> > before.  It just adds some sugar so that the following sets of
> > commands
> > are equivalent:
> > 
> > ifconfig xl0.2
> > 
> > vlanif=`ifconfig vlan create`
> > ifconfig $vlanif name xl0.2
> > ifconfig xl0.2 vlandev xl0 vlantag 2
> > 
> > -- Brooks
> > 
> > -- 
> > Any statement of the form "X is the one, true Y" is FALSE.
> > PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4
> > 
> 
> So it sounds like I say:
> 
> cloned_interfaces="xl0.2"
> 
> and get myself the interface I want, on the right vlan but what happens
> when I want to say:
> 
> ifconfig_xl0.2="DHCP"
> 
> That `.' is going to cause some problems isn't it?

Yah, that's a definite issue.  I could add another seperator fairly
easy, care to suggest one?

> I asked earlier for reasons like this and compatability in general if
> there would be a way to create vlan interfaces named "vlan2" for
> example.
>
> The trouble with this naming convention is it doesn't imply it's
> physical device in it's name but the name doesn't contain a `.' which
> in things like sh(1) can cause problems.
>
> My patch may be a little more cumbersome, requiring explicit naming of
> the device but it does eliminiate ambiquity and permit that naming
> scheme with the ability to do DHCP and not trip over some other things
> in rcNG.

I don't have any strong objections to your patch.

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040417/3ccc1093/attachment.bin