Hello There,

The response for '1:282/1031 bbs.ouijabrd.net' using IPv6 is:

PING bbs.ouijabrd.net(2602:41:670c:a600:d1d2:c23d:4b1c:940c) 56 data bytes
64 bytes from 2602:41:670c:a600:d1d2:c23d:4b1c:940c: icmp_seq=1 ttl=55 time=65.1 ms
64 bytes from 2602:41:670c:a600:d1d2:c23d:4b1c:940c: icmp_seq=2 ttl=55 time=65.3 ms
64 bytes from 2602:41:670c:a600:d1d2:c23d:4b1c:940c: icmp_seq=3 ttl=55 time=64.9 ms
64 bytes from 2602:41:670c:a600:d1d2:c23d:4b1c:940c: icmp_seq=4 ttl=55 time=65.4 ms
64 bytes from 2602:41:670c:a600:d1d2:c23d:4b1c:940c: icmp_seq=5 ttl=55 time=65.4 ms

-+- bbs.ouijabrd.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms rtt min/avg/max/mdev = 64.987/65.283/65.472/0.181 ms

And the response for '1:14/5 ftn.region14.org' using IPv6 is:

PING ftn.region14.org(2602:41:670c:a600:5f4a:49a9:8216:d121) 56 data bytes
64 bytes from 2602:41:670c:a600:5f4a:49a9:8216:d121: icmp_seq=1 ttl=55 time=66.5 ms
64 bytes from 2602:41:670c:a600:5f4a:49a9:8216:d121: icmp_seq=2 ttl=55 time=65.7 ms
64 bytes from 2602:41:670c:a600:5f4a:49a9:8216:d121: icmp_seq=3 ttl=55 time=65.5 ms
64 bytes from 2602:41:670c:a600:5f4a:49a9:8216:d121: icmp_seq=4 ttl=55 time=65.6 ms
64 bytes from 2602:41:670c:a600:5f4a:49a9:8216:d121: icmp_seq=5 ttl=55 time=64.8 ms

-+- ftn.region14.org ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms rtt min/avg/max/mdev = 64.879/65.670/66.529/0.525 ms

Jeff


--- BBBS/Li6 v4.10 Toy-4
* Origin: Fidoneet: The Ouija Board - Anoka, MN -bbs.ouijabrd.net (1:282/1031)

Hello Jeff,

On Monday April 29 2019 05:32, you wrote to All:

The response for '1:282/1031 bbs.ouijabrd.net' using IPv6 is:

PING bbs.ouijabrd.net(2602:41:670c:a600:d1d2:c23d:4b1c:940c) 56 data
bytes 64 bytes from 2602:41:670c:a600:d1d2:c23d:4b1c:940c: icmp_seq=1 ttl=55 time=65.1 ms 64 bytes from

The fact that it pings does not necesarily imply that the node is IPv6 reachable. But in this case it does. I do not know why I could not connect yesterday, but now I can.

I have updated the list. Thanx for the feedback.



Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello Michiel.

The fact that it pings does not necesarily imply that the node is IPv6 reachable. But in this case it does. I do not know why I could not connect yesterday, but now I can.

I have updated the list. Thanx for the feedback.

The fault may be mine. The v6 IP's that I have are derived from the individual static v4 IP's that I currently have. My ISP *suggests* that since the v6 IP are derived from static IP's they shouldn't change. My experience has taught me
that that isn't the case. As I have had to update the AAAA records manually several times.

I am working on a bash script that will detect an v6 IP change and send that updated IP to my DNS provider.

For a time my ISP did offer the purchase/lease of a block of static v6 IP's. But they look to have changed that to derived IP's now.

Jeff

--- BBBS/Li6 v4.10 Toy-4
* Origin: Fidoneet: The Ouija Board - Anoka, MN -bbs.ouijabrd.net (1:282/1031)