Subj : Maybe Kees will know
To   : Michiel van der Vlist
From : Joe Delahaye
Date : Mon Sep 05 2016 16:16:34

  Re: Maybe Kees will know
  By: Michiel van der Vlist to Joe Delahaye on Mon Sep 05 2016 21:48:35

 MV> I can't rule it out, but I very much doubt this is IPv6 related. A delay
 MV> can occur when a cleint thinks it has IPv6 andtries to make a connetction
 MV> tio an IPv6 capable server and the connection fails because the client
 MV> does not actually have an IPv6 connection.

 MV> But that would cause a timeout, not a password error. I suspect this is a
 MV> configuration error on Bob's system, but without more infromation, we can
 MV> only guess.

Looking back, I have a downlink, running NIX that suddenly developed that
problem of Bad Password when I send him anything.  I can connect with Bob no
problem.  He has the problem sending to me with the Ddutch.nl domain.  


 MV> Kees' suggestion of forcing the mailer to make an IPv4 connection by
 MV> adding -4 is a good suggestion to rule out an IPv6 related problem.

I have sent him a netmail suggesting that.

BTW, here is a log of the session with the bad password.

+ 04 Sep 17:25:03 [3] call to 1:249/300@fidonet
  04 Sep 17:25:03 [3] trying 69.165.170.121...
  04 Sep 17:25:03 [3] connected
+ 04 Sep 17:25:03 [3] session with lionsden.ddutch.nl (69.165.170.121)
- 04 Sep 17:25:04 [3] OPT CRAM-MD5-0071de0d40545b7ce6e8170fceeddaee
+ 04 Sep 17:25:04 [3] Remote requests MD mode
- 04 Sep 17:25:04 [3] SYS The Lion's Den
- 04 Sep 17:25:04 [3] ZYZ Joe Delahaye
- 04 Sep 17:25:04 [3] LOC Trenton, Ont. Cdn
- 04 Sep 17:25:04 [3] NDL 115200,TCP,BINKP
- 04 Sep 17:25:04 [3] TIME Sun,  4 Sep 2016 11:25:04 -0400
- 04 Sep 17:25:04 [3] VER binkd/1.1a-94/Win32 binkp/1.1
+ 04 Sep 17:25:04 [3] addr: 1:249/303@fidonet
+ 04 Sep 17:25:04 [3] addr: 1:249/300@fidonet
+ 04 Sep 17:25:04 [3] addr: 1:249/0@fidonet
+ 04 Sep 17:25:04 [3] addr: 1:12/0@fidonet
? 04 Sep 17:25:04 [3] rerror: Bad password
+ 04 Sep 17:25:04 [3] done (to 1:249/300@fidonet, failed, S/R: 0/0 (0/0 bytes))
  04 Sep 17:25:04 [3] session closed, quitting...

 And I think I just found the problem.  The above is trying to connect to my
/300 hub node, while the one that worked was calling the /303 node

+ 04 Sep 17:50:32 [3] call to 1:249/303@fidonet
  04 Sep 17:50:32 [3] trying 69.165.170.121...
  04 Sep 17:50:32 [3] connected
+ 04 Sep 17:50:32 [3] session with lionsden.darktech.org (69.165.170.121)
--- SBBSecho 3.00-Win32
 * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

.