See INC0164829
pinger.slac.stanford.edu
A quick test to see if the host has full IPv6 capability is to run traceroute6
453cottrell@www3:~$traceroute6 ipv6.google.com traceroute to ipv6.google.com (2607:f8b0:4007:802::200e), 30 hops max, 80 byte packets connect: Network is unreachable Exit
To enable for IPv6:
- Had to get subnet enabled for IPv6 - Mark.
- Taylor blocks ipv6 by default for security reasons, so had to request to enable IPv6 for pinger in Taylor (INC0175010) - Karl
for taylor.opts on a linux server, I believe would look something like
ipv6addr=2620:114:d000:25a1::80/64,2620:114:d000:25a1::1
- Modifications to the PAN rules - Kent
- It will need an IPv6 address in NetDB
It may seem to have an IPv6 address by looking at ifconfig you may see
eth0 Link encap:Ethernet HWaddr 00:50:56:BE:3D:4C inet addr:134.79.197.214 Bcast:134.79.197.255 Mask:255.255.255.128 inet6 addr: 2620:114:d000:2716:250:56ff:febe:3d4c/64 Scope:Global inet6 addr: fe80::250:56ff:febe:3d4c/64 Scope:Link
The global ipv6 addr which is currently configure on www3 is probably the slaac (auto configured) from the router.
If the last couple octets look like a MAC address (versus zero or a very small number), then the address was almost certainly auto configured.The other way to convince yourself is to look at the DNS record for the given system (e.g. “host www3”). If there is no IPv6 address displayed, then the address got autoconfigured.
447cottrell@rhel6-64f:~$host www3 www3.slac.stanford.edu has address 134.79.197.214
pinger2.pl
Modified to enable both the hostname and IPv6 address to be the same.
traceroute.pl
Modified to make work on Solaris and Linux:
my $version="7.3, 12/13/2017, Les Cottrell";
# Added \[\] to untainting of dig command. Appears to be needed for IPv6.
# Do not avoid testing internal domains if server is IPv6 host,
# Added avoid calling gethostbyname6 if hostname is already an ipv6 address
# Fixed how Solaris mis-interprets system(@args) sometimes (saw in IPv6)
Hosts with IPv6 support
Pinger (Linux), www1 (Solaris), www3 (Linux), nospam2-out (Linux)
Looks like nospam2 is working for me. this is the ipv6 address for nospam2: ```ksa@nospam2 $ host nospam2-out nospam2-out.slac.stanford.edu has IPv6 address 2620:114:d000:2598::10 ksa@nospam2 $ ``` ```ksa@nospam2 $ host google.com | grep IPv6 google.com has IPv6 address 2607:f8b0:4005:808::200e ksa@nospam2 $ ping6 2607:f8b0:4005:808::200e PING 2607:f8b0:4005:808::200e(2607:f8b0:4005:808::200e) 56 data bytes 64 bytes from 2607:f8b0:4005:808::200e: icmp_seq=1 ttl=53 time=2.34 ms 64 bytes from 2607:f8b0:4005:808::200e: icmp_seq=2 ttl=53 time=2.24 ms 64 bytes from 2607:f8b0:4005:808::200e: icmp_seq=3 ttl=53 time=2.27 ms ^C --- 2607:f8b0:4005:808::200e ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2638ms rtt min/avg/max/mdev = 2.248/2.290/2.347/0.057 ms ksa@nospam2 $ ``` www1 also works: 435cottrell@www1:~>ping -s -A inet6 -a 2607:f8b0:4005:805::200e PING 2607:f8b0:4005:805::200e: 56 data bytes 64 bytes from 2607:f8b0:4005:805::200e: icmp_seq=0. time=2.58 ms 64 bytes from 2607:f8b0:4005:805::200e: icmp_seq=1. time=2.37 ms 64 bytes from 2607:f8b0:4005:805::200e: icmp_seq=2. time=2.46 ms ^C ----2607:f8b0:4005:805::200e PING Statistics---- 3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms) min/avg/max/stddev = 2.37/2.47/2.58/0.10 However ns-ext1, pinger do not work: 436cottrell@ns-ext1:~$ping6 2607:f8b0:4005:805::200e PING 2607:f8b0:4005:805::200e(2607:f8b0:4005:805::200e) 56 data bytes --- 2607:f8b0:4005:805::200e ping statistics --- 12 packets transmitted, 0 received, 100% packet loss, time 10999ms Exit 1 436cottrell@pinger:~$ping6 2607:f8b0:4005:808::200e connect: Network is unreachable Exit 2