See INC0164829
pinger.slac.stanford.edu
A quick test to see if the host has full IPv6 capability is to run traceroute6
| Code Block |
|---|
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 1 |
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
Code Block 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.
Code Block 447cottrell@rhel6-64f:~$host www3 www3.slac.stanford.edu has address 134.79.197.214
...