HEADSUP: Network interface cloning changes
brooks at one-eyed-alien.net
Tue Jun 22 20:24:15 GMT 2004
I just commited network interface cloning. For most users there are no
effects. The single real exception is that users who create their
stf(4) interface with the command "ifconfig stf" will get an interface
named stf rather then stf0 and ifconfig will not print "stf0" to stdout.
For the record: THERE ARE NO OTHER CHANGES TO THINGS THAT PREVIOUSLY
- Creation and configuration of vlans can be accomlished with "ifconfig
<interface>.<tag> create". There is no support for this in etc yet
so it's not fully useable.
- stf(4) interfaces can be created with "ifconfig 6to4" inaddition to
"ifconfig stf" and "ifconfig stf0". This mostly exists as an easier
to understand example of the new cloning code then that provided by
the new vlan code.
- Attempting to "ifconfig lo0 destory" now fails rather then panicing
This change will require a recompile of modules using cloning and
modification of external ones to the new API. __FreeBSD_version has
been bumped to 502119 to mark this change.
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
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040622/16e0224d/attachment.bin
More information about the freebsd-current