Subj : Connection Tests
To   : Rob Swindell
From : Michiel van der Vlist
Date : Wed Apr 05 2023 11:52 am

Hello Rob,

On Tuesday April 04 2023 15:18, you wrote to me:

 >> netsh int ipv6 add address Internet 2600:6c88:8c40:5b:f1do:1:103:705

 RS> That worked (after changing 'o' to '0' of course).

Of course. ;-)

And your binkp server answers on that address:

+ 09:37 [3496] call to 1:103/705@fidonet
  09:37 [3496] trying 2600:6c88:8c40:5b:f1d0:1:103:705
               [2600:6c88:8c40:5b:f1d0:1:103:705]...
  09:37 [3496] connected
+ 09:37 [3496] outgoing session with 2600:6c88:8c40:5b:f1d0:1:103:705:24554
- 09:37 [3496] OPT CRAM-MD5-357f8433fbc4ded531732d8e1c7c8842
+ 09:37 [3496] Remote requests MD mode
- 09:37 [3496] SYS Vertrauen
- 09:37 [3496] ZYZ Rob Swindell
- 09:37 [3496] LOC Riverside County, California
- 09:37 [3496] NDL 115200,TCP,BINKP
- 09:37 [3496] TIME Wed Apr 05 2023 00:37:54 GMT-0700 (Pacific Daylight Time)
- 09:37 [3496] VER BinkIT/2.41,JSBinkP/4,sbbs3.20a/Win32 binkp/1.1
+ 09:37 [3496] addr: 1:103/705@fidonet

So all you have to do to earn your 'f' in the list is update the DNS for the mew IPv6 address.

Binkd has the possibility to specify the address to use for outgoing calls. It overrides the OS preference.

  bindaddr 2600:6c88:8c40:5b:f1do:1:103:705

I don't know about BinkIT.

 >> For incoming you should create a pinhole for port 24554 and maybe
 >> port 23.

 RS> With the DMZ set, no pin-holes needed.

I am still a bit puzzled about your setup. Do you have /any/ barrier between the big bad InterNet and your Fido Machine?


Cheers, Michiel

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

.