Call for testers: RFC 5569 (6rd) support in stf(4)

[Hiroki Sato]

Ondoy <loki.fab at gmail.com> wrote
  in <AANLkTiko-wzTDMcLXw8OQokizzEiwwDsDpP1yP94yKJC at mail.gmail.com>:

lo> Hello Hiroki,
lo>
lo> Thanks for your reply.
lo> I think I now see how you this is supposed to work.
lo> What I didn't (crucially) get first was that the BR IPv4 address is configured
lo> at the CE when adding the IPv6 default route.
lo>
lo> It is simpler to get when 6rdPrefixLen is 32 and IPv4MaskLen is 0.
lo> Now I'm trying to figure out how to configure a CE using different
lo> parameters (all else the same with your sample setup).
lo>
lo> For example:
lo> IPv4MaskLen   = 8
lo> 6rdPrefix        = 2001:db8:dd00::
lo> 6rdPrefixLen     = 40
lo> 6rdBRIPv4Address = 192.0.2.1 (c0 00 02 01)
lo>
lo> given:
lo> CE WAN IPv4      = 192.0.2.2 (c0 00 02 02)
lo> so we'll get:
lo> 6rd delegated prefix (at the CE LAN side) = 2001:db8:dd00:0202::/64
lo>
lo> To configure the LAN side interface, stf, and route:
lo> # ifconfig fxp0 inet6 2001:db8:dd00:0202::1/64
lo> # ifconfig stf0 inet6 2001:db8:dd00:0202::/32
lo> # route add -inet6 default 2001:db8:ddc0:0002:0100::1
lo> Is the above correct, or am I way off target?

 Ahh, no, the embedded IPv4 address only supports exactly 32-bit
 length currently.  I am working on the shorter case
 (i.e. 6rdBRIPv4Address cannot be extracted from 6rdPrefix in a simple
 way), so please wait for the next patch ;)

 The current implementation is limited to the cases of "0 <
 6rdPrefixLen < 32" and BR IPv4 address is embedded in the same way as
 6to4.

-- Hiroki
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-net/attachments/20100924/1cd313da/attachment-0001.pgp