Subj : New candidate member
To   : Markus Reschke
From : Michiel van der Vlist
Date : Sun Oct 16 2016 13:41:51

Hello Markus,

On Sunday October 16 2016 12:24, you wrote to me:

 MvdV>> There are also 2001:470:70:bf5::1 and 2001:470:70:bf5::2. Note
 MvdV>> the '70' instead of the '71' in the third position. Those two
 MvdV>> addresses are the end points of his he.net tunnel. They both
 MvdV>> ping from here as well now. Since his tunnel does not end on
 MvdV>> his router, but on his fidonet system, his binkp server may
 MvdV>> also answer on the address of his tunnel end point.

 MR> In this case the best option is to use 2001:470:70:bf5::1, since it's
 MR> the WAN address of the fido system.

I disagree.

1) "WAN address" is IPv4 NAT speak. In IPv6 one has link local addresses and globally unique routable addresses. 2001:470:70:bf5::1 is a globally routable address.

2) 2001:470:70:bf5::1 is the he.net tunnel endpoint. His binkp server does not answer on that address.

 MR> $ telnet -6 2001:470:70:bf5::2 24554
 MR> Trying 2001:470:70:bf5::2...
 MR> Connected to 2001:470:70:bf5::2.

3) 2001:470:70:bf5::2 is the tunnel end point on his end. His binkp server answers on that address because it so happens that the tunnel end point and the binkp server run on the same host. But this is co‹ncidence. He could move the tunnel end point to another device on his LAN and then it would no longer work. 2001:470:71:bf5::1 is the address of the interface that connects the system that runs his binkp server to the 2001:470:71:bf5::/64 subnet. IMNSHO that should be the address to connect to his binkp server. That keeps working if he moves the tunnel end point to his router or another host on the same subnet.


Cheers, Michiel

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

.