On Tue, Jan 3, 2012 at 8:23 AM, Devin Teske <devin.te...@fisglobal.com> wrote:
>> -----Original Message-----
>> From: Mohacsi Janos [mailto:moha...@niif.hu]
>> Sent: Tuesday, January 03, 2012 3:59 AM
>> To: Devin Teske
>> Cc: freebsd-hackers@freebsd.org; Dave Robison; Devin Teske
>> Subject: Re: [ANN] host-setup 4.0 released
>>
>> Hi Devin,
>> I had a look at the code. It is very nice,
>
> Thank you.
>
>
>> however there are same missing
>> elements:
>> - IPv6 support
>
> Open to suggestions.
>
> Maybe adding a "ipaddr6" below "ipaddr" in the interface configuration menu.
>
> Also, do you happen to know what the RFC number is for IPv6 address format? I
> need to know all the special "features" (for example, I know you can specify
> "::1" for localhost, but can you simply omit octets at-will? e.g.,
> ::ff:12:00:::
> ?)
>
>
>> - VLAN tagging support - creation/deleting
>
> How is that done these days? and how might we present it in the user
> interface?
http://www.cyberciti.biz/faq/howto-configure-freebsd-vlans-with-ifconfig-command/
Adding a means to create lagged interfaces might be a good idea,
but that's also more complicated than setting up a vlan interface.
The problem from a user perspective with how we present vlans in
FreeBSD is that it isn't tied directly to an interface, so it's
confusing for newbies when they're trying to grok how vlans work.
In general you have a couple properties to make the user aware of:
1. My parent interface.
2. My vlan tag.
3. Other good stuff like MTU, HW Filters (which I've never used),
HW TSO, etc.
MTU is also kind of tricky because you can set a vlan interface's
MTU to something greater than the MTU of the lower interface and
things won't fail properly IIRC (or maybe that was just a bug in
FreeNAS.. I forget).
Cheers,
-Garrett
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
