Closed colemar closed 1 year ago
Hello, Everyone wants IPv6. Unless there are edge circumstances, all installations should have IPv6 enabled. Disabling IPv6 at the kernel level will stop all IPv6-related networking if you choose to deactivate it; In order to future-proof installations, it is structured in this manner; if a user decides they eventually want IPV6 but don't want it now, they just need to enable it on the kernel level.
Note: It is not advised to manually edit the WireGuard configuration.
If ipv6 is enabled at the kernel level but disabled (temporarily) at systemd level or by some other means, I guess there will be no ipv6 addresses in wireguard wg0 config file (if installed while ipv6 is disabled). There are still many providers (even server providers like Oneprovider) that do not support ipv6 in the local network, hence sometimes there is no point in keeping ipv6 enabled except to complicate network administration.
Whether we like it or not, we will all soon be utilizing IPv6 since we ran out of IPv4 capacity.
Additionally, I honestly have no idea why IPv6 is so despised; the developer adoption rate is atrocious. If we can impose Ipv6 at the code level without the user having to worry about it in the background, it would be the best choice for the future of the web.
Ubuntu 22.04
Wireguard was already installed (apt install wireguard) with just one peer before wireguard-manager.sh first run. This is /etc/wireguard/wg0.conf
IPv6 is disabled at the kernel startup time. Since line 1219 seems to deal with ipv6 addresses, I guess the culprit is that there are no ipv6 addresses in /etc/wireguard/wg0.conf.