Jump to content
hurricanehrndz

Requesting IPV6 in unRAID kernel.

116 posts in this topic Last Reply

Recommended Posts

I making the following request, because without it apps the require IPV6 will cause headaches. A good example is x11vnc, if using x11vnc within an unRAID environment that doesn't have ipv6 built into the kernel, x11vnc causes a buffer overrun.

Share this post


Link to post

in trying to make a container for a video conference server i also hit upon an issue with ipv6 and echo this request.

Share this post


Link to post

I will run this past Tom and Eric.  If it's simple enough and doesn't impose risk, I can't see why we wouldn't do it, but this is beyond my depth to judge.

Share this post


Link to post

If you add IPv6 (a good idea) specifically mark it as beta or you will soon enough get a load of support and GUI alteration requests.

 

Let the power users hammer it for a couple of years

Share this post


Link to post

+1 to this. Basic support should (in theory) be as simple as enabling IPV6 in the kernel config.

Share this post


Link to post

I would love to see IPv6 support added.  Don't get me wrong, I love NATing as much as the next guy, but I am really looking forward to allocating an IPv6 address to every cell in my body (and my wife's body, and my kids, and...).  :o

Share this post


Link to post

I've tested on a custom kernel, and found that indeed adding support is as simple as setting CONFIG_IPV6=y in the kernel config.

Share this post


Link to post

I've tested on a custom kernel, and found that indeed adding support is as simple as setting CONFIG_IPV6=y in the kernel config.

What testing did you perform to ensure stability?  Have you tested every combination of network configuration as well as with each file sharing protocol, VMs, Docker, etc?  Also, I think you'd also need to craft a webgui front end control for this as well.  Maybe you could take a swing at creating a plugin for this?

 

Point is that it's a low priority item because there is a lot more to it than just enabling the kernel flag and the benefits are pretty minimal right now.

Share this post


Link to post

I've tested on a custom kernel, and found that indeed adding support is as simple as setting CONFIG_IPV6=y in the kernel config.

What testing did you perform to ensure stability?  Have you tested every combination of network configuration as well as with each file sharing protocol, VMs, Docker, etc?  Also, I think you'd also need to craft a webgui front end control for this as well.  Maybe you could take a swing at creating a plugin for this?

 

Point is that it's a low priority item because there is a lot more to it than just enabling the kernel flag and the benefits are pretty minimal right now.

 

Sorry; didn't mean to imply that was all that needed to be done for full support. It would've been more accurate to have said "…adding basic support is as simple as…".

 

However, enabling the kernel build flag and setting the sysctl `net.ipv6.conf.all.disable_ipv6=1`, or providing it as a kernel module that's not loaded by default, would allow users to test a variety of scenarios without causing potential backwards-compatibility problems in the interim.

Share this post


Link to post

 

 

I've tested on a custom kernel, and found that indeed adding support is as simple as setting CONFIG_IPV6=y in the kernel config.

What testing did you perform to ensure stability?  Have you tested every combination of network configuration as well as with each file sharing protocol, VMs, Docker, etc?  Also, I think you'd also need to craft a webgui front end control for this as well.  Maybe you could take a swing at creating a plugin for this?

 

Point is that it's a low priority item because there is a lot more to it than just enabling the kernel flag and the benefits are pretty minimal right now.

 

Sorry; didn't mean to imply that was all that needed to be done for full support. It would've been more accurate to have said "…adding basic support is as simple as…".

 

However, enabling the kernel build flag and setting the sysctl `net.ipv6.conf.all.disable_ipv6=1`, or providing it as a kernel module that's not loaded by default, would allow users to test a variety of scenarios without causing potential backwards-compatibility problems in the interim.

 

Sorry if I came off as a bit cross about it.  Not what was intended. More of inquisitory in asking what testing has been done as well as if you'd feel up to proposing a plugin for its incorporation.

 

My concerns with enabling it in the kernel is how it could cause additional issues with initial setup or basic things like network bonding.  The reality is we have no experience in implementing or supporting ipv6, so we would be treading into uncharted territory. I've mentioned before that this is something that we will have to do eventually, but I just can't see the short term benefit of prioritizing this.  If we knew for 100% certain that enabling it in the kernel (and nothing else) couldn't / wouldn't cause issues, maybe we could do that, but I don't know that and I'd be worried about what folks may expose themselves to in toying around with it without a proper implementation.  For example, could this inadvertently open up network security risks?  What about routing tables?  Again, all uncharted territory, but if there are any ipv6 experts out there, I'm prepared to be schooled ;-)

Share this post


Link to post

Just coming in with my $0.02 here.  IPv6 adoption is slow, but speeding up.  You could probably do much worse than compiling in IPv6 in the kernel and let your more advanced users give it a go.

 

In the next year or two I'd like to be dual stack in my internal network. I suspect that by 2020 adoption will be high enough that anything that doesn't support it well will be seen as being caught flat footed.

Share this post


Link to post

It is especially annoying for people like me if unRaid has no IPv6 connectivity.

My ISP is running DSLite, i have no real IPv4 Adress anymore but only a Carrier Grade NAT. What i have on the other hand is a real IPv6 Adress.

 

Life could be really easy for me but because unRaid has no IPv6 i need to run another 6Tunnel at home to translate from IPv6 to IPv4 for my unRaid if i connnect from outside.

 

I would really appreciate and IPv6 branch, or a config setting or whatever to get IPv6 running on unRaid.

 

I understand the fear of the Limetech team, but IPv6 is coming definately.

Share this post


Link to post

My Provider is running DS-Lite too.. that is annoying as fuck..

 

as a workaround: pass additional NIC through to KVM and run a IPv6 capable ovpn server ?

Share this post


Link to post

10% of google users now access their services by IPv6. Those are no longer trivial numbers.

Share this post


Link to post

If i recall it right Sparklyballs already has a IPv6 Version of the unRaid Kernel compiled by itself. Thin i read about it in the Daapd Container discussion.

Maybe he could tell if he encountered any problems so far etc.

 

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.