https://forum.linode.com/viewtopic.php?f=19&t=14570&p=72785 I can not figure out what I need to do. Apparently according to linode support, the VM is trying to grab an IPv6 address with some privacy stuff enabled by default causing it to not grab the IPv6 address that is assigned to me. Nothing I have tried seems to work, and it seems that Linode support are far more familiar with Ubuntu than CentOS. I know CentOS follows Red Hat so I'm not suggesting this is CentOS's fault, but stuff like this really is why I am a much bigger fan of KISS with simple key=value configuration files that don't seem to exist anymore with Linux networking in the Red Hat world. Making things more complex to benefit "Cloud" servers it the worst thing Red Hat ever did. Sorry for the tone, I'm quite frustrated and as an epileptic who doesn't drive, driving down to the SF Bay Area for RHCE classes that won't even be applicable in a few years when they change stuff again isn't really an option. Been using Red Hat since MKLinux DR3 (based on Red Hat 5.1) and been through the training courses before and everything changes. Anyone know what might be going on? And how to get dhclient to grab the "right" IPv6 address, the same one this VM grabbed no problem for well over a year?
In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581b5e at domblogger.net>, Alice Wonder <alice at domblogger.net> wrote:> https://forum.linode.com/viewtopic.php?f=19&t=14570&p=72785 > > I can not figure out what I need to do. > > Apparently according to linode support, the VM is trying to grab an IPv6 > address with some privacy stuff enabled by default causing it to not > grab the IPv6 address that is assigned to me.Does the accepted answer at the following link give you any useful hints? http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6 Cheers Tony -- Tony Mountifield Work: tony at softins.co.uk - http://www.softins.co.uk Play: tony at mountifield.org - http://tony.mountifield.org
On 02/16/2017 12:54 AM, Tony Mountifield wrote:> In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581b5e at domblogger.net>, > Alice Wonder <alice at domblogger.net> wrote: >> https://forum.linode.com/viewtopic.php?f=19&t=14570&p=72785 >> >> I can not figure out what I need to do. >> >> Apparently according to linode support, the VM is trying to grab an IPv6 >> address with some privacy stuff enabled by default causing it to not >> grab the IPv6 address that is assigned to me. > > Does the accepted answer at the following link give you any useful hints? > > http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-when-using-ipv6 > > Cheers > Tony >Not really - I tried net.ipv6.conf.all.use_tempaddr = 0 and it still fails to grab the proper IPv6 -=- Just in case, I did ask Linode support to verify that my hardware address is what it is suppose to be. Still waiting to hear on that.
On Thu, 2017-02-16 at 00:37 -0800, Alice Wonder wrote:> https://forum.linode.com/viewtopic.php?f=19&t=14570&p=72785 > > I can not figure out what I need to do. > > Apparently according to linode support, the VM is trying to grab an IPv6 > address with some privacy stuff enabled by default causing it to not > grab the IPv6 address that is assigned to me.I'm no IPv6 expert (as in I know nothing), but look at the options that dhclient is using when it's running - there are various v6 specific options that would affect what's happening. 'man dhclient' is useful here.> > > I know CentOS follows Red Hat so I'm not suggesting this is CentOS's > fault, but stuff like this really is why I am a much bigger fan of KISS > with simple key=value configuration files that don't seem to exist > anymore with Linux networking in the Red Hat world.Yes they do. Everything concerned with networking is held in flat files - they may be XML like files or some other structured approach, but they are there. What you are probably confusing it with is the fact that most of the config files are written by GUI applications or maintained by CLI commands rather than editing them by hand. That's all down to NetworkManager - love it or hate it, but the clue to what it does is in the name, it manages your network. If you don't want something to manage your network, don't use it.> > Anyone know what might be going on? And how to get dhclient to grab the > "right" IPv6 address, the same one this VM grabbed no problem for well > over a year? >As I said, you need to look at dhclient configuration and command line options. If you have NetworkManager running then it will be controlling what dhclient does so manual editing the files will not work. Use nmcli to see what's happening and modify the configuration. P.
--On Thursday, February 16, 2017 10:12 AM +0000 Pete Biggs <pete at biggs.org.uk> wrote:> As I said, you need to look at dhclient configuration and command line > options. If you have NetworkManager running then it will be > controlling what dhclient does so manual editing the files will not > work. Use nmcli to see what's happening and modify the configuration.It's not so much that editing files won't work, but that in many cases editing the files you're used to won't work. They're now generated from new flat files, and you have to dig around to figure out where the new configuration is hidden. It's a learning curve we all hate to climb, of course. Fortunately we have the source code for when the documentation is inadequate! We see the same thing with the new firewalld. iptables didn't go away. It's just hidden behind firewalld configuration, which automatically writes iptables rules. I liken it to going from assembly language to a higher level language to describe my programming problems. And the new systems usually provide back doors that let you drop down to the more detailed implementation layer if absolutely needed. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus