Bug 1331189 - after update, 2nd Ethernet doesn't find internet
Summary: after update, 2nd Ethernet doesn't find internet
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 23
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-27 23:42 UTC by John A. Ward
Modified: 2016-12-20 20:10 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-12-20 20:10:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John A. Ward 2016-04-27 23:42:29 UTC
User-Agent:       Mozilla/5.0 (X11; Fedora; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0
Build Identifier: 

Can't ping google.com, can't Firefox into websites. If I do dnf update from root.
after about 8 minutes update starts and seems to run correctly, other than that it won't connect to anything, just hangs.

Reproducible: Always

Steps to Reproduce:
1.try connecting to Internet with Firefox and select a site, 
2.Also tried Konqueror
3.tried ping google.com, no response
Actual Results:  
Firefox sits there and eventually drops the request to connect.

Expected Results:  
Expect to connect, 

I brought a laptop (also running Linux) over to the desktop that won't work and connected to the cable the desktop uses, connected fine.

The other Ethernet port is connected to a local server with fixed ip address and works fine.

Comment 1 John A. Ward 2016-05-10 22:36:47 UTC
Red Hat service found a solution for a VERY similar problem I have had with RHEL6.7.

The condition seems to be caused by a fixed ip address on the first Ethernet that has a the fixed IP address for the Gateway. It seems the 2nd Ethernet can't do a dns connection for the 2nd Ethernet (if present).

You go to /etc/sysconfig/network/network-scripts and comment out the Gateway line in the ifcfg-enp2s0(the name of the 2nd Ethernet in my system).  Then the system works.  On the RHEL6.7 system and my Fedora System, I also set the IPv6 to IGNORED.

Now the Network connects, runs and all is wonderful.  This bug was also in a report I submitted for Fedora 20, the answer wasn't found and I downgraded to Fedora 20 to get my desktop back, which peeved the person helping, sorry but I had to get work done. This solution seems like it would apply to a number of dns bugs reported!

John

Comment 2 John A. Ward 2016-05-10 22:42:50 UTC
To clarify my comment, the enp2s0 ifconfig statement that had the Gateway command I commented out is for the 1st Ethernet of the 2 Ethernet system. Having the entry Gateway entry in the first Ethernet seems to stop Network manager from succeeding in making a dns connection for the 2nd Ethernet.

John

Comment 3 Fedora End Of Life 2016-11-25 07:29:26 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2016-12-20 20:10:03 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.