Bug 141677

What type & driver are your wired ethernet card?

Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast
Ethernet (rev 90).

Driver = sis900

Network manger doens't work for me as well with 'ath0' (madwifi) on a thinkpad.
I'm currently using NetworkManager-gnome-0.3.2-3.cvs20041117 from rawhide.

It does attempt to change to wireless (on disconnecting eth0 - e1000) - but it
can't find the network.

I attempt to manually specify the 'essid' - but it still can't find the network.
(this is with unencrypted) network. I get the message:

'The requested wireless netowrk 'SSID' does nt appear to be in range. ...'

I've also tried with an encrypted network (didn't work)

Looks like the same problem as the initial bugreport - hence tagging along
(otherwise I can open another bugzilla entry)

BTW: I tired 'NetworkManager --no-daemon' - and tried setting ESSID from
'NetworkManagerInfo' - and I get the following:

NetworkManager: nm_device_activate_wireless(ath0): waiting for an access point.
NetworkManager: nm_hal_device_property_modified() called with udi =
/org/freedesktop/Hal/devices/pci_168c_12, key = net.interface_up, is_removed =
0, is_added = 0
NetworkManager: nm_hal_device_property_modified() called with udi =
/org/freedesktop/Hal/devices/pci_168c_12, key = net.interface_up, is_removed =
0, is_added = 0
NetworkManager: nm_device_wireless_activate(ath0) using essid 'MCS', with no
authentication.
NetworkManager: HAVELINK: act=0
NetworkManager: nm_device_activate_wireless(ath0): no link to 'MCS', or couldn't
get configure interface for IP.  Trying another access point.
NetworkManager: nm_device_activate_wireless(ath0): waiting for an access point.
N

Could you guys try with newer versions of NetworkManager &
NetworkManager-gnome that are in FC3-updates?

Thanks!
Dan

I have tried the latest update and the more recent CVS. The tray
applet just spins indefinitely. The graphic is well done and quite
appealing if that's any consolation. Nevertheless, no failover to
wireless. 

I am going to create a new BZ because the newer versions introduce a
new problem which is the necessity of having Bind running. This is a
terrible waste of resources given that I have a dedicated Bind server
on the network (which is also locally authoritative). Moreover, it
overwrites resolv.conf without consent.

There is an option in the CVS to compile without bind support which
does not alleviate the issue.

Without bind running, NM senses if I pull the ethernet plug but does
nothing further. It does not sense when the ethernet connection is
restored.

Current rawhide uses bind in a caching-nameserver situation.  This
will persist until we can get lwresd & nss_lwres functional.

FC3-updates version does _NOT_ use bind, with slightly reduced
functionality.

There was also an FC-3 update to HAL that may fix the ethernet link
problem.  There was a bug in HAL that caused it to stop monitoring the
netlink socket for link status change events.

Dan

NetworkManager-0.3.3-1.cvs20050119.2.fc3.i386.rpm
NetworkManager-devel-0.3.3-1.cvs20050119.2.fc3
NetworkManager-glib-0.3.3-1.cvs20050119.2.fc3
NetworkManager-gnome-0.3.3-1.cvs20050119.2.fc3
hal=hal-0.4.7-1.FC3

I am assuming those are the update versions. If I'm a nitwit and got
it wrong, please advise.

This time, NM overwrote resolv.conf and left it blank.
No failover to ath when I pulled the eth0 plug.. 

Confirmed, this is caused by a previous "feature" (ahem, hack) that
left an existing configured wired device up, but short-circuited the
DNS process.  That was removed in CVS on Jan 21, and should show up in
a further update for FC3.