TIP: Click on subject to list as thread! ANSI
echo: binkd
to: ANDREI DZEDOLIK
from: MICHIEL VAN DER VLIST
date: 2018-04-28 22:51:00
subject: Feature request: soft IPv

Hello Andrei,

On Saturday April 28 2018 20:27, you wrote to me:

 MV>> There are a few poblems. First I had to remove the commands
 MV>> related to compression from my config.

This I had to disable:

#zlevel 9                                                                     °
#zminsize 1024                                                                °
#zallow *.PKT                                                                 °
#zdeny *.SU? *.MO? *.TU? *.WE? *.TH? *.FR? *.SA?                              °
#zdeny *.ZIP *.RAR *.ARJ *.HA *.LHA *.7Z *.GZ *.TGZ *.BZ2 *.XZ
*.[ALRZ][0-9][0-9]
#zallow *                                                                     °
#                                                                             °

 MV>> There is an error at startup:

 AD> Aha, this is intersting can you share the node line which didn't work?

listen [2001:1c02:1100:d700:f1d0:2:280:5555]:24555
listen [2001:1c02:1100:d700:f1d0:2:280:5555]:24554
bindaddr [2001:1c02:1100:d700:f1d0:2:280:5555]
listen 0.0.0.0

node 2:5020/9696 -6 skovpen.org -

 AD> Which version you were running with this config before mine?

D:\FIDO\BINKD>binkd -vv
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

D:\FIDO\BINKD>

 AD> Can you share your config? To be honest I didn't touch nor test server
 AD> pieces of code, onlu client

Aha. As I mentioned in my other message, it seems to work in client mode.

 AD> and I did my tests with 'binkd -c -P'.
 AD> Perhaps there is some work to do in a server side too, you config (or
 AD> at least pieces of it where you 'bind' binkd) might be helpfull.

See above.

 MV>> And then when I try to call 2:5020/9696 (T-6to4) it always calls
 MV>> out on IPv6, no matter if I specify -64, -46 or just -4.

 AD> Let me try this one ...

What I have not been able to test yet, is what happens if the attempt to
connect via IPv6 fails. It should fall back to IPv4, (or the other way around)
but I have not been able to test that.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.