Subj : Re: Connect...??
To   : Bill McGarrity
From : Wilfred van Velzen
Date : Sat Jan 14 2017 12:58 pm

Hi,

On 2017-01-13 17:53:57, Bill McGarrity wrote to Wilfred van Velzen:
  about: "Re: Connect...??":

 WV>> That explains it. I'm using hub.tequilamockingbirdonline.net, as
 WV>> requested in  Bill's original message. And that resolves to a
 WV>> different IPv6 address. When I  use the ftn.* address I get a connect
 WV>> on IPv6...

 BM> No, you were doing it correctly.  hub.tequilamocokingbirdonline.net on
 BM> 24555 should be working now.  When you tried the 24554 port, it was
 BM> probably the ftn address.  When I added the IPv6 forwarding, I had to turn
 BM> on the IPv6 firewall and then give a pkt exception for it.  Once I did 
that
 BM> I saw that I also had to give the main server an exception as well.
 BM> According to ipv6scanner.com all ports on both INA are open and working.

So there are 2 ports, 1 IPv4 address, and 2 IPv6 addresses, which makes 6 
combinations:

IPv4 24554 works
IPv4 24555 works
ftn IPv6 24554 works
ftn IPv6 24555 does not work
hub IPv6 24554 does not work
hub IPv6 24555 works

Is this how it should be? ;)


Bye, Wilfred.


--- FMail-W32 1.73.12.64-B20170112
 * Origin: Native IPv6 connectable node (2:280/464)

.