On 04/17/2010 07:56 PM, Kurian Thayil wrote:
On Thu, 2010-04-15 at 21:07 -0700, Paolo Galtieri wrote:
On 04/15/2010 08:42 PM, Kurian Thayil wrote:
Hi All,
Since the installation of F12 in my Acer Aspire 580 series laptop
with Intel 3945ABG wireless module, I am having the issue where my
Wifi link gets deactivated and activated (disconnects & connects)
frequently. AP is a Netgear WGR router with WEP enabled. Was using
Debian GNU/Linux (Etch & Lenny) and I was able to work without any
issues. The following is the /var/log/messages when a typical wifi
session is disabled and enabled. This issue was severe when there
was no security enabled in the router (I gave only MAC address level
security). When I included WEP, it became better. Module iwl3945 is
loaded in the kernel along with iwlcore, mac80211. Any idea on how
to avoid this completely?
Apr 16 09:03:36 localhost NetworkManager: <info> (wlan0): device
state change: 8 -> 2 (reason 0)
Apr 16 09:03:36 localhost NetworkManager: <info> (wlan0):
deactivating device (reason: 0).
Apr 16 09:03:36 localhost NetworkManager: <info> (wlan0): canceled
DHCP transaction, dhcp client pid 3603
Apr 16 09:03:36 localhost NetworkManager: <WARN> check_one_route():
(wlan0) error -34 returned from rtnl_route_del(): Sucess#012
Apr 16 09:03:36 localhost avahi-daemon[1265]: Withdrawing address
record for 192.168.0.4 on wlan0.
Apr 16 09:03:36 localhost avahi-daemon[1265]: Leaving mDNS multicast
group on interface wlan0.IPv4 with address 192.168.0.4.
Apr 16 09:03:36 localhost avahi-daemon[1265]: Interface wlan0.IPv4
no longer relevant for mDNS.
Apr 16 09:03:36 localhost NetworkManager: <info> (wlan0): taking
down device.
Apr 16 09:03:36 localhost avahi-daemon[1265]: Withdrawing address
record for fe80::21b:77ff:fe51:4fcd on wlan0.
Apr 16 09:03:37 localhost NetworkManager: <info> (wlan0): bringing
up device.
Apr 16 09:03:37 localhost kernel: Registered led device: iwl-phy0::radio
Apr 16 09:03:37 localhost kernel: Registered led device: iwl-phy0::assoc
Apr 16 09:03:37 localhost kernel: Registered led device: iwl-phy0::RX
Apr 16 09:03:37 localhost kernel: Registered led device: iwl-phy0::TX
Apr 16 09:03:37 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link
is not ready
Apr 16 09:03:37 localhost NetworkManager: <info> (wlan0):
supplicant interface state: starting -> ready
Apr 16 09:03:37 localhost NetworkManager: <info> (wlan0): device
state change: 2 -> 3 (reason 42)
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
starting connection 'Auto virusk'
Apr 16 09:03:37 localhost NetworkManager: <info> (wlan0): device
state change: 3 -> 4 (reason 0)
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) scheduled...
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) started...
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) scheduled...
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) complete.
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) starting...
Apr 16 09:03:37 localhost NetworkManager: <info> (wlan0): device
state change: 4 -> 5 (reason 0)
Apr 16 09:03:37 localhost NetworkManager: <info> Activation
(wlan0/wireless): access point 'Auto virusk' has security, but
secrets are required.
Apr 16 09:03:37 localhost NetworkManager: <info> (wlan0): device
state change: 5 -> 6 (reason 0)
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) complete.
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) scheduled...
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) started...
Apr 16 09:03:37 localhost NetworkManager: <info> (wlan0): device
state change: 6 -> 4 (reason 0)
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) scheduled...
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 1 of 5 (Device Prepare) complete.
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) starting...
Apr 16 09:03:37 localhost NetworkManager: <info> (wlan0): device
state change: 4 -> 5 (reason 0)
Apr 16 09:03:37 localhost NetworkManager: <info> Activation
(wlan0/wireless): connection 'Auto virusk' has security, and secrets
exist. No new secrets needed.
Apr 16 09:03:37 localhost NetworkManager: <info> Config: added
'ssid' value 'virusk'
Apr 16 09:03:37 localhost NetworkManager: <info> Config: added
'scan_ssid' value '1'
Apr 16 09:03:37 localhost NetworkManager: <info> Config: added
'key_mgmt' value 'NONE'
Apr 16 09:03:37 localhost NetworkManager: <info> Config: added
'auth_alg' value 'OPEN'
Apr 16 09:03:37 localhost NetworkManager: <info> Config: added
'wep_key0' value '<omitted>'
Apr 16 09:03:37 localhost NetworkManager: <info> Config: added
'wep_tx_keyidx' value '0'
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) complete.
Apr 16 09:03:37 localhost NetworkManager: <info> Config: set
interface ap_scan to 1
Apr 16 09:03:37 localhost NetworkManager: <info> (wlan0):
supplicant connection state: scanning -> disconnected
Apr 16 09:03:37 localhost NetworkManager: <info> (wlan0):
supplicant connection state: disconnected -> associating
Apr 16 09:03:37 localhost kernel: ADDRCONF(NETDEV_CHANGE): wlan0:
link becomes ready
Apr 16 09:03:37 localhost NetworkManager: <info> (wlan0):
supplicant connection state: associating -> associated
Apr 16 09:03:37 localhost NetworkManager: <info> (wlan0):
supplicant connection state: associated -> completed
Apr 16 09:03:37 localhost NetworkManager: <info> Activation
(wlan0/wireless) Stage 2 of 5 (Device Configure) successful.
Connected to wireless network 'virusk'.
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 3 of 5 (IP Configure Start) scheduled.
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 3 of 5 (IP Configure Start) started...
Apr 16 09:03:37 localhost NetworkManager: <info> (wlan0): device
state change: 5 -> 7 (reason 0)
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Beginning DHCP transaction (timeout in 45 seconds)
Apr 16 09:03:37 localhost NetworkManager: <info> dhclient started
with pid 3807
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 4 of 5 (IP6 Configure Get) scheduled...
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 3 of 5 (IP Configure Start) complete.
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 4 of 5 (IP6 Configure Get) started...
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 4 of 5 (IP6 Configure Get) complete.
Apr 16 09:03:37 localhost dhclient[3807]: Internet Systems
Consortium DHCP Client 4.1.1
Apr 16 09:03:37 localhost dhclient[3807]: Copyright 2004-2010
Internet Systems Consortium.
Apr 16 09:03:37 localhost dhclient[3807]: All rights reserved.
Apr 16 09:03:37 localhost dhclient[3807]: For info, please visit
https://www.isc.org/software/dhcp/
Apr 16 09:03:37 localhost dhclient[3807]:
Apr 16 09:03:37 localhost NetworkManager: <info> DHCP: device wlan0
state changed normal exit -> preinit
Apr 16 09:03:37 localhost dhclient[3807]: Listening on
LPF/wlan0/00:1b:77:51:4f:cd
Apr 16 09:03:37 localhost dhclient[3807]: Sending on
LPF/wlan0/00:1b:77:51:4f:cd
Apr 16 09:03:37 localhost dhclient[3807]: Sending on Socket/fallback
Apr 16 09:03:37 localhost dhclient[3807]: DHCPREQUEST on wlan0 to
255.255.255.255 port 67
Apr 16 09:03:37 localhost dhclient[3807]: DHCPACK from 192.168.0.1
Apr 16 09:03:37 localhost NetworkManager: <info> DHCP: device wlan0
state changed preinit -> reboot
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 4 of 5 (IP4 Configure Get) scheduled...
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 4 of 5 (IP4 Configure Get) started...
Apr 16 09:03:37 localhost NetworkManager: <info> address 192.168.0.4
Apr 16 09:03:37 localhost NetworkManager: <info> prefix 24
(255.255.255.0)
Apr 16 09:03:37 localhost NetworkManager: <info> gateway 192.168.0.1
Apr 16 09:03:37 localhost NetworkManager: <info> nameserver
'192.168.0.1'
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 5 of 5 (IP Configure Commit) scheduled...
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 4 of 5 (IP4 Configure Get) complete.
Apr 16 09:03:37 localhost NetworkManager: <info> Activation (wlan0)
Stage 5 of 5 (IP Configure Commit) started...
Apr 16 09:03:37 localhost avahi-daemon[1265]: Joining mDNS multicast
group on interface wlan0.IPv4 with address 192.168.0.4.
Apr 16 09:03:37 localhost avahi-daemon[1265]: New relevant interface
wlan0.IPv4 for mDNS.
Apr 16 09:03:37 localhost avahi-daemon[1265]: Registering new
address record for 192.168.0.4 on wlan0.IPv4.
Apr 16 09:03:37 localhost dhclient[3807]: bound to 192.168.0.4 --
renewal in 36412 seconds.
Apr 16 09:03:38 localhost NetworkManager: <info> (wlan0): device
state change: 7 -> 8 (reason 0)
Apr 16 09:03:38 localhost NetworkManager: <info> Policy set 'Auto
virusk' (wlan0) as default for routing and DNS.
Apr 16 09:03:38 localhost NetworkManager: <info> Activation (wlan0)
successful, device activated.
Apr 16 09:03:38 localhost NetworkManager: <info> Activation (wlan0)
Stage 5 of 5 (IP Configure Commit) complete.
Apr 16 09:03:39 localhost avahi-daemon[1265]: Registering new
address record for fe80::21b:77ff:fe51:4fcd on wlan0.*.
Regards,
Kurian Thayil.
I also have a 3945ABG and I see no wifi issues with F12. However, I
use WPA authentication. I have on rare occasions had some of my
connections get dropped while transferring data while other
connections (even to the same system) remaining active.
Paolo
Paolo
Hi Paolo,
Will it be possible for you to check with WEP authentication? Just to
make sure, its not dependent on the authentication method. Due to this
connection issue, I have started using Wired Connection. I know its a
security issue, hence its even OK if you can't change the
authentication method. Thanks in advance.
Regards,
Kurian Thayil.
I setup a WEP connection and it connected just fine. It's been running
for about 10 minutes with no disconnects. I'll keep running for a
while. I've been doing updates to try to keep the network busy to see
if that has any effect.
Paolo
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
