Closed hi0t closed 3 weeks ago
This should already be solved on main
- please give it a look. localhost
even on Windows refers to 127.0.0.1, for what it's worth - ie, the loopback interface; unsure why Windows is allowing the connection from the IPv6 link local address for your NIC, though it might well be some transparent address rewriting in the networking stack making that work.
Yes, you are absolutely right. Rebuilt from the main branch, now the utility listens to both protocols. Thank you for such prompt support!
This does sound like a manifestation of pre #1776 behaviour on windows, where it would get the IPv6 address from getaddrinfo but on windows the IPV6_ONLY socket option is set by default so the socket would only accept v6 connections.
It would probably make sense to fix the usage info and BMDA readme to say it binds to the any address not specifically localhost too.
The documentation correction sounds like a reasonable suggestion 👍🏼
I built a bmda app v1.10.2 for Windows. Launched the app:
Now I'm trying to connect via telnet:
But on IPv6 it works:
Typically, network applications listen to both protocols. I see no reason to limit them to only the IPv6 protocol.
Also in the help it is indicated that only the localhost is listened to:
But in fact, all addresses are listened to. Probably worth fixing the help?