IPv6 control
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
shroudBNC |
In Progress
|
Medium
|
Gunnar Beutner |
Bug Description
IPv6 in its current state deployment is rather unstable, most places it is rolled out, its rolled out dual stack so that both IPv4 and IPv6 are available side by side.
With the removal of the IPv6 toggle in the user settings, it is no longer possible for the admin/user to decide which of these services to use, this needs fixed.
IPv6 and IPv4 should not be able to failover to each other, users should be bound to whichever vhost they have set.
ADDITIONAL INFORMATION:
For an IRC server for example 'tripwire.
My server runs with a full /64 range and 3 IPv4 addresses, on sbnc 1.2 I had 3 clients running on IPv4, for stability with another 15 clients connected to the same server on IPv6.
tags: | added: core |
As a workaround I would suggest binding the client to an IPv4 or IPv6 vhost.