-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dictd and IPv6 support #5
Comments
Fixed in dictd-1.13.0. Thanks a lot for pointing out! |
Hmm, rpmlint still complains:
|
Oops. You are right. There are still some gethostbyname :-/ |
Is it possible, to listen on all addresses, both IPv4 and IPv6? If yes, how? If not, this would be a good enhancement. |
I have patches against dictd-1.13.1 that do just that, if anyone is interested... |
|
Not necessarily. Depends on the OS, and system settings. You need to set the IPV6_V6ONLY flag to "off" on the socket, hence why I needed the patch. Also, some systems don't support IPv4 on Ipv6 sockets at all (OpenBSD) Incidentally, when IPV6_V6ONLY is set, you (obviously) can't bind the socket to listen to a specific address. |
These are my current patches against 1.31.1: |
@Jamie-Landeg-Jones , I had started a solution too but using the posix |
It would be nice to have the ability to have listeners on independent sockets (that way you can specify which address to listen on, instead of INADDR_ANY), but I took the lazy way out. Prior to that, I was running 2 separate dictd instances, but that got a bit heavy when running 252 databases :-) (https://dictionary.catflap.org/?Form=/4) |
dictd
as it stands now (9a2f53e) works only with IPv4 (for example, it still usesgethostbyname
function). There were efforts in Red Hat to make all their programs working with IPv6, including this bug for dictd. That included this patch against 1.9.15 by @dkopecek, but the patch has never been finished and applied, AFAIK. It meanwhile bitrotten, so it cannot be directly applied to the current checkout.Attaching the patch here, so it is preserved for posterity.
The text was updated successfully, but these errors were encountered: