Subj : Your IPv6 connection
To   : Allen Prunty
From : Michiel van der Vlist
Date : Wed Aug 17 2016 21:21:48

Hello Allen,

On Wednesday August 17 2016 14:42, you wrote to me:

 MvdV>> addresses on your Fido machine? Connection-specific

 AP> IPv6 Address. . . . . . . . . . . : 2602:306:83c1:a710::48
 AP> IPv6 Address. . . . . . . . . . . :
 AP> 2602:306:83c1:a710:5cb0:9a56:dd26:5d18
 AP> Temporary IPv6 Address. . . . . . :
 AP> 2602:306:83c1:a710:9d54:ff3c:6d09:1fcf
 AP> Link-local IPv6 Address . . . . . : fe80::5cb0:9a56:dd26:5d18%12
 AP> IPv4 Address. . . . . . . . . . .: 192.168.1.91
 AP> Subnet Mask . . . . . . . . . . . :
 AP> 255.255.255.0
 AP> Default Gateway . . . . . . . . . : fe80::9662:69ff:fee2:7d20%12

Ah, this is what I suspected!  The AAAA record in ipv6.livewirebbs.com is a temporary address. You should NOT use that for incoming calls.

I see thatthe first IPv6 address, the one ending on ::48 is probably a manually entered fixed address. If so I would use that.

The third one, the one ending on 5d18 looks like a DHCP6 address. Nothe that the last 64 bits are the same as that of the links local address, the one starting with fe80:

Can you confirm that the address ending on ::48 is a manually added fixed address?

It does work to make a binkp connect:


+ 21:14 [576] call to 1:2320/100@fidonet
  21:14 [576] trying 2602:306:83c1:a710::48 [2602:306:83c1:a710::48]...
  21:14 [576] connected
+ 21:14 [576] outgoing session with 2602:306:83c1:a710::48:24554
- 21:14 [576] SYS LiveWire BBS
- 21:14 [576] ZYZ Allen Prunty
- 21:14 [576] LOC Parts Unknown, KY, USA
- 21:14 [576] NDL 115200,TCP,BINKP
- 21:14 [576] TIME Wed, 17 Aug 2016 15:14:06 -0400
- 21:14 [576] VER binkd/1.1a-94/Win32 binkp/1.1


Cheers, Michiel

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

.