...
- Had to get subnet enabled for IPv6 - Mark.
- To find subnet for the host (e.g. pinger) use NetDB (or ping, or ifconfig on actual host) to find IPv4 address
- Use http://network.slac.stanford.edu/subnets to find list of subnets
- Enter first 3 octets of the host (e.g. 134.79.197.) in the filter
- Taylor blocks blocked 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 needed 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 address which is currently configure configured on this host 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
If it does not have an IPv6 address then we have to assign one from the relevant range (e.g. for www3)
Code Block ksa@cdlogin3 $ /afs/slac/g/scs/net/bin/subnet all | grep SERV01-DMZ-WEBSERV 134.79.197.128 SERV01-DMZ-WEBSERV 134.79.197.129 255.255.255.128 Serv01 Web Servers DMZ (vlan 1814) 2620:114:d000:2716:: SERV01-DMZ-WEBSERV 2620:114:d000:2716::1 ffff:ffff:ffff:ffff:: Serv01 Web Servers DMZ (vlan 1814)
To test:
Code Block ksa@www3 $ curl -I -v www3 * About to connect() to www3 port 80 (#0) * Trying 2620:114:d000:2716::8... connected * Connected to www3 (2620:114:d000:2716::8) port 80 (#0) [?]
...
One can use https://network-tools.webwiz.net/ping.htm to check if a target responds to IPv6 pings. As part of this we discovered that the SLAC border was blocking IPv6 pings (see INC0178575). This was fixed.
We started by adding ipv6.google.com(2607:f8b0:4007:802::200e) to NODEDETAILS in the SLACPROD database. After running
/afs/slac/package/pinger/guthrie/node.pl -o > /afs/slac/package/pinger/nodes.cf, we got the following in nodes.cf.
| Code Block |
|---|
"ipv6.google.com" => [
"2607:f8b0:4007:802::200e",
"Google.com",
"COM.GOOGLE.IPV6",
"GooglePlex",
"Mountain View, California",
"",
"",
"37.4220 -122.0841",
"NOT-SET",
"NOT-SET",
"NOT-SET",
"NOT-SET",
"http://www.google.com",
"",
"",
"",
"",
"Testing IPv6 support, add by Cottrell 1/31/2018.",
], |
XML file at Guanhzhou
See here. Currently, it contains random pingable IPv6 addresses as Saqib took it from http://www.ipv6forum.com/ipv6%5fenabled/approval%5flist.php. He proceeded as follows:
...