I ran into this exact issue last night -
When a computer is connected via IPv4 but the IPv4 a repo host connects to is not available, yum then tries the IPv6 address and will fail with a confusing message telling you it failed to connect to the IPv6 address.
I don't know if there is a way for yum to figure out whether the current network connection to the Internet is IPv4 or IPv6.
But if there is a way, it might make a usability improvement. A lot of people have no idea what IPv6 is and would be confused.
I was confused myself at first, wondering if DHCP pulled in IPv6 from the router.
On Mon, Dec 28, 2015 at 5:24 PM, Alice Wonder alice@domblogger.net wrote:
I ran into this exact issue last night -
When a computer is connected via IPv4 but the IPv4 a repo host connects to is not available, yum then tries the IPv6 address and will fail with a confusing message telling you it failed to connect to the IPv6 address.
I don't know if there is a way for yum to figure out whether the current network connection to the Internet is IPv4 or IPv6.
But if there is a way, it might make a usability improvement. A lot of people have no idea what IPv6 is and would be confused.
I was confused myself at first, wondering if DHCP pulled in IPv6 from the router.
If your DNS answers IPv6, it will have prefence over IPv4. You can set ip_resolve=4 in your yum.conf
On 12/28/2015 02:10 PM, Marcelo Roccasalva wrote:
On Mon, Dec 28, 2015 at 5:24 PM, Alice Wonder alice@domblogger.net wrote:
I ran into this exact issue last night -
When a computer is connected via IPv4 but the IPv4 a repo host connects to is not available, yum then tries the IPv6 address and will fail with a confusing message telling you it failed to connect to the IPv6 address.
I don't know if there is a way for yum to figure out whether the current network connection to the Internet is IPv4 or IPv6.
But if there is a way, it might make a usability improvement. A lot of people have no idea what IPv6 is and would be confused.
I was confused myself at first, wondering if DHCP pulled in IPv6 from the router.
If your DNS answers IPv6, it will have prefence over IPv4. You can set ip_resolve=4 in your yum.conf
The issue is the yum server was down, so IPv4 didn't work.
Once that server was back up (third party repo) it of course worked no issue.
The issue is the error message, while a technically correct one, is one that is not very user friendly and can be confusing to people who are not dual-stack.
It could be improved.
On 12/28/15 17:16, Alice Wonder wrote:
On 12/28/2015 02:10 PM, Marcelo Roccasalva wrote:
On Mon, Dec 28, 2015 at 5:24 PM, Alice Wonder alice@domblogger.net wrote:
I ran into this exact issue last night -
When a computer is connected via IPv4 but the IPv4 a repo host connects to is not available, yum then tries the IPv6 address and will fail with a confusing message telling you it failed to connect to the IPv6 address.
I don't know if there is a way for yum to figure out whether the current network connection to the Internet is IPv4 or IPv6.
But if there is a way, it might make a usability improvement. A lot of people have no idea what IPv6 is and would be confused.
I was confused myself at first, wondering if DHCP pulled in IPv6 from the router.
If your DNS answers IPv6, it will have prefence over IPv4. You can set ip_resolve=4 in your yum.conf
The issue is the yum server was down, so IPv4 didn't work.
Once that server was back up (third party repo) it of course worked no issue.
The issue is the error message, while a technically correct one, is one that is not very user friendly and can be confusing to people who are not dual-stack.
It could be improved.
The place to complain about this is the Fedora list since what CentOS has comes from them by way of RHEL. They, Fedora, are not apt to pay you any mind because they have already abandoned yum and are going with a new package manager named dnf soon to be appearing in a system near you.
On Mon, 2015-12-28 at 19:23 -0500, Mark LaPierre wrote:
The place to complain about this is the Fedora list since what CentOS has comes from them by way of RHEL. They, Fedora, are not apt to pay you any mind because they have already abandoned yum and are going with a new package manager named dnf soon to be appearing in a system near you.
DNF is a stupid name. The Feds could have called it yum2 - K.I.S.S.
On 12/28/15 22:38, Always Learning wrote:
On Mon, 2015-12-28 at 19:23 -0500, Mark LaPierre wrote:
The place to complain about this is the Fedora list since what CentOS has comes from them by way of RHEL. They, Fedora, are not apt to pay you any mind because they have already abandoned yum and are going with a new package manager named dnf soon to be appearing in a system near you.
DNF is a stupid name. The Feds could have called it yum2 - K.I.S.S.
Well thank God, and Linus, for symbolic links.
On Wed, 2015-12-30 at 20:50 -0500, Mark LaPierre wrote:
On 12/28/15 22:38, Always Learning wrote:
On Mon, 2015-12-28 at 19:23 -0500, Mark LaPierre wrote:
The place to complain about this is the Fedora list since what CentOS has comes from them by way of RHEL. They, Fedora, are not apt to pay you any mind because they have already abandoned yum and are going with a new package manager named dnf soon to be appearing in a system near you.
DNF is a stupid name. The Feds could have called it yum2 - K.I.S.S.
Well thank God, and Linus, for symbolic links.
Amen. I concur. 'ln -s' is incredibly useful - it solves problems quickly, efficiently and effectively.
6 years ago I abandoned all Micro$oft for exclusive Centos. It was one of the best and happiest decisions in my computer life. Linux is so liberating - it is real computing.
Wishing all the world-wide Centos "industry" a very Happy New Year and thanking everyone for their support. I continue to learn and discover new things on this mailing list.
On 12/28/15 15:24, Alice Wonder wrote:
I ran into this exact issue last night -
When a computer is connected via IPv4 but the IPv4 a repo host connects to is not available, yum then tries the IPv6 address and will fail with a confusing message telling you it failed to connect to the IPv6 address.
I don't know if there is a way for yum to figure out whether the current network connection to the Internet is IPv4 or IPv6.
But if there is a way, it might make a usability improvement. A lot of people have no idea what IPv6 is and would be confused.
I was confused myself at first, wondering if DHCP pulled in IPv6 from the router.
Funny that you should say that. IPv6 is celebrating it's 20th birthday.
-
Alice Wonder -
Always Learning -
Marcelo Roccasalva -
Mark LaPierre