Building a dual stack host

1
Building a dual stack host

• Rangers.ipv6.unl.edu
• Dale Finkelson

2
OS

• I started by installing Freebsd 4.4.
• Has the advantage of having the Kame stack
  compiled into the Kernel.
• I choose to use two names for the machine.
• One resolving to a v6 address
• One resolving to a v4 host
• In the rc.conf file I used the name
  rangers.unl.edu rather then the v6 name.
• For some reason this worked better.
• It messed up the window manager Gnome.
• My guess is Gnome didnt know how to deal with a
  AAAA record
• Not a big deal if you use another window manager.

3
Applications

• Named
• 4.4 came with 8.2.4
• This supports AAAA
• Configuration
• DNS will be done in more detail at another time
  in the workshop.

4
Applications

• Apache_1.3.20ipv6
• This was trivial. All I had to do was do a make
  in the ports directory.
• The config file is /usr/local/etc/apache/httpd.con
  f
• Apart from some http configuration there was
  nothing v6 specific to do.

5
Applications

• Mozilla-0.9.3.1ipv6
• This took forever to install. The compilation is
  huge. It probably cannot be done in a half day of
  a workshop.
• Unless your machine is faster.
• It worked just fine. However you will have a hard
  time convincing yourself if www.kame.net is not
  available.
• You need a v6 addressed server where you know you
  will use the v6 address.
• It does not display the address of the machine it
  is going to.
• I use different names for v4 and v6 on rangers.
  Thus by attaching to rangers.ipv6.unl.edu I
  convinced myself it works.

6
Applications

• Sendmail
• The sendmail in freebsd 4.4 is v6 capable. Its
  version 8.11.6.
• There is however configuration you need to do.
• In the M4 file, in my case this was
  /etc/mail/freebsd.mc, you need to add the
  following two lines.
• DAEMON_OPTIONS(NameMTA-v4, Familyinet)
• DAEMON_OPTIONS(NameMTA-v6, Familyinet6)

7
Sendmail Configuration

• In my machine the file /etc/mail/freebsd.mc
  contained the lines.
• I uncommented them.
• I copied the file to /usr/share/sendmail/cf/cf.
• Then /usr/share/sendmail/cf/m4/cf.m4 freebsd.mc gt
  freebsd.cf
• Copied freebsd.cf to sendmail.cf and restarted
  the sendmail process.
• It worked fine.
• Test this by telneting to port 25 on the v6
  hostname

8
Sendmail

• I could not make the m4 stuff work if I was in
  another directory then the one specified.
• The README file says to do a ./Build in the
  directory, but I could not get that to work.

9
Applications

• Cucipop-1.31
• Pop3 server
• There are several, I chose this one for no
  particular reason.
• Compiled and installed with no problem.
• Configuration
• By default pop3 is probably turned off in
  inetd.conf.
• Had to change the pop line in inetd.conf from tcp
  to tcp6 or create a new one so it would support
  both.
• Restart inetd

10
Applications

• Sylpheed.0.6
• A v6 complient mail client.
• Complied and installed just fine.
• Configuration
• I configured it to use rangers.ipv6.unl.edu as
  the sending and receiving host.
• Set up a user
• Testing
• This will be hard to test as someone else with a
  v6 capable mailer needs to mail you a message.
• In a workshop this could be done and mail could
  move back and forth there.

11
Applications

• Those are the major ones that I know of that will
  provide the major services that at least I use
  most of the time.
• I also installed some tools.

12
Tools

• Ethereal 0.9.1
• Easy to compile and install.
• Will receive and decode v6 packets.
• At least to the extent that you know how to use
  ethereal.
• Good for exploring and verifying the packet flows
  for neighbor discovery or stateless autoconfig as
  well as verifying packets are using v6 addresses.

13
Tools

• Netperf-2.1.3
• Compiled and installed fine.
• I have no clue if it works.

14
Tools

• Pchar-1.4
• This does the path charactistics.
• Works with v6 addresses.

15
Failures

• I had two packages that are claimed to work but
  that I could not make work.
• Mtr 0.45
• This is a ping/traceroute tool. It would not
  resolve a v6 hostname or work with a v6 address.
• Ncftp 3.1.2
• Same problem. It failed to resolve v6 hostnames
  or use v6 addresses.

16
Conclusion

• Over about 3 days, I was able to build a dual
  stack workstation that can
• Do DNS for ipv6.unl.edu
• Send and receive mail
• Host a web site
• Use other v6 web sites
• Do some network analysis and testing.
• There are also of course the standard tools line
  ping6 and traceroute6 that are simply included in
  4.4.
• This is Unix specific. I suspect that Linux with
  Usagi will have very similar results.