IETF50 IPv6 network instructions
$Id: index.html,v 1.2 2001/05/17 12:26:20 itojun Exp $
IETF50 has finished.
Thank you to all IPv6 users and Lucent NOC team!
Statistics
- # of IPv6 hosts on links
(host count = those responds to link-local ping6)
note that there were 900+ IPv4 users (as told in plenary session),
so nearly 8% of the machines understands IPv6 ping.
- traffic by Omnisci Eden
(user: ietf50 password: ietf50)
- # of connections went through TCP translator.
"# of clients" suggests the number of IPv6-only users, who have
configured their laptop as described in "advanced configuration" section.
| 3/17 Sat
| 3/18 Sun
| 3/19 Mon
| 3/20 Tue
| 3/21 Wed
| 3/22 Thu
| 3/23 Fri
|
|---|
| http | 367
| 671
| 1462
| 681
| 1151
| 2775
| 664
|
|---|
| ssh | 62
| 90
| 127
| 149
| 212
| 126
| 8
|
|---|
| pop3 | 30
| 13
| 12
| 17
| 21
| 15
| 3
|
|---|
| smtp | 27
| 91
| 44
| 62
| 239
| 222
| 37
|
|---|
| https | 0
| 74
| 30
| 19
| 0
| 13
| 1
|
|---|
| telnet | 4
| 0
| 0
| 4
| 1
| 0
| 0
|
|---|
| ftp | 4
| 19
| 3
| 3
| 9
| 6
| 0
|
|---|
| finger | 0
| 0
| 1
| 0
| 0
| 0
| 0
|
|---|
| icb | 0
| 3
| 0
| 0
| 3
| 0
| 0
|
|---|
| whois | 0
| 0
| 4
| 3
| 0
| 0
| 0
|
|---|
| # of clients | 4
| 10
| 13
| 19
| 15
| 13
| 3
|
|---|
Basic configuration
- Which network segments are IPv6 ready?
- Laptop term room, and 802.11 wireless segment.
- IPv6 global address prefix?
- 3ffe:0507:01ff:0001::/64 (ethernet in laptop term room)
- 3ffe:0507:01ff:0002::/64 (802.11 wireless)
- How to configure my notebook PC?
- Use IPv6 stateless address autoconfiguration
(RFC2462).
- Quick autoconf howto:
NetBSD
OpenBSD
FreeBSD
BSD/OS
Win2k
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)
- Service time?
- Whenever terminal cluster is running.
Hopefully 24hours, starting from Saturday 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.
- 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
ietf50@kame.net.
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 135.222.63.249
- 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
- Need additional tcp port to be translated? Contact
ietf50@kame.net.
- DHCPv6 server?
- Yes, it is running (draft-ietf-dhc-dhcpv6-15),
supplying DNS server address and timezone information only.
No address assignment is made by DHCPv6 server
(because of this, O bit on router advertisement is turned on).
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.
- List of wireless basestation that has the problem (overstriked ones were already corrected, thanks!):
BSSID 00:02:2d:1c:f4:04, @ 3F near Director's room #3
BSSID 00:60:1d:f6:b4:28, @ 3F near big ballroom D
BSSID 00:60:1d:1e:ee:91, @ 3F near big ballroom D
BSSID 00:60:1d:21:7c:2e, @ 3F near big ballroom E/F
BSSID 00:02:2d:08:5c:cc, @ 3F near big ballroom B
BSSID 00:02:2d:0f:08:15, @ 3F near Salon C
BSSID 00:60:1d:f6:b4:1c, @ 3F near Salon A
- Another problem we are seeing is that, even though it is announced that
WEP is supported as an optional feature, some of the baesstations
do not take WEP-enabled packets from laptops.
You may try turning WEP off.
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.5S, 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.
Misc.
- Stuffed "KAME" turtles?
- We will be distributing a limited number of
stuffed "KAME" turtles.
$12/turtle.
Contact itojun, or KAME guys, for details.
[IIJ research laboratory]
[IETF50]
[IETF50 term room/social]
