Intel Centrino Advanced-N 6205 wireless Network controller problem

wangsiyuan · 2014-08-24 14:12:52

Hi, all
My computer's wireless connection has a problem. The Wifi ad hoc is at another room. My Wfi strength is 50% or so. I found my net speed is very slow. I ping the gateway, sometimes I got 2000ms delay. I think this is a driver problem, because my friend's Windows laptop has a good speed in the same situation. If I take my laptop near to the Wifi adhoc, The net speed is also good.
So I think my driver only works fine when the signal is strong. If the Wifi signal is weak, there are some connection problem.
Does anyone has the same problem as me?

Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
driver: iwlwifi
kernel: 3.16.1-1-ARCH
I use Network-Manager, maybe it is its problem?

Thank you very much.

ewaller · 2014-08-24 18:38:52

If it is an ad hoc setup, I assume you are all on the same band. Can you tell us if you are on the 2.4 GHz or the 5 GHz band?
Also, if you could post the output of iw list and of sudo iw wlan0 scan (replace wlan0 with the name of your interface, of course)

Pse · 2014-08-24 19:00:06

I've seen some drivers behave in erratic ways when in ad-hoc mode. Have you tried setting an AP in the same spot as the other ad-hoc station temporarily to see if it works better?

wangsiyuan · 2014-08-25 14:10:08

iw list output

$ sudo iw list
Wiphy phy0
	max # scan SSIDs: 20
	max scan IEs length: 195 bytes
	Coverage class: 0 (up to 0m)
	Device supports RSN-IBSS.
	Supported Ciphers:
		* WEP40 (00-0f-ac:1)
		* WEP104 (00-0f-ac:5)
		* TKIP (00-0f-ac:2)
		* CCMP (00-0f-ac:4)
	Available Antennas: TX 0 RX 0
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
	Band 1:
		Capabilities: 0x1072
			HT20/HT40
			Static SM Power Save
			RX Greenfield
			RX HT20 SGI
			RX HT40 SGI
			No RX STBC
			Max AMSDU length: 3839 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 4 usec (0x05)
		HT TX/RX MCS rate indexes supported: 0-15, 32
		Bitrates (non-HT):
			* 1.0 Mbps
			* 2.0 Mbps (short preamble supported)
			* 5.5 Mbps (short preamble supported)
			* 11.0 Mbps (short preamble supported)
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 2412 MHz [1] (15.0 dBm)
			* 2417 MHz [2] (15.0 dBm)
			* 2422 MHz [3] (15.0 dBm)
			* 2427 MHz [4] (15.0 dBm)
			* 2432 MHz [5] (15.0 dBm)
			* 2437 MHz [6] (15.0 dBm)
			* 2442 MHz [7] (15.0 dBm)
			* 2447 MHz [8] (15.0 dBm)
			* 2452 MHz [9] (15.0 dBm)
			* 2457 MHz [10] (15.0 dBm)
			* 2462 MHz [11] (15.0 dBm)
			* 2467 MHz [12] (15.0 dBm) (no IR)
			* 2472 MHz [13] (15.0 dBm) (no IR)
	Band 2:
		Capabilities: 0x1072
			HT20/HT40
			Static SM Power Save
			RX Greenfield
			RX HT20 SGI
			RX HT40 SGI
			No RX STBC
			Max AMSDU length: 3839 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 4 usec (0x05)
		HT TX/RX MCS rate indexes supported: 0-15, 32
		Bitrates (non-HT):
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 5180 MHz [36] (15.0 dBm) (no IR)
			* 5200 MHz [40] (15.0 dBm) (no IR)
			* 5220 MHz [44] (15.0 dBm) (no IR)
			* 5240 MHz [48] (15.0 dBm) (no IR)
			* 5260 MHz [52] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5280 MHz [56] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5300 MHz [60] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5320 MHz [64] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5500 MHz [100] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5520 MHz [104] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5540 MHz [108] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5560 MHz [112] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5580 MHz [116] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5600 MHz [120] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5620 MHz [124] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5640 MHz [128] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5660 MHz [132] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5680 MHz [136] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5700 MHz [140] (15.0 dBm) (no IR, radar detection)
			  DFS state: usable (for 1432073 sec)
			* 5745 MHz [149] (15.0 dBm) (no IR)
			* 5765 MHz [153] (15.0 dBm) (no IR)
			* 5785 MHz [157] (15.0 dBm) (no IR)
			* 5805 MHz [161] (15.0 dBm) (no IR)
			* 5825 MHz [165] (15.0 dBm) (no IR)
	Supported commands:
		 * new_interface
		 * set_interface
		 * new_key
		 * start_ap
		 * new_station
		 * new_mpath
		 * set_mesh_config
		 * set_bss
		 * authenticate
		 * associate
		 * deauthenticate
		 * disassociate
		 * join_ibss
		 * join_mesh
		 * set_tx_bitrate_mask
		 * frame
		 * frame_wait_cancel
		 * set_wiphy_netns
		 * set_channel
		 * set_wds_peer
		 * probe_client
		 * set_noack_map
		 * register_beacons
		 * start_p2p_device
		 * set_mcast_rate
		 * Unknown command (104)
		 * connect
		 * disconnect
	Supported TX frame types:
		 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
	Supported RX frame types:
		 * IBSS: 0x40 0xb0 0xc0 0xd0
		 * managed: 0x40 0xd0
		 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * mesh point: 0xb0 0xc0 0xd0
		 * P2P-client: 0x40 0xd0
		 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * P2P-device: 0x40 0xd0
	WoWLAN support:
		 * wake up on disconnect
		 * wake up on magic packet
		 * wake up on pattern match, up to 20 patterns of 16-128 bytes,
		   maximum packet offset 0 bytes
		 * can do GTK rekeying
		 * wake up on GTK rekey failure
		 * wake up on EAP identity request
		 * wake up on rfkill release
	software interface modes (can always be added):
		 * AP/VLAN
		 * monitor
	valid interface combinations:
		 * #{ managed } <= 1, #{ AP } <= 1,
		   total <= 2, #channels <= 1, STA/AP BI must match
		 * #{ managed } <= 2,
		   total <= 2, #channels <= 1
	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	Device supports TX status socket option.
	Device supports HT-IBSS.
	Device supports scan flush.

iw wlan0 scan output. I connect this Wifi

$ sudo iw wlan0 scan
BSS e4:d3:32:e9:eb:5a(on wlan0) -- associated
	TSF: 96548868570 usec (1d, 02:49:08)
	freq: 2437
	beacon interval: 100 TUs
	capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
	signal: -58.00 dBm
	last seen: 0 ms ago
	Information elements from Probe Response frame:
	SSID: youcanyouup
	Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 
	DS Parameter set: channel 6
	ERP: <no flags>
	Extended supported rates: 24.0 36.0 48.0 54.0 
	HT capabilities:
		Capabilities: 0x106e
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			No RX STBC
			Max AMSDU length: 3839 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: No restriction (0x00)
		HT RX MCS rate indexes supported: 0-15
		HT TX MCS rate indexes are undefined
	HT operation:
		 * primary channel: 6
		 * secondary channel offset: below
		 * STA channel width: any
		 * RIFS: 0
		 * HT protection: 20 MHz
		 * non-GF present: 0
		 * OBSS non-GF present: 0
		 * dual beacon: 0
		 * dual CTS protection: 0
		 * STBC beacon: 0
		 * L-SIG TXOP Prot: 0
		 * PCO active: 0
		 * PCO phase: 0
	RSN:	 * Version: 1
		 * Group cipher: CCMP
		 * Pairwise ciphers: CCMP
		 * Authentication suites: PSK
		 * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
	WPA:	 * Version: 1
		 * Group cipher: CCMP
		 * Pairwise ciphers: CCMP
		 * Authentication suites: PSK
	WMM:	 * Parameter version 1
		 * BE: CW 15-1023, AIFSN 3
		 * BK: CW 15-1023, AIFSN 7
		 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
		 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
	WPS:	 * Version: 1.0
		 * Wi-Fi Protected Setup State: 2 (Configured)
		 * Response Type: 3 (AP)
		 * UUID: 00000000-0000-1000-0000-e4d332e9eb5a
		 * Manufacturer: TP-LINK
		 * Model: TL-WR842N
		 * Model Number: 4.0
		 * Serial Number: 1.1.1.3
		 * Primary Device Type: 6-0050f204-1
		 * Device name: Wireless N Router WR842N
		 * Config methods: Display, PBC
		 * RF Bands: 0x1
		 * Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20

ewaller wrote:

If it is an ad hoc setup, I assume you are all on the same band. Can you tell us if you are on the 2.4 GHz or the 5 GHz band?
Also, if you could post the output of iw list and of sudo iw wlan0 scan (replace wlan0 with the name of your interface, of course)

ewaller · 2014-08-25 15:49:27

signal: -58.00 dBm

That signal is down in the mud; I don't know what 50% means, but on my system my reported receive power is -43dBm. You are 15dB down from there. When discussing power, each 3dB represents a loss of half the power. At -15 dB compared to my results, the RF power in your receiver is a bit more than 1% of the power in my receiver (Correction: about 3%). My machine is in a wood frame single family dwelling with 3 plaster walls and 15 meters between the computer and the router.

Let's see how many packets are being dropped. What are the contents of /proc/net/wireless ?
Does this work with a different operating system (*cough*)Windows(*cough*)
I know you said that it works okay with your friend's system, but can you check the AP and see how much power it is putting out? You said it was ad hoc, so I wonder if it is running at a reduced power level.

Last edited by ewaller (2014-08-25 15:55:37)

wangsiyuan · 2014-08-26 01:46:45

I'm sorry, maybe It is wrong to use "ad hoc". Actually it is a wireless router, something like http://www.amazon.com/TP-LINK-TL-WR842N … +TL-WR842N

50% means: I use NetworkManager to manage network, there is a tray of signal. when I move mouse to the tray. it display "50%"

When I come back, I'll check /proc/net/wireless

Thank you very much!

ewaller wrote:

signal: -58.00 dBm
That signal is down in the mud; I don't know what 50% means, but on my system my reported receive power is -43dBm. You are 15dB down from there. When discussing power, each 3dB represents a loss of half the power. At -15 dB compared to my results, the RF power in your receiver is a bit more than 1% of the power in my receiver (Correction: about 3%). My machine is in a wood frame single family dwelling with 3 plaster walls and 15 meters between the computer and the router.
Let's see how many packets are being dropped. What are the contents of /proc/net/wireless ?
Does this work with a different operating system (*cough*)Windows(*cough*)
I know you said that it works okay with your friend's system, but can you check the AP and see how much power it is putting out? You said it was ad hoc, so I wonder if it is running at a reduced power level.

wangsiyuan · 2014-08-26 15:25:34

$ sudo cat  /proc/net/wireless
[sudo] password for siyuan: 
Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE
 face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 22
 wlan0: 0000   42.  -68.  -256        0      0      0   1050   3652        0

ewaller wrote:

signal: -58.00 dBm
That signal is down in the mud; I don't know what 50% means, but on my system my reported receive power is -43dBm. You are 15dB down from there. When discussing power, each 3dB represents a loss of half the power. At -15 dB compared to my results, the RF power in your receiver is a bit more than 1% of the power in my receiver (Correction: about 3%). My machine is in a wood frame single family dwelling with 3 plaster walls and 15 meters between the computer and the router.
Let's see how many packets are being dropped. What are the contents of /proc/net/wireless ?
Does this work with a different operating system (*cough*)Windows(*cough*)
I know you said that it works okay with your friend's system, but can you check the AP and see how much power it is putting out? You said it was ad hoc, so I wonder if it is running at a reduced power level.

Pse · 2014-08-26 18:49:13

ewaller wrote:

signal: -58.00 dBm
That signal is down in the mud

Actually, -58dBm is a fairly reasonable power level. I've seen stable 802.11g connections at around -70dBm (though they were slower than 54Mbps).

wangsiyuan wrote:

I'm sorry, maybe It is wrong to use "ad hoc". Actually it is a wireless router

If the other endpoint is a router, then setup infrastructure mode on it and test again.

Last edited by Pse (2014-08-26 18:50:15)

Arch Linux

#1 2014-08-24 14:12:52

Intel Centrino Advanced-N 6205 wireless Network controller problem

#2 2014-08-24 18:38:52

Re: Intel Centrino Advanced-N 6205 wireless Network controller problem

#3 2014-08-24 19:00:06

Re: Intel Centrino Advanced-N 6205 wireless Network controller problem

#4 2014-08-25 14:10:08

Re: Intel Centrino Advanced-N 6205 wireless Network controller problem

#5 2014-08-25 15:49:27

Re: Intel Centrino Advanced-N 6205 wireless Network controller problem

#6 2014-08-26 01:46:45

Re: Intel Centrino Advanced-N 6205 wireless Network controller problem

#7 2014-08-26 15:25:34

Re: Intel Centrino Advanced-N 6205 wireless Network controller problem

#8 2014-08-26 18:49:13

Re: Intel Centrino Advanced-N 6205 wireless Network controller problem

Board footer