Subj : Maybe Kees will know To : Joe Delahaye From : Kees van Eeten Date : Mon Sep 05 2016 22:27:12 Hello Joe! 05 Sep 16 16:16, you wrote to Michiel van der Vlist: JD> BTW, here is a log of the session with the bad password. JD> + 04 Sep 17:25:03 [3] call to 1:249/300@fidonet JD> 04 Sep 17:25:03 [3] trying 69.165.170.121... JD> 04 Sep 17:25:03 [3] connected JD> + 04 Sep 17:25:03 [3] session with lionsden.ddutch.nl (69.165.170.121) JD> - 04 Sep 17:25:04 [3] OPT CRAM-MD5-0071de0d40545b7ce6e8170fceeddaee JD> + 04 Sep 17:25:04 [3] Remote requests MD mode JD> - 04 Sep 17:25:04 [3] SYS The Lion's Den JD> - 04 Sep 17:25:04 [3] ZYZ Joe Delahaye JD> - 04 Sep 17:25:04 [3] LOC Trenton, Ont. Cdn JD> - 04 Sep 17:25:04 [3] NDL 115200,TCP,BINKP JD> - 04 Sep 17:25:04 [3] TIME Sun, 4 Sep 2016 11:25:04 -0400 JD> - 04 Sep 17:25:04 [3] VER binkd/1.1a-94/Win32 binkp/1.1 JD> + 04 Sep 17:25:04 [3] addr: 1:249/303@fidonet JD> + 04 Sep 17:25:04 [3] addr: 1:249/300@fidonet JD> + 04 Sep 17:25:04 [3] addr: 1:249/0@fidonet JD> + 04 Sep 17:25:04 [3] addr: 1:12/0@fidonet JD> ? 04 Sep 17:25:04 [3] rerror: Bad password JD> + 04 Sep 17:25:04 [3] done (to 1:249/300@fidonet, failed, S/R: 0/0 (0/0 JD> bytes)) 04 Sep 17:25:04 [3] session closed, quitting... JD> And I think I just found the problem. The above is trying to connect to JD> my /300 hub node, while the one that worked was calling the /303 node JD> + 04 Sep 17:50:32 [3] call to 1:249/303@fidonet JD> 04 Sep 17:50:32 [3] trying 69.165.170.121... JD> 04 Sep 17:50:32 [3] connected JD> + 04 Sep 17:50:32 [3] session with lionsden.darktech.org (69.165.170.121) JD> --- SBBSecho 3.00-Win32 JD> * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303) I agree with Michiel, that this is not an IPv6 problem, so off topic for this echo. The above problem can be avoided by setting the password for all aliases. You for all aliases of Bob's node and Bob for all aliases of your node. EOT Kees --- GoldED+/LNX 1.1.5 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4) .