Subj : getaddrinfo failed: Servname not supported for ai_socktype (-8)
To : Bj�rn Wiberg
From : Conny Enstr�m
Date : Sun Jan 30 2022 06:23 pm
Den 2022-01-30 kl. 15:55, skrev 2201/137:
BW> Hello Conny!
BW> On 30 Jan 2022, Conny Enstr÷m said the following...
CE>> I try to set up binkd and when I specify the port to the host node
BW> I get
CE>> this error:
CE>> getaddrinfo failed: Servname not supported for ai_socktype (-8)
CE>> The line for the node looks like this:
CE>> node 2:203/0 eljaco.se:24555 secretpasswd
BW> Could this possible be the same as:
BW>
https://github.com/pgul/binkd/issues/27
BW> I'm using binkd 1.1a-111 on Debian now, and in that version things work
BW> as expected (whereas earlier versions did not).
BW> I'm not sure exactly which version of binkd that fixed this, though.
BW> Best regards
BW> Björn
BW> --- Mystic BBS v1.12 A48 2022/01/28 (Linux/64)
BW> * Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)
I use Binkd 1.1a-99 (Oct 18 2019 19:27:01/Linux), installed from Ubuntu repo. And it seems in your link this is the exact version with this problem, I will see if i can find a up tp date version.
The ufw is disabled completely (Ubuntu Fire Wall)
But as I read on in the your link it says something about:
netstat -anp | grep SYN
tcp 0 1 192.168.1.5:42058 219.89.83.33:* SYN_SENT 8760/binkd: call to
Is this something created when the connection is made or something resistant somewhere?
i can not see this when I use the command: sudo netstat -anp | grep SYN
Conny
--- Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
* Origin:
news://eljaco.se:4119 (2:203/2)