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. :)
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?
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.
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 neeOr, the way the address is formatted in your binkd.cfg file, it thinks you're trying to bind to an ipv6 address/interface?
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.
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.
neeNo, 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
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 default "listen" address for binkd is "*", maybe try setting that valuein
your binkd.cfg to the IPv4 address of your network interface instead.
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 228:04:15 |
| Calls: | 2,088 |
| Calls today: | 2 |
| Files: | 11,140 |
| Messages: | 948,500 |