When creating a new network in netmaker and assigning an ipv6 prefix, the auto-generated node IP is not assigned to the wireguard interface but somehow the ipv4 address is assigned twice. Once as /24 and once as /32.
It works correctly on regular netcliend instances but somehow in the container it does not. The eth0 above shows an fe80 so I don't think it's an os issue. This is running with the platform kubernetes env flag.
I can manually assign a v6 address to the eth0 interface but not to any wg interfaces
bash-5.1# ip -6 addr add 2001:470:28:5b2::1/64 dev eth0 <-- works fine
bash-5.1# ip -6 addr add 2001:470:28:5b2::1/64 dev nm-ByteMe
RTNETLINK answers: Invalid argument
Contact Details
Lorenzo95 in discord
What happened?
When creating a new network in netmaker and assigning an ipv6 prefix, the auto-generated node IP is not assigned to the wireguard interface but somehow the ipv4 address is assigned twice. Once as /24 and once as /32.
It works correctly on regular netcliend instances but somehow in the container it does not. The eth0 above shows an fe80 so I don't think it's an os issue. This is running with the platform kubernetes env flag.
I can manually assign a v6 address to the eth0 interface but not to any wg interfaces
Version
v0.13.1
What OS are you using?
Linux
Relevant log output
Contributing guidelines