You're welcome.? I didn't do much, but looks like it was a minor configuration error that confused tlb.? Commenting out the offending line did the trick.

For everyone else following, don't use a hostname for SF_Bind2IP.? This should only ever set to an IP address, and even then, only if you know you need this setting.? Most people don't need to use it.? Most common usage scenarios for Bind2IP or SF_Bind2IP are when you're running multiple instances of tlb or tbd on the same physical host that has multiple IP addresses, or where you want to be certain what address tlb reports to the servers or the remote peers it connects to.? And it seems using a hostname confuses tlb internally.? It binds to 0.0.0.0 (all IPs), but doesn't seem to properly pass traffic on the Speak Freely (IRLP) ports.? I consider this a bug in tlb, because the configuration parser should either reject this as an invalid IP(v4) or perform a DNS lookup and obtain the actual IP.? The first option (rejecting anything that's not an IPv4 address) is the safest.

In this instance, connections could happen on a couple of IP addresses, so you actually don't want to set SF_Bind2IP here, hence the reason I commented it out, rather than setting it to a valid IP address.

On 13/7/24 2:58 am, Enrique XE1E via groups.io wrote:

-- 
73 de Tony VK3JED/VK3IRL