(I'm a bit undecided if this is a doc-bug or a change-request, but I think the former is certain, the latter could be useful.) Let me explain: when a server changes IPv4 it can (in some cases) have both as aliases for a while, so that the change does not imply downtimes. Using 6to4 this does not appear to be the case: interface stf1 can't be created (and this is the documentation bug: "man stf" states that "Each stf interface is created at runtime using interface cloning") and adding an alias address to the existing stf0 interface does no effect at all: only the first address is used (and this is the change request: either support both address or maybe forbid adding a second alias, if that's possible). In reference (and a bit more verboseness), two messages by myself in the freebsd-net mailing list: http://lists.freebsd.org/pipermail/freebsd-net/2009-March/021271.html http://lists.freebsd.org/pipermail/freebsd-net/2009-July/022591.html
State Changed From-To: open->suspended Mark suspended awaiting patches.
Responsible Changed From-To: freebsd-bugs->freebsd-net Over to maintainer(s).
batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.