Skip to content
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

Open
vanrein opened this issue Jun 17, 2020 · 6 comments
Open

Feature Request: IPv6 connections #46

vanrein opened this issue Jun 17, 2020 · 6 comments
Labels
enhancement New feature or request

Comments

@vanrein
Copy link

vanrein commented Jun 17, 2020

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 to conserver?

@vanrein
Copy link
Author

vanrein commented Jun 17, 2020

To help out, in my own programs I usually drop socket.h and socket.c among the program files. It tends to hide network details really well. You are more than welcome to include those in your program.

@bstansell
Copy link
Owner

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 configure with the --with-ipv6 option. Not sure if anyone has exercised the code in a pure ipv6 environment yet. Would be interesting to know if things are all good or not.

@bstansell bstansell added the enhancement New feature or request label Oct 13, 2020
@owendelong
Copy link

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
Console clients running on:

  • local to conserver (via SSH shell access)

  • Remote Mac Mini M1 (using home-brew package customized to compile --with-ipv6 and --with-openssl)

  • Local iMac Intel (using home-brew package similarly customized)

@bzfbd
Copy link

bzfbd commented Jul 15, 2021

Is there documentation on how to deal with IPv6 addresses?
I cannot find anything after a quick skip online and the local man pages.
Would especially be interesting for access/trusted to be able to give subnets access w/o password.

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.

@owendelong
Copy link

That FreeBSD Jail issue might be more likely happening under the hood in the BSD kernel and not something conserver is doing at all.

@bzfbd
Copy link

bzfbd commented May 5, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants