Progress with demo to Juniper / DT

[Francis Dupont]

> 1) second B4 running on one of the Netgear boxes.

=> the AFTR has the provision for 3 B4s, two WNDR boxes and the laptop,
so the idea is to adapt the laptop B4 config to the WNDR setup.

> 2) second AFTR working with fail-over

=> outside the network, edit the /etc/network/interfaces to give it
its own MAC addresses and the 208.223.208.13 address, shutdown it,
connect it to the Ethernet, boot it, copy the config from .12 to it,
including the MAC addresses and co (there should be a directory from
Paris with all files), shutdown it.

At this point you have two identical (at the exception of the sticker)
boxes so you can go from one to the other using suspend. Of course
if both are active at the same time it will deadly confused switches.

Note for the services you need:
 - the network setup (/etc/network/interfaces)
 - the proxy arp (run once the proxy script if Dave didn't put it
  in one of the network setup hook)
 - named (you should have nothing to do as it uses the standard install
  and config, i.e., just do a 'dig xxx @::1' to check if the DNS doesn't
  work as it should (*))
 - the 2 DHCP servers (binaries and configs in the compilation
  directory. The TSV is harder to run so the first line of tsv.conf
  provides a hint for the command line to use)
 - the AFTR (in ~dtaht/rt28354, it seems it is now in a rc so the detail
  to remember is the default command channel port is 1015).

(*) on the laptop B4 NetworkManager (aka NetworkMangler :-) can junk
/etc/resolv.conf. It did it once yesterday...

Regards

Francis Dupont <fdupont at isc.org>

PS: the DNS service is done by:

for the hosts by the dnsmasq running on the attached B4, its IPv4 address
is given by the DHCPv4 server on the B4.

On B4s dnsmasq uses /etc/resolv.conf (set by the DHCPv6 client) to relay
to the caching server on the AFTR at the address 2001:db8:0:1::1

On the AFTR named with the standard install/config provides a caching
service.

PPS: the way a B4 etablished the services:
 - first it runs a DHCPv6 client which gets:
  * its IPv6 address, netmask, gateway, DNS server and AFTR parameters
 - the DHCPv6 client calls a script which does the next step
  (aka setup6) and launches dnsmasq
 - establish the DS-Lite tunnel and routing
 - launch a DHCPv4 over IPv6 CRA to relay requests to the TSV
 - launch a DHCPv4 client which gets:
  * its IPv4 address, netmask and SD parameters (aka the port range)
 - the DHCPv4 client calls a script which finishes this (aka setup4)
 - add a multicast route (so the AFTR is no longer busy to drop multicast
  packets it doesn't know how to NAT :-)
 - launch a DHCPv4 server for the hosts
 - (missing today) enable the IPv4 routing
 - setup the netfilter filter/nat rules, including for sdctld
 - launch the sdctld (i.e., the miniupnpd with PCP server and SD port
  range mapping)
 - (not yet) launch the ICMP 3/13 handler (Dave's crazymon or my prmon)
  for unexpected port range reconfig