Re: IPv6 assistance
On 03/07/18 11:23, Ed Greshko wrote: > And this is running > > /sbin/dhclient -d -q -6 Ah, Hah! After a time that process exited. And this did show up in the journal. Mar 07 11:20:37 f27gq.greshko.com NetworkManager[740]: [1520392837.1581] dhcp6 (enp0s3): state changed unknown -> timeout Mar 07 11:20:37 f27gq.greshko.com NetworkManager[740]: [1520392837.1606] dhcp6 (enp0s3): canceled DHCP transaction, DHCP client pid 1074 Mar 07 11:20:37 f27gq.greshko.com NetworkManager[740]: [1520392837.1606] dhcp6 (enp0s3): state changed timeout -> done So, it would seem that communication between your system and the DHCP server is the source of the problem. (Sorry for the fragmentation. I'm doing a poor job of multitasking this morning) -- If simple questions can be answered with a simple google query then why are there so many of them? signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: IPv6 assistance
On 03/07/18 11:16, Ed Greshko wrote: > On 03/07/18 07:04, Chris Caudle wrote: >> Could be the case that AUTOCONF and DHCPv6 are mutually exclusive now. >> I have a CentOS 7.4 machine which seems to be running correctly with both >> IPV6_AUTOCONF=yes and DHCPV6C=yes, but that distribution has dhclient >> provided by dhclient-4.2.5-58.el7.centos.1 and Fedora 27 is using rhclient >> from dhcp-client-4.3.6-9.fc27. Could be changed behavior between 4.2 and >> 4.3 of dhclient. >> >> Against that hypothesis is that the dhclient did log that it was requesting >> on the second interface, which has the same settings in the ifcfg file. >> I'll try some different settings tonight. I'm pretty sure that the current >> version of the file was hand edited, I have used nmcli and nmtui in the past. >> I just edited the connection with nmtui and it did use only the autoconf >> directive, not the dhcp, so I will see if that worked. It did not just from >> restarting NetworkManager, I will have to try later bringing the interface >> down all the way and restarting. I am connected over that network via ssh >> currently so I can't easily shut it down. >> > FWIW, I manually added DHCPV6C=yes to a config file on a VM. As I mentioned, > my > router can only support one address assignment method at a time and it is > configured > for "stateless". > > With that said, the only message that appears in the journal is... > > Mar 07 11:02:24 f27k.greshko.com NetworkManager[811]: > [1520391744.1479] > dhcp-init: Using DHCP client 'dhclient' > > There is no indication from the status of NetworkManager that /sbin/dhclient > was ever > started and it isn't running. > > So, if your router is configured for "stateful (dhcp)" it is possible it won't > simultaneously support "stateless". Therefore I would try... > > IPV6_AUTOCONF=no > DHCPV6C=yes > Oh, for completeness I went back to my VM and configured my interface with IPV6_AUTOCONF=no DHCPV6C=yes And this is running /sbin/dhclient -d -q -6 But I have no global IPv6 address since there is no dhcpv6 server available. -- If simple questions can be answered with a simple google query then why are there so many of them? signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: IPv6 assistance
On 03/07/18 07:04, Chris Caudle wrote: > Could be the case that AUTOCONF and DHCPv6 are mutually exclusive now. > I have a CentOS 7.4 machine which seems to be running correctly with both > IPV6_AUTOCONF=yes and DHCPV6C=yes, but that distribution has dhclient > provided by dhclient-4.2.5-58.el7.centos.1 and Fedora 27 is using rhclient > from dhcp-client-4.3.6-9.fc27. Could be changed behavior between 4.2 and 4.3 > of dhclient. > > Against that hypothesis is that the dhclient did log that it was requesting > on the second interface, which has the same settings in the ifcfg file. I'll > try some different settings tonight. I'm pretty sure that the current > version of the file was hand edited, I have used nmcli and nmtui in the past. > I just edited the connection with nmtui and it did use only the autoconf > directive, not the dhcp, so I will see if that worked. It did not just from > restarting NetworkManager, I will have to try later bringing the interface > down all the way and restarting. I am connected over that network via ssh > currently so I can't easily shut it down. > FWIW, I manually added DHCPV6C=yes to a config file on a VM. As I mentioned, my router can only support one address assignment method at a time and it is configured for "stateless". With that said, the only message that appears in the journal is... Mar 07 11:02:24 f27k.greshko.com NetworkManager[811]: [1520391744.1479] dhcp-init: Using DHCP client 'dhclient' There is no indication from the status of NetworkManager that /sbin/dhclient was ever started and it isn't running. So, if your router is configured for "stateful (dhcp)" it is possible it won't simultaneously support "stateless". Therefore I would try... IPV6_AUTOCONF=no DHCPV6C=yes -- If simple questions can be answered with a simple google query then why are there so many of them? signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: IPv6 assistance
On 03/07/18 07:04, Chris Caudle wrote: > Could be the case that AUTOCONF and DHCPv6 are mutually exclusive now. > I have a CentOS 7.4 machine which seems to be running correctly with both > IPV6_AUTOCONF=yes and DHCPV6C=yes, but that distribution has dhclient > provided by dhclient-4.2.5-58.el7.centos.1 and Fedora 27 is using rhclient > from dhcp-client-4.3.6-9.fc27. Could be changed behavior between 4.2 and 4.3 > of dhclient. > > Against that hypothesis is that the dhclient did log that it was requesting > on the second interface, which has the same settings in the ifcfg file. I'll > try some different settings tonight. I'm pretty sure that the current > version of the file was hand edited, I have used nmcli and nmtui in the past. > I just edited the connection with nmtui and it did use only the autoconf > directive, not the dhcp, so I will see if that worked. It did not just from > restarting NetworkManager, I will have to try later bringing the interface > down all the way and restarting. I am connected over that network via ssh > currently so I can't easily shut it down. > OK. Just one thing to note. Auto-Configuration, also known as stateless, will only work if the router is configured to supply "router advertisements" FWIW, I do think a network can have both. Just not sure if a client can define both. I would be concerned with inconsistent addresses being assigned. I've just not been able to test it since I only have one router on my system and it can only be configured for "stateless" or "stateful (dhcp)" operation. -- If simple questions can be answered with a simple google query then why are there so many of them? signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: IPv6 assistance
Could be the case that AUTOCONF and DHCPv6 are mutually exclusive now. I have a CentOS 7.4 machine which seems to be running correctly with both IPV6_AUTOCONF=yes and DHCPV6C=yes, but that distribution has dhclient provided by dhclient-4.2.5-58.el7.centos.1 and Fedora 27 is using rhclient from dhcp-client-4.3.6-9.fc27. Could be changed behavior between 4.2 and 4.3 of dhclient. Against that hypothesis is that the dhclient did log that it was requesting on the second interface, which has the same settings in the ifcfg file. I'll try some different settings tonight. I'm pretty sure that the current version of the file was hand edited, I have used nmcli and nmtui in the past. I just edited the connection with nmtui and it did use only the autoconf directive, not the dhcp, so I will see if that worked. It did not just from restarting NetworkManager, I will have to try later bringing the interface down all the way and restarting. I am connected over that network via ssh currently so I can't easily shut it down. thanks, Chris C ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: IPv6 assistance
On 03/07/18 03:50, Chris Caudle wrote: > I am looking for some help getting IPv6 configured properly on a Fedora 27 > system. > I have one system which was installed fresh with Fedora 27, that system is > working properly, it receives both IPv4 and IPv6 addresses assigned by my > router (running latest LEDE release). > I have a second system which receives the expected IPv4 address but does > not receive an IPv6 address. > > I notice that on the working system NetworkManager shows two instances of > dhcp client: Some of questions. What desktop are you using? The NetworkManager GUI displays are a bit different between KDE and GNOME. Are you using the GUI to configure the interfaces or doing it manually? I think the problem is that in your config file you have both > IPV6_AUTOCONF=yes and > DHCPV6C=yes > I don't use DHCP for IPv6 in my network since Android devices can't use it. So, I manually configure IPv6 for systems where I want a "short" IPv6 address and they are "servers". For the other systems I just let them use the IPv6 native auto-discovery do its things. I believe with both of those parameters defined the IPV6_AUTOCONF takes precedence and will prevent the dhcp-client from starting. FWIW, using the GUI on KDE I could not force my config files to have both of those defined with "yes". -- If simple questions can be answered with a simple google query then why are there so many of them? signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
