From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitri Seletski Date: Wed, 05 Aug 2009 21:10:19 +0100 Subject: [ath9k-devel] N mode In-Reply-To: <4A79E2CB.5020508@gmail.com> References: <20090615174758.GA22922@tesla> <4A36AEF8.5030703@gmail.com> <4A36CFF9.6070506@gmail.com> <20090616003715.GA5492@tesla> <4A6A56AD.2090104@gmail.com> <4A78FFE6.4030701@gmail.com> <20090805153427.GA4727@mosca> <4A79AB23.7020007@gmail.com> <4A79B49A.2060902@gmail.com> <20090805171151.GD4727@mosca> <4A79E2CB.5020508@gmail.com> Message-ID: <4A79E72B.7030207@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Dmitri Seletski wrote: > Luis R. Rodriguez wrote: > >> On Wed, Aug 05, 2009 at 09:34:34AM -0700, Dmitri Seletski wrote: >> >> >>> Right after i send message strange things started to happen. >>> >>> I didn't use wireless for a while, however, i started to use it now, my >>> land lady insist on it, since she really doesnt like cables in her house. >>> >>> for last couple of days it seemed to work without problems(in g mode), >>> this afternoon i have noticed that connection is shaky. I powerd off/on >>> my access point to improve situation - nothing changed. >>> >>> I decided to take a look at it. >>> >>> I decided to ping another machine connected over access point. >>> i noticed it freezes after some time for short period of time. >>> I decided to look at it over "iw event -t" as well >>> way i pinged other machine: "ping -A" >>> at some stage other machine stopped replying. >>> I looked into "iw event" >>> >>> and got this: >>> 1249487677.365807: wlan0 (phy #0): deauth 00:22:b0:bc:1e:1e -> >>> 00:1e:58:b4:f6:83 reason 4: Disassociated due to inactivity >>> >>> >> That should be your AP telling you that. Can you modify the >> time out of inactivity on your AP? >> >> >> >>> 1249487677.365880: wlan0 (phy #0): disconnected (local request) >>> >>> I believe it happened couple of second later after pings stopped >>> replying, but i may be wrong, as it happened too quickly. >>> >>> >>> >>> >>> iw dev wlan0 scan >>> BSS 00:1e:58:b4:f6:83 (on wlan0) >>> TSF: 13042924 usec (0d, 00:00:13) >>> freq: 2442 >>> beacon interval: 25 >>> capability: ESS ShortPreamble ShortSlotTime (0x0421) >>> signal: -57.00 dBm >>> SSID: dlink >>> Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 >>> DS Paramater set: channel 7 >>> ERP: >>> Extended supported rates: 24.0 36.0 48.0 54.0 >>> >>> I manually set wlan0 to use 11M(or less) connection, as my Broadband >>> conenction is 12mbit(and it is very quick), which is rather annoying. >>> >>> >> Your broadband connection throughput has nothing to do with your >> wireless rate selection. Your rate selection is a physical >> characteristic chosen on the device for communication. The bitrate >> is defined by the modulation scheme used (BPSK, QPSK, 16QAM, 64QAM, >> etc) amongst other things. >> >> If you select 54Mbit/s bit rate you won't get exactly 54 MBit/s, the >> bit PHY 54 MBit/s bit rate will be selected and what you actually >> get will vary due to many factors. >> >> >> >>> I hope it could be of help. >>> >>> From iwconfig: >>> wlan0 IEEE 802.11bgn ESSID:"dlink" >>> Mode:Managed Frequency:2.442 GHz Access Point: >>> 00:1E:58:B4:F6:83 >>> Bit Rate=1 Mb/s Tx-Power=20 dBm >>> Retry long limit:7 RTS thr:off Fragment thr:off >>> Encryption key:off >>> Power Management:on >>> Link Quality=61/70 Signal level=-49 dBm >>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >>> (usually link quality warries between 60-70) >>> >>> >> Try to ditch iwconfig, and use iw: iw dev wlan0 link >> >> For more info see: >> >> http://wireless.kernel.org/en/users/Documentation/iw >> http://wireless.kernel.org/en/users/Documentation/iw/replace-iwconfig >> >> >> >>> Machine started to suffer with disconnects. >>> >>> Below is fuller log. >>> 1249488753.366831: wlan0 (phy #0): deauth 00:22:b0:bc:1e:1e -> >>> 00:1e:58:b4:f6:83 reason 4: Disassociated due to inactivity >>> 1249488753.366985: wlan0 (phy #0): disconnected (local request) >>> 1249488848.660029: wlan0 (phy #0): auth 00:1e:58:b4:f6:83 -> >>> 00:22:b0:bc:1e:1e status: 0: Successful >>> 1249488848.668387: wlan0 (phy #0): assoc 00:1e:58:b4:f6:83 -> >>> 00:22:b0:bc:1e:1e status: 0: Successful >>> 1249488848.668489: wlan0 (phy #0): connected to 00:1e:58:b4:f6:83 >>> 1249488918.365949: wlan0 (phy #0): deauth 00:22:b0:bc:1e:1e -> >>> 00:1e:58:b4:f6:83 reason 4: Disassociated due to inactivity >>> >>> >> Can you tune your AP? >> >> Luis >> >> > Hi guys > I am on the verge of frustration. > I have updated firmware for AP(by an accident found more new version > from Australian mirror of dlink, i dont even know if its legal or not > for me to install that firmware). > I was messing around with combination of sli nvidia/ipv6 > I was clearly able to get connected over Nmode and bng moderebooted > computer i can connect over g mode now as well. I know that because i > was able to see from access point client info, which clearly stated > Nmode was working > Now i cant connect over n mode, and i get disconnected once every > minute. i get a lot of these: > > 1249500223.748309: wlan0 (phy #0): assoc 00:1e:58:b4:f6:83 -> > 00:22:b0:bc:1e:1e status: 0: Successful > 1249500223.748414: wlan0 (phy #0): connected to 00:1e:58:b4:f6:83 > 1249500374.770847: wlan0 (phy #0): deauth 00:22:b0:bc:1e:1e -> > 00:1e:58:b4:f6:83 reason 4: Disassociated due to inactivity > 1249500374.770924: wlan0 (phy #0): disconnected (local request) > 1249500389.484218: wlan0 (phy #0): auth 00:1e:58:b4:f6:83 -> > 00:22:b0:bc:1e:1e status: 0: Successful > 1249500389.492708: wlan0 (phy #0): assoc 00:1e:58:b4:f6:83 -> > 00:22:b0:bc:1e:1e status: 0: Successful > 1249500389.492815: wlan0 (phy #0): connected to 00:1e:58:b4:f6:83 > 1249500533.770593: wlan0 (phy #0): deauth 00:22:b0:bc:1e:1e -> > 00:1e:58:b4:f6:83 reason 4: Disassociated due to inactivity > 1249500533.770706: wlan0 (phy #0): disconnected (local request) > 1249500749.108242: wlan0 (phy #0): auth 00:1e:58:b4:f6:83 -> > 00:22:b0:bc:1e:1e status: 0: Successful > 1249500749.116632: wlan0 (phy #0): assoc 00:1e:58:b4:f6:83 -> > 00:22:b0:bc:1e:1e status: 0: Successful > 1249500749.116684: wlan0 (phy #0): connected to 00:1e:58:b4:f6:83 > 1249500758.770179: wlan0 (phy #0): deauth 00:22:b0:bc:1e:1e -> > 00:1e:58:b4:f6:83 reason 4: Disassociated due to inactivity > 1249500758.770225: wlan0 (phy #0): disconnected (local request) > > I started to get a lot of disconnects specifically today, before i > started to tinker with system. > My access point doesn't offer much by means of any time out > configuration.(i don't even know what i am looking for, but again access > point has small amount of options). > If you like i can try to make some sort of a tunnel, that will allow you > to remotely connect to access point. I wont give access to my own PC. > > I feel like writing a small script, which will be a loop to connect my > wifi card to ap. > > I am in a very bad situation(if not dire) i wont go into details, but i > am heavily dependent on internet, and I cant use it. > I specifically bought my wifi ap and wlan card, since i knew they were > compatible with linux (same brand, wlan was on chart of being compatible > with linux) if I knew than and there - o wouldnt buy them in the first > place, but than again, how can i buy something that is linux compatible? > I mean, i cant even trust linux compatibility charts anymore, they fail > miserably. > > I just need help. > Dmitri > Sorry, please cut out the emotional part. script seemed to help me a bit...