Looks like binkd has problems parsing some IPv6 addresses correctly:


+ 15 Sep 19:41:40 [5273] call to 2000:1/1@fakenet
15 Sep 19:46:48 [5290] trying fd12:3456::1 [fd12:3456::1]...
? 15 Sep 19:46:48 [5290] connection to 2000:1/1@fakenet failed: Invalid argument

+ 15 Sep 19:41:40 [5273] call to 2000:1/1@fakenet
15 Sep 19:41:22 [5268] trying fd12 via socks 127.0.0.1:1080...
15 Sep 19:41:22 [5268] connected
15 Sep 19:41:22 [5268] connected to socks5 127.0.0.1:1080
+ 15 Sep 19:41:22 [5268] outgoing session with fd12:24554
[...]
? 15 Sep 19:41:24 [5268] recv: Connection reset by peer

---
* Origin: 1995| Invention of the Cookie. The End. (2:280/464.47)

Hello Oli,

On Thursday September 16 2021 09:45, you wrote to All:

Looks like binkd has problems parsing some IPv6 addresses correctly:

+ 15 Sep 19:41:40 [5273] call to 2000:1/1@fakenet
15 Sep 19:46:48 [5290] trying fd12:3456::1 [fd12:3456::1]...
? 15 Sep 19:46:48 [5290] connection to 2000:1/1@fakenet failed:
Invalid argument

Here I have no problem with ULA addresses:

+ 11:15 [3380] call to 2:280/5555@fidonet
11:15 [3380] trying fd51:550:40b9:0:f1d0:2:280:5555
[fd51:550:40b9:0:f1d0:2:280:5555]...
11:15 [3380] connected
+ 11:15 [3380] outgoing session with fd51:550:40b9:0:f1d0:2:280:5555:24554
- 11:15 [3380] OPT CRAM-MD5-fc351e1068288146a98febc2160121ee
+ 11:15 [3380] Remote requests MD mode
- 11:15 [3380] SYS Nieuw Schnoord
- 11:15 [3380] ZYZ Michiel van der Vlist
- 11:15 [3380] LOC Driebergen, NL
- 11:15 [3380] NDL CM,MO,XW,IBN:fido.vlist.eu,RPK,NPK,ENC,NC,PING,TRACE,IPv6

Note: I have the literal address in the config, no DNS incolved. So the problem may be in the DNS server.


Cheers, Michiel

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

Hello Michiel,

Michiel wrote (2021-09-16):

Looks like binkd has problems parsing some IPv6 addresses
correctly:

+ 15 Sep 19:41:40 [5273] call to 2000:1/1@fakenet
15 Sep 19:46:48 [5290] trying fd12:3456::1 [fd12:3456::1]...
? 15 Sep 19:46:48 [5290] connection to 2000:1/1@fakenet failed:
Invalid argument

MvdV> Here I have no problem with ULA addresses:

MvdV> + 11:15 [3380] call to 2:280/5555@fidonet
MvdV> 11:15 [3380] trying fd51:550:40b9:0:f1d0:2:280:5555
MvdV> [fd51:550:40b9:0:f1d0:2:280:5555]...
MvdV> 11:15 [3380] connected
MvdV> + 11:15 [3380] outgoing session with fd51:550:40b9:0:f1d0:2:280:5555:24554

MvdV> Note: I have the literal address in the config, no DNS incolved. So the
MvdV> problem may be in the DNS server.

I also use the literal IPv6 address. I just tried it on another machine with 64-bit Linux and I cannot reproduce the problem there. Interesting. Maybe specific to 32-bit (or armv7 / Raspberry)?

---
* Origin: 1995| Invention of the Cookie. The End. (2:280/464.47)

Hello Oli,

On Thursday September 16 2021 11:02, you wrote to me:

MvdV>> Note: I have the literal address in the config, no DNS
MvdV>> incolved. So the problem may be in the DNS server.

I also use the literal IPv6 address. I just tried it on another
machine with 64-bit Linux and I cannot reproduce the problem there. Interesting. Maybe specific to 32-bit

I use the 32 bit Windows version, so no 32 bit problem as such.

(or armv7 / Raspberry)?

Maybe...


Cheers, Michiel

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

Oli wrote (2021-09-16):

Looks like binkd has problems parsing some IPv6 addresses
correctly:

+ 15 Sep 19:41:40 [5273] call to 2000:1/1@fakenet
15 Sep 19:46:48 [5290] trying fd12:3456::1 [fd12:3456::1]...
? 15 Sep 19:46:48 [5290] connection to 2000:1/1@fakenet failed:
Invalid argument

MvdV>> Here I have no problem with ULA addresses:

MvdV>> Note: I have the literal address in the config, no DNS incolved.
MvdV>> So the problem may be in the DNS server.

I also use the literal IPv6 address. I just tried it on another machine with 64-bit Linux and I cannot reproduce the problem there. Interesting. Maybe specific to 32-bit (or armv7 / Raspberry)?

Correction: the IPv6 over Socks5 problem is the same on the 64-bit machine.

* Origin: (2:280/464.47)

Hello Oli!

On Thu, 16 Sep 2021 at 12:49 +0100, you wrote to All:

I also use the literal IPv6 address. I just tried it on another
machine with 64-bit Linux and I cannot reproduce the problem
there. Interesting. Maybe specific to 32-bit (or armv7 /
Raspberry)?

Correction: the IPv6 over Socks5 problem is the same on the 64-bit machine.

Which probably mean the problem is on Socks5 server side.


... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)

Michiel wrote (2021-09-16):

MvdV> Hello Oli,

MvdV> On Thursday September 16 2021 11:02, you wrote to me:

MvdV>>> Note: I have the literal address in the config, no DNS
MvdV>>> incolved. So the problem may be in the DNS server.

I also use the literal IPv6 address. I just tried it on another
machine with 64-bit Linux and I cannot reproduce the problem there.
Interesting. Maybe specific to 32-bit

MvdV> I use the 32 bit Windows version, so no 32 bit problem as such.

(or armv7 / Raspberry)?

MvdV> Maybe...

The problem with the direct connections has most likely nothing to do with binkd. After a reboot I cannot reproduce it anymore. Maybe user error.

The problem with ipv6 and socks5 persists though. Does anyone use IPv6 addresses with socks5 successfully?

---
* Origin: https://www.vox.com/22654167/war-on-terror (2:280/464.47)

Alexey wrote (2021-09-16):

Hello Oli!

On Thu, 16 Sep 2021 at 12:49 +0100, you wrote to All:

I also use the literal IPv6 address. I just tried it on another
machine with 64-bit Linux and I cannot reproduce the problem
there. Interesting. Maybe specific to 32-bit (or armv7 /
Raspberry)?

Correction: the IPv6 over Socks5 problem is the same on the 64-bit
machine.

Which probably mean the problem is on Socks5 server side.

The socks server only receives the first part of the IPv6 address and the port number (fd12:24554).

This is exactly what binkd tries to do:

16 Sep 16:55:51 [2645] trying fd12 via socks 127.0.0.1:2080...

Looks very much like binkd cannot handle IPv6 addresses for socks5 connections. Socks server works fine with other software and IPv6.

---
* Origin: https://www.vox.com/22654167/war-on-terror (2:280/464.47)

Hello Oli!

On Thu, 16 Sep 2021 at 17:09 +0100, you wrote to me:

This is exactly what binkd tries to do:
16 Sep 16:55:51 [2645] trying fd12 via socks 127.0.0.1:2080...

Indeed, that makes sense.


... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)