$ ping 2001:470:d:123::50
PING 2001:470:d:123::50(2001:470:d:123::50) 56 data bytes
64 bytes from 2001:470:d:123::50: icmp_seq=1 ttl=42 time=321 ms
64 bytes from 2001:470:d:123::50: icmp_seq=2 ttl=42 time=322 ms
64 bytes from 2001:470:d:123::50: icmp_seq=3 ttl=42 time=317 ms

$ ncat 2001:470:d:123::50 24556
Ncat: TIMEOUT.

$ ncat 2001:470:d:123::50 24554
Ncat: TIMEOUT.

---
* Origin: . (21:3/102)

On 18 Apr 2021 at 05:18p, Oli pondered and said...

$ ping 2001:470:d:123::50
PING 2001:470:d:123::50(2001:470:d:123::50) 56 data bytes
64 bytes from 2001:470:d:123::50: icmp_seq=1 ttl=42 time=321 ms
64 bytes from 2001:470:d:123::50: icmp_seq=2 ttl=42 time=322 ms
64 bytes from 2001:470:d:123::50: icmp_seq=3 ttl=42 time=317 ms

$ ncat 2001:470:d:123::50 24556
Ncat: TIMEOUT.

$ ncat 2001:470:d:123::50 24554

thanks, I am moving systems between different computers. Once everything is shifted off the old box to the new one this should start to work again.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Avon wrote (2021-04-19):

thanks, I am moving systems between different computers. Once everything
is shifted off the old box to the new one this should start to work again.

Not really a problem for me, I'm not polling mails from Net 1. It was a good test case though. I'm experimenting with an IPv6-only VPS and had to learn the hard way, that many services don't offer IPv6 connectivity (i.e. docker.io and many other container repos, which is kind of weird). Found a workaround to connect to IPv4 with NAT64/DNS64, but this doesn't work, if the domain does return an AAAA record to an unreachable server. Next step is to setup 464XLAT, which is IPv4 to IPv6 to IPv4 NAT, so my server can connect to 21:1/100's IPv4 address.

If everyone would just stop using IPv4, everything would be much easier. Dual-stack sucks. But who could have known that 4 billion IP addresses are not enough for a global network? ;)

---
* Origin: . (21:3/102)