Arch Linux

greylogic

Member

Registered: 2009-08-15

Posts: 14

intel 3945ABG wireless frequently gets dropped

I have been using arch for almost a month and is very impressed. The system as a whole feels very lively. I just have one issue with my setup. My wireless connection frequently gets dropped. When i try '/etc/rc.d/network restart', it gets reconnected sucessfully. It works well till it gets dropped again after some random time.

i see a lot of "wlan0: no probe response from AP 00:18:4d:97:04:2a - disassociating" message before it gets disconnected. am i missing something in the configurations. My wirelss card is "Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)". I am using a netgear router.

I do a lot of downloading and during nights and when the network gets disconnected  all downloading stops. Is there a way to make network automatically try reconnecting when this happens. your help is appreciated.

log details
grep -i wlan everything.log

...
Sep  2 10:24:40 revelation kernel: wlan0: no probe response from AP 00:18:4d:97:04:2a - disassociating
Sep  2 10:24:56 revelation kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  2 10:24:58 revelation kernel: wlan0: authenticate with AP 00:18:4d:97:04:2a
Sep  2 10:24:58 revelation kernel: wlan0: authenticated
Sep  2 10:24:58 revelation kernel: wlan0: associate with AP 00:18:4d:97:04:2a
Sep  2 10:24:58 revelation kernel: wlan0: RX AssocResp from 00:18:4d:97:04:2a (capab=0x431 status=0 aid=1)
Sep  2 10:24:58 revelation kernel: wlan0: associated
Sep  2 10:24:58 revelation kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep  2 10:25:09 revelation kernel: wlan0: no IPv6 routers present
Sep  2 10:50:59 revelation kernel: wlan0: no probe response from AP 00:18:4d:97:04:2a - disassociating
Sep  2 10:53:44 revelation kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  2 10:53:46 revelation kernel: wlan0: authenticate with AP 00:18:4d:97:04:2a
Sep  2 10:53:46 revelation kernel: wlan0: authenticated
Sep  2 10:53:46 revelation kernel: wlan0: associate with AP 00:18:4d:97:04:2a
Sep  2 10:53:46 revelation kernel: wlan0: RX AssocResp from 00:18:4d:97:04:2a (capab=0x431 status=0 aid=1)
Sep  2 10:53:46 revelation kernel: wlan0: associated
Sep  2 10:53:46 revelation kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep  2 10:53:57 revelation kernel: wlan0: no IPv6 routers present
Sep  2 11:25:28 revelation kernel: wlan0: no probe response from AP 00:18:4d:97:04:2a - disassociating
Sep  2 11:26:35 revelation kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  2 11:26:37 revelation kernel: wlan0: authenticate with AP 00:18:4d:97:04:2a
Sep  2 11:26:37 revelation kernel: wlan0: authenticated
Sep  2 11:26:37 revelation kernel: wlan0: associate with AP 00:18:4d:97:04:2a
Sep  2 11:26:37 revelation kernel: wlan0: RX AssocResp from 00:18:4d:97:04:2a (capab=0x431 status=0 aid=1)
Sep  2 11:26:37 revelation kernel: wlan0: associated
Sep  2 11:26:37 revelation kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep  2 11:26:47 revelation kernel: wlan0: no IPv6 routers present
Sep  2 12:55:07 revelation kernel: wlan0: no probe response from AP 00:18:4d:97:04:2a - disassociating
Sep  2 12:55:18 revelation kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  2 12:55:20 revelation kernel: wlan0: authenticate with AP 00:18:4d:97:04:2a
Sep  2 12:55:20 revelation kernel: wlan0: authenticated
Sep  2 12:55:20 revelation kernel: wlan0: associate with AP 00:18:4d:97:04:2a
Sep  2 12:55:20 revelation kernel: wlan0: RX AssocResp from 00:18:4d:97:04:2a (capab=0x431 status=0 aid=1)
Sep  2 12:55:20 revelation kernel: wlan0: associated
Sep  2 12:55:20 revelation kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep  2 12:55:30 revelation kernel: wlan0: no IPv6 routers present
Sep  2 18:39:41 revelation kernel: wlan0: no probe response from AP 00:18:4d:97:04:2a - disassociating
Sep  2 18:41:23 revelation kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  2 18:41:23 revelation kernel: wlan0: direct probe to AP 00:18:4d:97:04:2a try 1
Sep  2 18:41:23 revelation kernel: wlan0 direct probe responded
Sep  2 18:41:23 revelation kernel: wlan0: authenticate with AP 00:18:4d:97:04:2a
Sep  2 18:41:23 revelation kernel: wlan0: authenticated
Sep  2 18:41:23 revelation kernel: wlan0: associate with AP 00:18:4d:97:04:2a
Sep  2 18:41:23 revelation kernel: wlan0: RX AssocResp from 00:18:4d:97:04:2a (capab=0x431 status=0 aid=3)
Sep  2 18:41:23 revelation kernel: wlan0: associated
Sep  2 18:41:23 revelation kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep  2 18:41:25 revelation dhcpcd: wlan0: reject NAK
Sep  2 18:41:29 revelation dhcpcd: wlan0: reject NAK
Sep  2 18:41:33 revelation kernel: wlan0: no IPv6 routers present
Sep  2 18:41:33 revelation dhcpcd: wlan0: reject NAK
Sep  3 10:35:31 revelation kernel: wlan0: no probe response from AP 00:18:4d:97:04:2a - disassociating
Sep  3 10:36:07 revelation kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  3 10:36:09 revelation kernel: wlan0: authenticate with AP 00:18:4d:97:04:2a
Sep  3 10:36:09 revelation kernel: wlan0: authenticated
Sep  3 10:36:09 revelation kernel: wlan0: associate with AP 00:18:4d:97:04:2a
Sep  3 10:36:09 revelation kernel: wlan0: RX AssocResp from 00:18:4d:97:04:2a (capab=0x431 status=0 aid=3)
Sep  3 10:36:09 revelation kernel: wlan0: associated
Sep  3 10:36:09 revelation kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep  3 10:36:20 revelation kernel: wlan0: no IPv6 routers present
Sep  3 14:42:22 revelation kernel: wlan0: no probe response from AP 00:18:4d:97:04:2a - disassociating
Sep  3 22:01:01 revelation kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  3 22:01:03 revelation kernel: wlan0: authenticate with AP 00:18:4d:97:04:2a
Sep  3 22:01:03 revelation kernel: wlan0: authenticated
Sep  3 22:01:03 revelation kernel: wlan0: associate with AP 00:18:4d:97:04:2a
Sep  3 22:01:03 revelation kernel: wlan0: RX AssocResp from 00:18:4d:97:04:2a (capab=0x431 status=0 aid=3)
Sep  3 22:01:03 revelation kernel: wlan0: associated
Sep  3 22:01:03 revelation kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep  3 22:01:13 revelation kernel: wlan0: no IPv6 routers present
Sep  3 23:46:29 revelation kernel: wlan0: no probe response from AP 00:18:4d:97:04:2a - disassociating
Sep  3 23:47:29 revelation kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  3 23:47:31 revelation kernel: wlan0: authenticate with AP 00:18:4d:97:04:2a
Sep  3 23:47:31 revelation kernel: wlan0: authenticated
Sep  3 23:47:31 revelation kernel: wlan0: associate with AP 00:18:4d:97:04:2a
Sep  3 23:47:31 revelation kernel: wlan0: RX AssocResp from 00:18:4d:97:04:2a (capab=0x431 status=0 aid=1)
Sep  3 23:47:31 revelation kernel: wlan0: associated
Sep  3 23:47:31 revelation kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep  3 23:47:41 revelation kernel: wlan0: no IPv6 routers present
Sep  4 02:11:05 revelation kernel: wlan0: no probe response from AP 00:18:4d:97:04:2a - disassociating
Sep  4 06:22:00 revelation kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  4 06:22:02 revelation kernel: wlan0: authenticate with AP 00:18:4d:97:04:2a
Sep  4 06:22:02 revelation kernel: wlan0: authenticated
Sep  4 06:22:02 revelation kernel: wlan0: associate with AP 00:18:4d:97:04:2a
Sep  4 06:22:02 revelation kernel: wlan0: RX AssocResp from 00:18:4d:97:04:2a (capab=0x431 status=0 aid=1)
Sep  4 06:22:02 revelation kernel: wlan0: associated
Sep  4 06:22:02 revelation kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep  4 06:22:13 revelation kernel: wlan0: no IPv6 routers present

I have pasted my configurations details below.
rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="local"
USEDIRECTISA="no"
TIMEZONE="America/New_York"
KEYMAP="us"
CONSOLEFONT="ter-v16b"
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(iwl3945)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="revelation"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
wlan0="dhcp"
INTERFACES=(wlan0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond dbus hal mpd)

/etc/conf.d/wireless

#
# Settings for wireless cards
#
# For each wireless interface declared in INTERFACES (in rc.conf), declare
# a wlan_${IF} variable that contains the arguments to be passed to
# iwconfig(8).  Then list the original interface name in the
# WLAN_INTERFACES array.
#

#wlan_eth0="eth0 mode managed essid default"
#WLAN_INTERFACES=(eth0)

ifconfig wlan0 up #dhcpcd wlan0
wlan_wlan0="wlan0 mode managed essid Raj-4k key xxxxxxxxxxxx"
WLAN_INTERFACES=(wlan0)

djszapi

Member

From: Cambridge, United Kingdom

Registered: 2009-06-14

Posts: 1,439

Website

Re: intel 3945ABG wireless frequently gets dropped

Hello greylogic!

Which card/driver/kernel do you use ? Did you try networkmanager/wicd too ?

---

http://lpapp.blogspot.com

greylogic

Member

Registered: 2009-08-15

Posts: 14

Re: intel 3945ABG wireless frequently gets dropped

hi,

card - 0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
driver - iwl3945
kernel - 2.6.30-ARCH

I mostly use my laptop at home. Since i don't need any network profiles, i have not tried networkmanager/wicd.

Will these help in automatic reconnection once the connection gets dropped?

Thanks

FinBhera

Member

Registered: 2009-09-11

Posts: 2

Re: intel 3945ABG wireless frequently gets dropped

I have the exact same problem, with the exact same driver, network card and kernel.

I have tried to connect with WICD and netcfg, but the connection still gets dropped at seemingly random times.  The network doesn't seem to matter as I get similar issues on WPA and WEP.

Not sure if there's any other info I can provide that will help either greylogic or myself...

1LordAnubis

Member

Registered: 2008-10-10

Posts: 253

Website

Re: intel 3945ABG wireless frequently gets dropped

strange... works here with the same driver, card and kernel. but I use wicd- i roam too much to go without it
btw, wicd is a pretty nice and light wireless manager that doesn't have too many deps
my rc.conf

#                                                                                 
# /etc/rc.conf - Main Configuration for Arch Linux                                
#                                                                                 
                                                                                  
# -----------------------------------------------------------------------         
# LOCALIZATION                                                                    
# -----------------------------------------------------------------------         
#                                                                                 
# LOCALE: available languages can be listed with the 'locale -a' command          
# HARDWARECLOCK: set to "UTC" or "localtime"                                      
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock           
# TIMEZONE: timezones are found in /usr/share/zoneinfo                            
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps                             
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)      
# CONSOLEMAP: found in /usr/share/kbd/consoletrans                                
# USECOLOR: use ANSI color sequences in startup messages                          
#                                                                                 
LOCALE="en_US.utf8"                                                               
HARDWARECLOCK="localtime"                                                         
USEDIRECTISA="no"                                                                 
TIMEZONE="US/Eastern"                                                             
KEYMAP="us"                                                                       
CONSOLEFONT=                                                                      
CONSOLEMAP=                                                                       
USECOLOR="yes"                                                                    
                                                                                  
# -----------------------------------------------------------------------         
# HARDWARE                                                                        
# -----------------------------------------------------------------------         
#                                                                                 
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed              
# MOD_BLACKLIST: Prevent udev from loading these modules                          
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.              
#                                                                                 
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.  
#                                                                                 
MOD_AUTOLOAD="yes"                                                                
#MOD_BLACKLIST=() #deprecated                                                     
MODULES=(e1000e iwl3945 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore fuse !pcspkr !snd_pcsp vboxdrv !tp_smapi nvram thinkpad_acpi)                                                                
                                                                                  
# Scan for LVM volume groups at startup, required if you use LVM                  
USELVM="no"                                                                       
                                                                                  
# -----------------------------------------------------------------------         
# NETWORKING                                                                      
# -----------------------------------------------------------------------         
#                                                                                 
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts                 
#                                                                                 
HOSTNAME="thor"                                                                   
                                                                                  
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.      
#                                                                                 
# Interfaces to start at boot-up (in this order)                                  
# Declare each interface then list in INTERFACES                                  
#   - prefix an entry in INTERFACES with a ! to disable it                        
#   - no hyphens in your interface names - Bash doesn't like it                   
#                                                                                 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")                            
# Wireless: See network profiles below                                            
#                                                                                 
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"            
#eth0="dhcp"                                                                      
#wlan0="dhcp"                                                                     
INTERFACES=(!eth0 !wlan0)                                                         
                                                                                  
# Routes to start at boot-up (in this order)                                      
# Declare each route then list in ROUTES                                          
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng @hal !network @netfs @crond @alsa !dhcdbd !networkmanager @wicd @fam @kdm !slim @acpi-cpufreq @laptop-mode !sshd !mpd !tor !privoxy)

---

Any society that would give up a little liberty to gain a little security will deserve neither and lose both.
-Benjamin Franklin
The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man.
-George Bernard Shaw

tomd123

Developer

Registered: 2008-08-12

Posts: 565

Re: intel 3945ABG wireless frequently gets dropped

I also have dropped connections at random, but it automatically associates itself again. BTW, I have the same kernel, drivers, and hardware as the OP.

FinBhera

Member

Registered: 2009-09-11

Posts: 2

Re: intel 3945ABG wireless frequently gets dropped

I upgraded my kernel to 2.6.31 (available as of yesterday in the testing repository) and have now had 4-5 hours of wireless usage with no dropped connection.  If you'd rather not try the newest kernel I know that everything worked fine on my system with 2.6.28 as well. (That was in ubuntu, mind you, but it might do the trick.)  Upgrading seemed easier than downgrading though and things seem to be working fine now.

I'll post again if for some reason my connection starts getting dropped again.

frankieboy

Member

Registered: 2009-04-12

Posts: 65

Re: intel 3945ABG wireless frequently gets dropped

Hi!

I have upgraded to 2.6.31, and wifi connection gets dropped and reconnected, using the same config as above, but with 2.6.30 I didn't have the connection drop. Any help apreciated.

Thx

pikiweb

Member

From: /bin/pwd

Registered: 2009-06-01

Posts: 8

Re: intel 3945ABG wireless frequently gets dropped

I have an Intel 2200BG, and got the same problem now (suddenly: no kernel updates, only wicd)

blacklisting ipv6 seems to have solved the problem, for now

steve___

Member

Registered: 2008-02-24

Posts: 452

Re: intel 3945ABG wireless frequently gets dropped

What channel/frequency are you guys communicating on?  Are you sure there aren't others around you using the same frequency?  Here is a command I use to see what's going on around me:

iwlist eth1 scanning | \
    awk -F '[ :=]+' '/ESS/{ printf $3" " } /Chan/{ printf $6" " } /Qual/{ printf ($3 "\n") } /Encr/{ printf $4" " }' | \
    sed 's/)//g' | \
    sort -k4

Last edited by steve___ (2009-09-28 03:27:27)

pikiweb

Member

From: /bin/pwd

Registered: 2009-06-01

Posts: 8

Re: intel 3945ABG wireless frequently gets dropped

If my case is really the same as the others (and it does seem so) it's nothing about frequency and interference: you can't explain with that such a sudden change as I had - same place, same distance, same hardware as the day before, but connection drop in some few seconds. And just disabling ipv6 made the connection being stable again. Five minutes after the first drop.

And I have experience too of weak wireless signal, as the one you get with other routers using the same frequency. But you don't get such messages in the dmesg output and the connection was never so unstable.

I'm just unsure if blacklisting module ipv6 is a right solution - is it actually useful for anything else than ipv6 (which, as I understood it, is by now mostly unused)?