-
Notifications
You must be signed in to change notification settings - Fork 533
Abort connect when IP fails to bind #2793
Comments
It seems like net_resolve fails if hostname is already a raw IP address. Any suggestion on how to go around about this? I can only think of modifying net_resolve so it returns "hostname" if it's already an IP address, or creating a function that tests if a "hostname" is already an IP address and call it before calling net_resolve in all parts of hexchat's code that may need it. In this new patch I changed XP_TE_UKNHOST's message so the "hostname" is also included.
|
Apparently my code was just broken and Now I made it convert code to int. And bind is actually failing in this case.
|
This last patch adds cause of error to the error message. I received "Address family not supported by protocol" for specifying an IPv6 and "Invalid argument" for specifying an IPv4.
|
Hexchat probably needs to abort when it fails to bind to configured bind hostname otherwise it will use a network that it isn't supposed to use.
I just created a patch for it but I'm not getting the expected error message. I'm getting "Unknown host. Maybe you misspelled it?" instead. This happens both when the IP address to bind to is available or not, and I'm not sure where I made a mistake.
The text was updated successfully, but these errors were encountered: