IS IT GOOD TO DISABLE IPV6 ON MAC MAC

Your assertion that IPv6 is 'secure and a huge improvement over IPv4 in all aspects' is 100% subjective. Its cases like those that have brought me to the 'let's remove it entirely from the kernel' decision - if the kernel doesn't know what it is, doesn't know what to do with it, then it can drop it on the floor and it isn't an issue. Imagine what's to come when sites running IPv6 start leaking their mess onto the internet (due to a lack of understanding of a massively complex new protocol with some very, very distinct and significant differences from IPv4). It happens all the time with IPv4 - a protocol that is well known and, for the most part, well managed. Link-local (and any other 'restricted' address, such as IPv4 private address space addresses 10.0.0.0/8, 192.168.0.0/16, etc.) can be leaked by misconfigured routers. The thought of a 'more flat' address space (versus a hierarchical address space provided through NAT) is, based on my experience, dumb. Auto-configuration seems like a Charlie Foxtrot of epic proportions. Instead, what I read that inspired fear came from the wikipedia article. and arstechnica and (insert-your-online-armchair-expert-publication-here) threads on IPv6 for that very reason (FUD). In fact, I have intentionally shied away from the /. I'm hoping for someone to say, 'hey, idiot, add this to nf or set this in rc.conf, nf or some other one-liner.' If that's not possible and there's really no easy way to do it, then I will write a kernel module to kill as much of it as is possible, though I highly doubt it'll come to that. If this requires a custom kernel, then so be it - I'm sure there's a way to undefine INET6 and leave it all out of the kernel. (I'd also very much appreciate not seeing two inet6 addrs for lo0 - ::1 and some link-local junk that it adds.) (For clarification, yes, even after appending the aforementioned lines in rc.conf loopback still comes up with a pair of inet6 addresses, my tun0 address adds one (link local) and there are about a dozen or so routes in my routing table which I would have posted had I not immediately gone through and manually deleted them - along with the inet6 entries for all interfaces - after I booted.)

I can delete the privacy address or set it as deprecated but it re-appears whenever I netplan apply or reboot.Short of that, I would at least appreciate it if, after booting, I can do a netstat -nr and not see a handful of IPv6 routes. I'm still getting a temporary IPv6 address: $ ip -6 addr # 2 - prefer privacy addresses and use them over the normal addresses. # generated IPv6 address, which increases privacy. Privacy extensions allow using a randomly

IS IT GOOD TO DISABLE IPV6 ON MAC MAC

# IPv6 typically uses a device's MAC address when choosing an IPv6 address I have sysctl configured to not use IPv6 privacy addressing in /etc/sysctl.d/nf: # IPv6 Privacy Extensions (RFC 4941) I've configured Netplan with a static IPv6 address (example address shown - I'm not really using that) # This file describes the network interfaces available on your systemĪddresses: This means that when I try to connect to other things, I appear to come from the wrong IPv6 address. Some of the things I need to access are only reachable via IPv6 and expect me to connect from a specific IPv6 address so my box has a static IPv6 address configured.įor some reason, I can't seem to prevent Ubuntu from generating and preferring privacy IPv6 addresses. I have 18.04 installed and I'm using it as jump box to reach other things.

Is it good to disable ipv6 on mac