conserver icon indicating copy to clipboard operation
conserver copied to clipboard

Feature Request: IPv6 connections

Open vanrein opened this issue 4 years ago • 6 comments

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 avatar Jun 17 '20 17:06 vanrein

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.

vanrein avatar Jun 17 '20 17:06 vanrein

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 avatar Jul 04 '20 00:07 bstansell

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)

owendelong avatar Apr 06 '21 19:04 owendelong

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.

bzfbd avatar Jul 15 '21 19:07 bzfbd

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

owendelong avatar Jul 16 '21 20:07 owendelong

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.

bzfbd avatar May 05 '22 19:05 bzfbd