Subj : New in this
To   : Ward Dossche
From : Kees van Eeten
Date : Fri Dec 07 2018 16:40:02

Hello Ward!

 WD> I asked around how to do this but I'm getting conflicting answers or
 WD> answers to questions not asked.

 WD> The binkd-version I'm running identifies itself as ...

 WD>   07 Dec 14:37:39 [5004] BEGIN standalone, binkd/1.1a-94/Win32 BINKD.CFG
 WD> -cs

 WD> So I think that's a goodone. The name of the executable is

 WD>   binkd-static-perl-zlib-bzlib2

 WD> Am I still good?

 As you are aware I have a point system running Dbridge for some time now.

 BINKDWIN.EXE -vv    tells me:

Binkd 1.1a-95 (Dec 10 2016 21:44:31/Win32)
Compilation flags: mingw32, zlib, perldl, https, ntlm, amiga_4d_outbound, bwlim, ipv6.
Facilities: fts5004 ipv6

 So it is slightly newer than yours, but the important part is that
 Facillities mentions ipv6

 Including ipv6 support is a compile time option, so it may be there or not.
 The patch has been available since November 2011.

 The BINKDWIN.EXE I use with the DBRIDGE was distributes with DBRIDGE.

 In the configurations of DBridge I use Binkd in "Linux mode" whatever that
 may mean, but my impression is that it rund standalone and communicates
 with Dbridge using flag files.

 I use the config that dbridge generates and I hope that Nich does not object
 to me publishing it here.

# D'Bridge 3.99 BINKD configuration file output (DBRIDGE.BNK)
# Exported on 23:21:34 20181205
#
# Copyright (c) by Nick J. Andre, Ltd.
#
# If this file needs to be submitted for review or discussion due to
# to a problem, bug report or other issue, please remember to BLANK OUT
# any passwords from the "node" configuration lines. DO NOT post the
# contents of this file publically until you blank out the passwords.
#
# ------------------- [ START OF YOUR CONFIGURATION ] -------------------
#
# Domains:
#
domain fidonet data\\fidonet 2
#
# Addresses:
#
address 2:280/5003.10@fidonet
#
# General variables:
#
sysname "Somewhere, somehow."
location "Heerhugowaard, NL"
sysop "Kees van Eeten"
nodeinfo 9600,TCP,BINKP
oblksize 4096
timeout 60
connect-timeout 0
call-delay 60
rescan-delay 15
maxservers 4
:
maxclients 1
log binkd.log
loglevel 4
conlog 4
inbound F:\\DB\\INBOUND\\
inbound-nonsecure F:\\DB\\INBOUND\\
minfree 2048
minfree-nonsecure 2048
kill-dup-partial-files
kill-old-partial-files 86400
kill-old-bsy 43200
try 3
hold 60
flag dbridge.ufm *.*
#
# Systems:
#
node 2:280/5003@fidonet fido.ddutch.nl SECRET -
root-domain fidonet
prescan
#
# BinkD additional options:
#
domain fidonet.org alias-for fidonet
#
# -------------------- [ END OF YOUR CONFIGURATION ] --------------------

This is about what is really needed next to the defaults.

The above runs on a laptop with Windows XP installed.

After I consulted Michiel what was needed to make IPv6 work in n WIn-XP,
this setup has had all it connections with 2:280/5003 using IPv6.

So again as all are telling you if binkd -vv tells you that ipv6 is a
included facillity, then Ipv6 is supported.

The remainder of your problems is then either your OS, but I beleive the
version you use supports IPv6 out of the box, or your firewall.

If your point system on Android has problems conneting when IPv6 is active,
please ask the developer if IPv6 is supported.

I did not send this message from the Dbridge point system, as cut and past
seems not to work in a dosbox on WIN-xp, but that is plobably my own
ignorance.

Kees

--- GoldED+/LNX 1.1.5
 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

.