|
The issue with BPQ seems to be not the 'defaulting to IPv4' but that outgoing telnet to IPv6 fails to connect at all both in the latest stable and beta versions and
toggle quoted message
Show quoted text
this while IPv4 and IPv6 are both enabled for the telnet port, see below. -- I tested outgoing telnet from the BPQ node to a tcp port what can only handle IPv6 as I have a 6tunnel for IPv6 to Xnet, what is a IPv4 only program. 6tunnel converts here a IPv6 input at tcp port 24 to IPv4 at tcp port 23 what connects to Xnet. BPQ po BPQTOK:VE3TOK-12} Ports ? 1 Kiss Link to Kernel ? 2 Kiss Link to (X)net ? 3 Telnet Server ? 4 AX/IP/UDP attach 3 BPQTOK:VE3TOK-12} Ok c linux.ve3mch.ampr.org 24 *** Failed to Connect linux.ve3mch.ampr.org resolves both to an IPv4 and IPV6 address. I tested this from the latest stable BPQ version as well as from the latest beta version and both are failing with outgoing telnet over IPv6. Both IPv4 and IPv6 are enabled for the telnet port in BPQ with, ? IPV6=1 ? IPV4=1 From the linux shell to proof that IPv6 really works at port 24 # telnet linux.ve3mch.ampr.org 24 Trying 2001:470:1d:138::1... Connected to linux.ve3mch.ampr.org. Escape character is '^]'. (X)NET 1.39 @ VE3MCH-8 on LINUX: PSE enter Your callsign to login. Login: With IPv4 from the shell to Xnet at port 24 telnet -4 linux.ve3mch.ampr.org 24 Trying 44.135.85.151... telnet: Unable to connect to remote host: Connection refused What is as expected. Regards, Boudewijn VE3TOK On 5/17/25 15:36, Boudewijn (Bob) Tenty VE3TOK wrote:
Oops, the last line should be read as 'and when not possible fall back to IPv4 -' --
There is nothing permanent except change Heraclitus |
