-
Notifications
You must be signed in to change notification settings - Fork 38
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
Feature Request: IPv6 connections #46
Comments
Been a little distracted, so haven't gotten to these requests, but as far as this one is concerned, conserver does have IPv6 support (possibly complete). All you'd need to do is run |
I'll try to take a stab at testing this out. It won't be a pure IPv6 environment per se, but I can make sure the the conserver host itself doesn't have an IPv4 address and all access uses DNS to resolve the IPv6 address. That should test things out fairly well... Environment: Conserver using Ubuntu distributed package on Raspberry PI 4
|
Is there documentation on how to deal with IPv6 addresses? Turned out on classic FreeBSD jails the code does not cope well if listening to ::1 which automatically gets translated to the jail's (primary) IPv6 address. When trying to connect then one connects to the address and not to ::1. I'd assume there is some strcmp() involved or something. I might debug this as time moves on. |
That FreeBSD Jail issue might be more likely happening under the hood in the BSD kernel and not something conserver is doing at all. |
I think I do understand what FreeBSD is doing with IPv6 support in jails given I wrote the code ;-) I'll look into conserver some more as I really might need IPv6 subnet mask support for trust. |
I'm considering
conserver
for an internal IPv6-only network that is only backward compatible with IPv4 on the outside. This is a delightful relaxation in things like address assignment and firewalling. Is it perhaps time to add IPv6 support toconserver
?The text was updated successfully, but these errors were encountered: