Bug 224086 - NetworkManager brings up wired network when no wired is connected.
NetworkManager brings up wired network when no wired is connected.
Status: CLOSED DUPLICATE of bug 194124
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
6
All Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Aillon
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-23 19:21 EST by Steve Dickson
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-06-21 01:25:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Steve Dickson 2007-01-23 19:21:03 EST
Description of problem:
When logging into my T60 laptop the NetworkManager Applet (version 
0.6.4) will bring up the wired connection when there is nothing 
connect to the interface. I would expect NM should bring up the 
wireless connection since there is only one network available... 

After wired connection (incorrectly) brought up, I click on
the wireless network which brings down the wired connection
and brings up the wireless connection as expected. 

The wired interface is a Intel e1000
The wireless interface is a Intel ipw3945

The wired interface that has no connection 
is configure like:

eth0      Link encap:Ethernet  HWaddr 00:15:58:2E:22:22  
          inet addr:169.254.182.22  Bcast:169.254.255.255 Mask:255.255.0.0
          inet6 addr: fe80::215:58ff:fe2e:2222/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:24204 (23.6 KiB)

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


How reproducible:
Everytime 

Steps to Reproduce:
1. log in
2.
3.
  
Actual results:


Expected results:


Additional info:
ifcfg-eth0 (wired):
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:15:58:2E:22:22
ONBOOT=no
TYPE=Ethernet
USERCTL=yes
IPV6INIT=no
PEERDNS=yes

ifcfg-eth1 (wirless)
TYPE=Wireless
DEVICE=eth1
HWADDR=00:13:02:9a:25:29
BOOTPROTO=dhcp
NETMASK=
DHCP_HOSTNAME=
IPADDR=
DOMAIN=
ONBOOT=no
USERCTL=no
IPV6INIT=no
PEERDNS=yes
ESSID=
CHANNEL=1
MODE=Managed
RATE='36 Mb/s'
Comment 1 Matěj Cepl 2007-01-29 20:52:49 EST
Could be there some delay in activation of binary-only {drivers,dameon}? I have
similar problems with ndiswrapper-driven BCM4318, but I blame Broadcomm for not
providing documentation.
Comment 2 Dan Williams 2007-06-21 01:25:07 EDT

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

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