I guess I spoke too soon. :) Now I am getting the following error when I fire binkd up:

servmgr socket(): Address family not supported by protocol

I did some google searching on that... found a bunch of posts by other fido sysops but they are all in crylic and I could not seem to get an understandable translation of them. :)

---
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net

Re: binkd issue, pt 2
By: Dumas Walker to All on Mon Jul 16 2018 07:10 pm

I guess I spoke too soon. :) Now I am getting the following error when I fire binkd up:

servmgr socket(): Address family not supported by protocol

I did some google searching on that... found a bunch of posts by other fido sysops but they are all in crylic and I could not seem to get an understandable translation of them. :)

Are you trying to use IPv6?

digital man

Synchronet "Real Fact" #54:
The Synchronet source code consists of over 500,000 lines of C and C++.
Norco, CA WX: 69.6øF, 84.0% humidity, 4 mph E wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: binkd issue, pt 2
By: Dumas Walker to All on Mon Jul 16 2018 07:10 pm

I guess I spoke too soon. :) Now I am getting the following error when I fire binkd up:

servmgr socket(): Address family not supported by protocol

I did some google searching on that... found a bunch of posts by other fido sysops but they are all in crylic and I could not seem to get an understandable translation of them. :)

Are you trying to use IPv6?

No, but I think it must be set to do so somewhere on the Pi and I just cannot figure out where, like something set by default in a raspbian install. I was able to refine my search and determined that I probably need to be using AddressFamily = inet instead of "any," but I cannot find the system config file where that setting is located. My eth0 setting in /etc/network/services is set up for "inet" (ipv4), so that is not the culprit.

---
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net

Re: Re: binkd issue, pt 2
By: Dumas Walker to Digital Man on Tue Jul 17 2018 07:33 pm

Re: binkd issue, pt 2
By: Dumas Walker to All on Mon Jul 16 2018 07:10 pm

I guess I spoke too soon. :) Now I am getting the following error when I fire binkd up:

servmgr socket(): Address family not supported by protocol

I did some google searching on that... found a bunch of posts by other fido sysops but they are all in crylic and I could not seem to get an understandable translation of them. :)

Are you trying to use IPv6?

No, but I think it must be set to do so somewhere on the Pi and I just cannot figure out where, like something set by default in a raspbian install. I was able to refine my search and determined that I probably need to be using AddressFamily = inet instead of "any," but I cannot find the system config file where that setting is located. My eth0 setting in /etc/network/services is set up for "inet" (ipv4), so that is not the culprit.

Or, the way the address is formatted in your binkd.cfg file, it thinks you're trying to bind to an ipv6 address/interface?

digital man

This Is Spinal Tap quote #4:
David St. Hubbins: He died in a bizarre gardening accident...
Norco, CA WX: 71.9øF, 77.0% humidity, 5 mph E wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

No, but I think it must be set to do so somewhere on the Pi and I just cannot figure out where, like something set by default in a raspbian install. I was able to refine my search and determined that I probably nee
to be using AddressFamily = inet instead of "any," but I cannot find the system config file where that setting is located. My eth0 setting in /etc/network/services is set up for "inet" (ipv4), so that is not the culprit.

Or, the way the address is formatted in your binkd.cfg file, it thinks you're trying to bind to an ipv6 address/interface?

The only addresses I have defined in the binkd.cfg file are the FTN-style net/node numbers. I did a scan for ":" and did not find any which were not somewhere they should be.

---
þ SLMR 2.1a þ Gimme three chili dogs and a malt.
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net

Re: Re: binkd issue, pt 2
By: Dumas Walker to DIGITAL MAN on Wed Jul 18 2018 04:33 pm

No, but I think it must be set to do so somewhere on the Pi and I just cannot figure out where, like something set by default in a raspbian install. I was able to refine my search and determined that I probably nee
to be using AddressFamily = inet instead of "any," but I cannot find the system config file where that setting is located. My eth0 setting in /etc/network/services is set up for "inet" (ipv4), so that is not the culprit.

Or, the way the address is formatted in your binkd.cfg file, it thinks you're trying to bind to an ipv6 address/interface?

The only addresses I have defined in the binkd.cfg file are the FTN-style net/node numbers. I did a scan for ":" and did not find any which were not somewhere they should be.

The default "listen" address for binkd is "*", maybe try setting that value in your binkd.cfg to the IPv4 address of your network interface instead.

digital man

Synchronet/BBS Terminology Definition #38:
NUL = ASCII 0
Norco, CA WX: 88.6øF, 49.0% humidity, 11 mph NE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

The default "listen" address for binkd is "*", maybe try setting that value in
your binkd.cfg to the IPv4 address of your network interface instead.

Well, the version I am using (debian stable) does not support "listen," but
it does support tcp setting, "bindaddr." I have compiling a newer version
on my to-do list, but uncommenting the bindaddr setting for this older version seems to have done the trick!

Thanks for pointing me in the right direction!

---
þ SLMR 2.1a þ "Hired goons????" - Homer
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net