I ran into a quirk with relayd and how it binds to IP addresses and I want to understand more why this is.
Given a sample configuration: listen on 1.2.3.4 port 80 Where 1.2.3.4 does NOT exist as a valid IP for any network adapter on the system, relayd will start up and not complain of being unable to bind to the IP. Even with debugging flags relayd -dv it would not report any errors to stdout, just startup silently waiting for new connections (which would never come). This was a head scratcher for a while as I inadvertently made a typo in the IP. Is this by design? Normally I expect an error thrown if a service cannot bind to an IP, maybe I am missing something here? Regards Lloyd
