Bug 1940994

Summary: IPv6 problems after upgrading to Fedora 34
Product: [Fedora] Fedora Reporter: Dima Ryazanov <dima>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 34CC: fedoraproject, filbranden, flepied, kasong, lnykryn, msekleta, ssahani, s, systemd-maint, yuwatana, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-19 17:51:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dima Ryazanov 2021-03-19 17:50:18 UTC
Description of problem:

After upgrading to Fedora 34, about half of the time, I cannot connect to IPv6-enabled websites. E.g.:

$ curl -v 'https://mail.google.com/mail/u/0/'
*   Trying 2607:f8b0:4005:809::2005:443...
* Immediate connect fail for 2607:f8b0:4005:809::2005: Network is unreachable
* Closing connection 0
curl: (7) Couldn't connect to server

The DNS name resolves to both IPv4 and IPv6:

$ host mail.google.com
mail.google.com is an alias for googlemail.l.google.com.
googlemail.l.google.com has address 172.217.5.101
googlemail.l.google.com has IPv6 address 2607:f8b0:4005:801::2005

I don't have IPv6 routes:

$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.87.1    0.0.0.0         UG    600    0        0 wlp1s0
192.168.87.0    0.0.0.0         255.255.255.0   U     600    0        0 wlp1s0

I'm not sure if IPv6 has ever actually worked in my network - but I've never run into problems in Fedora 33, so I'm assuming it did not try to use IPv6.

Version-Release number of selected component (if applicable):


How reproducible:

About half of the time; looks like it picks IPv4 or IPv6 address at random.

Steps to Reproduce:
1. Connect to mail.google.com, use "dnf update", etc.
2.
3.

Actual results:
Network is unreachable

Expected results:
Use IPv4

Additional info:

Comment 1 Dima Ryazanov 2021-03-19 17:51:58 UTC
Sorry, filed a duplicate - bugzilla screwed up and said "bug 1940993 does not exist" when I submitted it.

*** This bug has been marked as a duplicate of bug 1940993 ***