Bug 12420

Summary:	wireless network fails to set correct gateway when travelling to a new location
Product:	Mageia	Reporter:	Pierre Fortin <pf>
Component:	RPM Packages	Assignee:	Olivier Blin <mageia>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Pierre Fortin 2014-01-24 21:25:18 CET

Description of problem:  Closed laptop, traveled 48 miles to another location where I've used the wireless AP for years.  However, upon connecting to that local router, no traffic would pass...

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.254   0.0.0.0         UG    35     0        0 wlp8s0
169.254.0.0     0.0.0.0         255.255.0.0     U     35     0        0 wlp8s0
192.168.1.0     0.0.0.0         255.255.255.0   U     35     0        0 wlp8s0
192.168.56.0    0.0.0.0         255.255.255.0   U     0      0        0 vboxnet0

### Wrong default gateway...  that's the address of the default gateway which I left just over an hour ago, and where bug 12398 occurs...

# route del default 
# route add default gw 192.168.1.1



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


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:

Comment 1 Pierre Fortin 2014-01-25 19:53:56 CET

(see also bug 12398 comment 4)
In this bug (12420), the network does not have to be deleted, nor re-created; but it appears the default gateway does not get set correctly in this case.

Comment 2 Pierre Fortin 2014-02-12 20:32:46 CET

While working on a minor network issue, discovered why my network seemed slower than usual...   In addition to setting the wrong gateway, the primary DNS server was also incorrectly set in /etc/resolv.conf....  even after carrying this laptop back and forth between home and office which both use "nameserver 192.168.1.1"
It's been a few weeks since it's been to the remote location where the gateway is 192.168.1.254; but regardless of connecting to home and office, /etc/resolv.conf was not updated...

Manuel Hiebel 2014-02-12 21:47:04 CET

Assignee: bugsquad => mageia

Comment 3 Pierre Fortin 2015-07-25 15:45:34 CEST

Inactive. Don't know when I can test this again.

Status: NEW => RESOLVED
Resolution: (none) => OLD