Bug 661628

Summary:	Default route to gateway not set when NetworkManager connects to wifi
Product:	[Fedora] Fedora	Reporter:	Miguel Angel Perez <mangelp>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	14	CC:	carwyn, dcbw
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-12-17 23:56:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Miguel Angel Perez 2010-12-09 09:21:23 UTC

Description of problem:
  After upgrading using preupgrade from Fedora 13 to 14 NetworkManager seems to not set the default route throught the gateway after connecting to wifi (brings up wlan interface and it gets the ip via dhcp), DNS resolution works but since default route is not set you can't access anything outside your lan and you get a "connect: Network is unreachable" message for every connection attempt.

Version-Release number of selected component (if applicable):
  NetworkManager-0.8.1-10.git20100831.fc14.i686

How reproducible:
  Every time NetworkManager (re)connects to wifi.

Steps to Reproduce:
1. Log into your machine
2. Let NetworkManager connect
3. Try to access any internet address (gmail, google, anything like that ...) or use any console app to connnect, you will get a "connect: Network is unreachable".
  
Actual results:
  Applications can't connect to ip addresses outside local lan

Expected results:
  Applications can connect to ip addresses outside local lan

Additional info:
  Using command "ip route" I saw that default routing was missing, so as a workaround I set it by hand every time NetworkManager connects or reconnects to wifi with "ip route add default via 192.168.0.1".

Comment 1 Carwyn Edwards 2010-12-16 23:42:15 UTC

Dupe of #642596 fix in #639935 ?

Comment 2 Miguel Angel Perez 2010-12-17 23:56:29 UTC

Thanks for the pointer. Closing this one as a duplicate of #642596.

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