You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/usr/libexec/cni/danm --version
2023/06/26 11:50:57 DANM binary was built from release: v4.3.0-3-ged6b0c5
2023/06/26 11:50:57 DANM binary was built from commit: ed6b0c57_dirty
First glance, I kinda doubt it would be DANM assigning the IP considering there isn't even a CIDR in the network to assign it from
do you have a default ClusterNetwork in your cluster?
link/ether fe:18:41:0d:dd:42 brd ff:ff:ff:ff:ff:ff
inet6 2001:11:195:105:fc18:41ff:fe0d:dd42/64 scope global mngtmpaddr dynamic
mngtmpaddr
(IPv6 only) make the kernel manage temporary addresses created from this one as template on behalf of
Privacy Extensions (RFC3041). For this to become active, the use_tempaddr sysctl setting has to be set
to a value greater than zero. The given address needs to have a prefix length of 64. This flag allows
to use privacy extensions in a manually configured network, just like if stateless auto-configuration
was active.
this seems to be an autoconfigured address (note that the host part contains the mac address in EUI64 form). What is the use_tempaddr sysctl set to?
Is this a BUG REPORT or FEATURE REQUEST?:
What happened:
Observing ipv6 global mngtmpaddr dynamic address in interface even when "ip6": "none"
Pod annotatation
{ "clusterNetwork": "sriov-x2u-dpdk", "ip6": "none" }
What you expected to happen:
Since accept_ra and autoconf is 0 we dont expect this IP to get assigned to interface
How to reproduce it:
This is intermittent , sometimes global mngtmpaddr dynamic address gets assigned to interface
Anything else we need to know?:
Describe cn output
Environment:
danm -version
):kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: