status

Francis Dupont fdupont at isc.org
Fri Mar 2 18:05:14 UTC 2012


AFTR/PCP: checked compilation with VS11beta
bind10: nothing at all
bind9: got some issues with VS11beta, pushed to resume the ECDSA support
 as the code points are available
DHCPv4 over IPv6:
 - wrote the CRA (Client Relay Agent) code and doc, tested on a VM
  (named CRA) with "./dhccra -d -i eth1 2001:0:0:1:1".
  A constraint (from the spec): it doesn't need to be colocated but
  it can handle only one link on the IPv4 side. Note the IPv6 must
  use the same interface but it is the way it is supposed to be used.

 - wrote the TRA (IPv6-Transport Relay Agent) code and doc, tested
  on a VM (named TRA) with "./dhctra -d 192.168.0.40".
  A bug: the interface used by IPv6 must have an IPv4 address (but
  this seems to not be a problem for real world deployment).

 - still wait for the TSV (IPv6-Transport SerVer) as it is very far
  from being trivial, both for the code and for the config
  (another occurence of the server with relays lack of doc/FAQ)

 - improved the standard (i.e., over IPv6) server to handle the
  Relay Agent 6ADDR new (sub)option so it can localize TRAs.
  Used to test the CRA and TRA chain.

Plans are:
 - TSV code and doc + tests
 - test the SD-AFTR hacks (i.e., static NAT entries to micmic
  a real SD-AFTR)
 - if wanted, add the icmp (echo) protocol to A+P/PRR entries
  so they will be usable for a pure A+P/PRR CGN (pure == doing
  in this case no translation at all)
 - various base code updates
 - miniupnpd SD support (still need a name for it)

Regards

Francis Dupont <fdupont at isc.org>

PS: DHCPv4 over IPv6 current schema:

    IPv4 link         IPv6 network            IPv4 network
 <--------------> <--------------------> <--------------------->
Client -DHCPv4- CRA -DHCPv4-over-IPv6- TRA -DHCPv4+RAI/6ADDR- Server

CPE SOW:

    Same box         IPv6 network
 <--------------> <-------------------->
Client -DHCPv4- CRA -DHCPv4-over-IPv6- TSV

BTW the dhcpd.conf I use:
 - the shared-network is to localize the TRA and what is behind
 - the subnet6 empty declaration matches the IPv6 address of
  the RAI 6ADDR and is the main extension I made to the server.
 - the last (and empty) subnet is to make the server happy:
  without it the server fails saying it can't find an interface:
  "Not configured to listen on any interfaces!"
  (this is one of the strange things when one configures a server
   to serve only clients behind relays)

The file itself:

# for talking to a TRA

allow unknown-clients;
default-lease-time 1800;
max-lease-time 7200;

local-address 192.168.0.40;

shared-network vmnet1 {
 subnet 10.0.0.0 netmask 255.255.255.0 {
  range 10.0.0.100 10.0.0.199;
 }
 subnet6 2001:0:0:1::/64 { }
}

subnet 192.168.0.0 netmask 255.255.255.0 {
}


More information about the sdcpe-devel mailing list