Subj : BinkD Callback Service
To   : Michiel van der Vlist
From : Tommi Koivula
Date : Sat Oct 03 2015 20:14:36

03 Oct 15 14:28, you wrote to me:

 TK>> If you send a file 'test' to 2:221/6, the system tries to call
 TK>> you back. :)

 MV> It does not work from my point 1. This may have to do with the fact
 MV> that PE are enabled on my laptop running Win 7 pro?

My brand new callbacksystem reads the ip address where the call is coming and tries to call back. Your .1 call was coming from ipv6 address which couldn't backresolv for dns name. That caused the callback to fail:

  03 Oct 15:24:33 [1360] creating a poll for 2:280/5555.1@fidonet (`d' flavour)
  03 Oct 15:24:33 [1360] clientmgr started
+ 03 Oct 15:24:33 [4068] call to 2:280/5555.1@fidonet
? 03 Oct 15:24:33 [4068] 470:1f15:1117:2d20:ebc3:3d83:dd77: incorrect port
(getaddrinfo: Servname not supported for ai_socktype)
? 03 Oct 15:24:33 [4068] 2001:470:1f15:1117:2d20:ebc3:3d83:dd77: 1: error
parsing host list
  03 Oct 15:24:33 [1360] rc(4068)=0
  03 Oct 15:24:33 [1360] the queue is empty, quitting...

Maybe Binkd needs []'s around the IPv6 address. Let's see.

 MV> O wait. When I tried it on my main system, I saw that the reply did
 MV> not come from *::f1d0:2:221:6 but from a PE address. So there is no
 MV> channel opened in my firewall voor that.

That's because Win2003 always sets (and defaults outgoing) slaac address even if I have set manually 2001:470:1f15:cb0:f1d0:2:221:6.

Privacy extensions are disabled.

'Tommi

---
 * Origin: ====================================== (2:221/1.1)

.