...
Created nodes-ipv6.pl to add the PingER IPv6 MA 2001:da8:270:2018:f816:3eff:fef3:bd3. See here for addition.
Copied getdata.pl to get datagetdata-ipv6.pl and modified to use the nodes-ipv6.cf file and write to the /nfs/slac/g/net/pinger/pingerdata/ipv6/data/ directory when running getdata-ipv6.pl 2001:da8:270:2018:f816:3eff:fef3:bd3 2017-12-19 1. Also replaced IPv4 address checks with sub chck_ip{} to test for both IPv4 and IPv6 addresses.
...
This does not accept IPv6 Addresses, see INC0176849 and INC0176966. APEX doesn't like colon(:) in primary key column values. Primary key value is passed in the URL as a parameter and APEX parameters are separated by colons (:), which is causing the issue. Venkat provided a workaround. We will test this on the Oracle SLACDEV2 (SLACPROD is the production version) test database. The connection to the database is defined in: /afs/slac/package/pinger/oracleArchive/netratDb.pm
In that program the following lines contain slacprod/SLACPROD
- ian@rhel6-64e $ grep -i slacprod netratDb.pm
- # to all the scripts that store in the SLACPROD database for the user
- $ENV{'TWO_TASK'} = 'SLACPROD';
- $dbh = DBI->connect('dbi:Oracle:dbname=SLACPROD;host=slacprod;SID=SLACPROD', $usr, $pwd,
I made a copy of the script and substituted slacdev2/SLACDEV2 for slacprod/SLACPROD and also made a of /afs/slac/package/pinger/guthrie/node.pl to call the new script.
The password is kept in a protected file. The password on SLACDEV2 was changed to match the one on SLACPROD
XML file at Guanhzhou
See here. Currently, it contains random pingable IPv6 addresses as I have taken it from http://www.ipv6forum.com/ipv6%5fenabled/approval%5flist.php
...