I posted a question about getting Synchronet to listen on multiple interfaces a while ago. At the time, the advice given was to do the following:

; IP address of network interface to bind to (defaults to ANY/ALL interfaces):
Interface=202.12.89.162,2001:44b8:4176:f100::6,10.69.181.6

This worked for a while, but in recent weeks, I am finding that Synchronet is only listening on the first listed interface (202.12.89.162). I haven't changed anything to my knowledge, and the above snippet is taken directly from my sbbs.ini file.

Anyone able to shed any light on what's going on here?


... The wages of sin are unreported.
--- MultiMail/Win32 v0.49
þ Synchronet þ Freeway BBS, Bendigo Australia. freeway.apana.org.au

Re: Binding to multiple IP addresses (again).
By: Vk3jed to All on Wed Feb 14 2018 08:42 am

I posted a question about getting Synchronet to listen on multiple interfaces a while ago. At the time, the advice given was to do the following:

; IP address of network interface to bind to (defaults to ANY/ALL interfaces):
Interface=202.12.89.162,2001:44b8:4176:f100::6,10.69.181.6

This worked for a while, but in recent weeks, I am finding that Synchronet is only listening on the first listed interface (202.12.89.162). I haven't changed anything to my knowledge, and the above snippet is taken directly from my sbbs.ini file.

Anyone able to shed any light on what's going on here?

What changed from when it worked to when it didn't? Did you perform a version/build update of SBBS in that time? What is telling you that Synchronet is only listening on the first interface? If you enable debug log level, it should spew details about each interface being bound. Do you not see all the listed interfaces being bound? Any errors?

digital man

Synchronet "Real Fact" #2:
Synchronet version 2 for DOS and OS/2 was released to the public domain in 1997.
Norco, CA WX: 52.6øF, 63.0% humidity, 0 mph SW wind, 0.01 inches rain/24hrs

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

Hello,

On Tue, 13 Feb 2018 23:04:28 -0800, Digital Man -> Vk3jed wrote:

; Anyone able to shed any light on what's going on here?

What changed from when it worked to when it didn't? Did you perform a version/build update of SBBS in that time? What is telling you that Synchronet is only listening on the first interface? If you enable
debug log level, it should spew details about each interface being
bound. Do you not see all the listed interfaces being bound?
Any errors?

Not sure if this is totally related or not, but every so often I seem be having
an issue similar with this after a reboot. Now seems to be one of those times. Could possibly be something to do with systemd, but..

Even though I use "After=network.target" in my systemd startup script, sbbs seems to try to initialize before dhcpcd is completely up. It tends to bind to IPv6 ports just fine, but fails on all IPv4 ports. Using "sudo systemctl restart sbbs" right after works every time.

So I'm not sure why sbbs is trying to load before or during the network.target inititialization process, and it seems to fix itself once in awhile, but it has
been a bit since it has actually worked by itself without me restarting manually after intitial startup on reboot. I may have to try looking into adding some sort of 30 or 60 second delay before starting sbbs to give network.target time to finish, but it shouldn't be necessary, and may not have anything to do with Synchronet itself. Just figured I'd throw it out there in case anyone else was having (or had) an issue and might have a proper fix.

Regards,
Nick

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (723:1/1)
þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)

Digital Man wrote to Vk3jed <=-

What changed from when it worked to when it didn't? Did you perform a version/build update of SBBS in that time? What is telling you that

No changes, still running the same build that I originally got it working on.

Synchronet is only listening on the first interface? If you enable
debug log level, it should spew details about each interface being
bound. Do you not see all the listed interfaces being bound? Any
errors?

netstat reports listening only on the first IP. I haven't yet tried changing the order of IPs in the ini file.

Will hae to look into the debug log. It's annoying, because:

1. NAT timeouts get in the way.

2. I have an issue with my tunnel router, which blocks me from quickly logging into the system (a lot of mail comes in via IPv6 these days, and binkd is not affected).

Will have to see what the debug log says.


... Sushi: known to the rest of the world as 'Bait'
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Nicholas Boel wrote to Digital Man <=-

Not sure if this is totally related or not, but every so often I seem
be having an issue similar with this after a reboot. Now seems to be
one of those times. Could possibly be something to do with systemd,
but..

Looks like a separate issue to me. I'm not running systemd or DHCP.


... Real Programmers do List Processing in FORTRAN.
--- MultiMail/Win32 v0.49
þ Synchronet þ Freeway BBS, Bendigo Australia. freeway.apana.org.au