IETF52 IPv6 network instructions
$Id: index.html,v 1.13 2001/12/12 19:58:39 itojun Exp $
Basic configuration
- Which network segments are IPv6 ready?
- Laptop term room, and 802.11 wireless segment are planned to be IPv6 ready.
- IPv6 global address prefix?
- 3ffe:0507:01ff:0001::/64 (ethernet in laptop term room)
- 3ffe:0507:01ff:0002::/64 (802.11 wireless)
- 3ffe:0507:01ff:0004::/64 (Grand America hotel rooms)
- How to configure my notebook PC?
- Use IPv6 stateless address autoconfiguration
(RFC2462).
- Quick autoconf howto:
NetBSD
OpenBSD
FreeBSD
BSD/OS
Win2k
WinXP
Linux
- How do I get static IPv6 address?
- We do not do that. Autoconfigure it.
- IPv6 transport-ready nameservers?
- 3ffe:501:4819::42
- 3ffe:0:1::c620:242, 198.32.2.66 (z.ip6.int)
- 3ffe:50e::1 (y.ip6.int)
- 3ffe:b00:4000::1 (x.ip6.int)
- 3ffe:4::4 (w.ip6.int)
- Service time?
- Whenever terminal cluster is running.
Hopefully 24hours, starting from Sunday and
terminating around Friday noon.
- How to obtain IPv6 stacks and make my laptop IPv6 ready?
- In general: http://www.ipv6.org/impl/index.html
- BSDs:
OpenBSD 2.7,
NetBSD 1.5,
BSD/OS 4.0,
FreeBSD 4.0 or later have
IPv6 stack integrated.
- Linux
- depends on the distribution you are using.
See distribution status page and
conformance test comparison page.
- http://www.bieringer.de/linux/IPv6/ and
http://www.linux-ipv6.org/
have more info.
- WinXP:
IPv6 stack is integrated.
- Win2K:
IPv6 research releases from MS research
- Win95/98:
Trumpet IPv6 or
Hitachi Toolnet6
- Sun Solaris:
Solaris 8 has IPv6 stack integrated.
more info
- Any other questions?
- Do not hesitate to contact
ietf52@kame.net.
Stats
Advanced configuration
You can run your laptop IPv6-only and kiss DHCP good bye!
- IPv6-to-IPv4 translators?
- We have installed a TCP relay translator
(KAME faith implementation), for
popular TCP ports.
You need to change DNS server configuration to use the translator.
There is no other special requirements to laptop client side.
- Set your nameserver to 3ffe:507:1ff:1::53, or 12.131.198.4
- Your tcp traffic to 3ffe:507:1ff:ffff::ipv4addr will be relayed
to ipv4addr.
- Supported ports are: whois pop3 ftp telnet printer icb http https ssh smtp nntp finger cvspserver imap
- Need additional tcp port to be translated? Contact
ietf52@kame.net.
Troubleshooting
- I'm on wireless, no basestation visible
- Did you configure 802.11 SSID (network name) to "IETF"?
- I'm on wireless, IPv4 goes fine but IPv6 does not.
- Maybe there's some problem with the basestation you are connected with
(ethernet layer multicast turned off, preventing all IPv6 neighbor
discovery process). Take note of wireless basestation ID (BSSID),
and talk with NOC guys.
- If you cannot get replies to ping6 ff02::1 from anyone (except yourself), it is a sign of
this problem.
Details of configuration
- Connectivity to the outside world?
- RFC1933/
RFC2893
configured IPv6-over-IPv4 tunnel to
IIJ equipment
in Palo Alto, California (PAIX).
IPv4 traceroute for tunnel section.
-
IIJ router in PAIX
|
| IPv6 over IPv4 tunnel
|
venue IPv6 router
| |
==+== ==+==
wireless laptop term room
- Router equipment?
- NetBSD-current
(1.5X, KAME IPv6 stack intergrated)
running on top of
Wildlab LAMB.
Basically, LAMB is used as a plain 486 PC with two 10Base-T ethernet
interfaces.
[IIJ research laboratory]
[IETF52]