Re: ath0 weak connectivity
Sten Daniel Sørsdal wrote: > Sam Leffler wrote: >> I've lost context about your problem but it appears you're having >> trouble associating with "trejago" sometimes. The failed scan shows >> that your rssi was only 6 when you were having problems which is a very >> marginal signal so I'm not at all surprised you're having trouble. >> You've got strong signal ap's on overlapping channels (5 and 7) which >> are likely drowning the signal on your ap. I don't see anything the >> driver could do differently; this seems more an issue of your >> environment being very busy. I vaguely recall you were comparing the >> operation of the freebsd to windows. If so then perhaps the windows >> driver was doing better because it switched to XR mode and operating in >> XR mode you were able to punch through the noise to get to the ap. >> freebsd does not support XR mode. >> >> Sam >> > > Are there any plans to support this? XR mode, no--at least not in sta mode. > What about fastframes/bursting? 10Mhz, 5Mhz channels? Bursting has been there forever. Fast frames have been in p4 for nearly 2 years; no plans to commit to cvs. Variable channel width is probably something to deal with soon; it's been implemented in other code bases but not in a way I'm happy with. > WDS? Virtual AP? Is there any place where i can read about this? I recently did another WDS implementation that's quite nice but depends on VAP's. The vap support, as I've said many times, won't come into cvs until developers appear to take responsibility for legacy wireless drivers (just too much work for me to do by myself). > Apologies if any of these are already in the works. > I'd hoped to see some movement on this stuff but w/o help much of the work done over the past 2 years will continue to sit outside cvs. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0 weak connectivity
On Mon, September 25, 2006 3:46 pm, Sten Daniel Sørsdal wrote: > Sam Leffler wrote: >> freebsd does not support XR mode. > Are there any plans to support this? > What about fastframes/bursting? 10Mhz, 5Mhz channels? > WDS? Virtual AP? Is there any place where i can read about this? > Apologies if any of these are already in the works. Read through the papers listed at http://people.freebsd.org/~sam/ Very interesting reads. Freddie Cash [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0 weak connectivity
Sam Leffler wrote: > I've lost context about your problem but it appears you're having > trouble associating with "trejago" sometimes. The failed scan shows > that your rssi was only 6 when you were having problems which is a very > marginal signal so I'm not at all surprised you're having trouble. > You've got strong signal ap's on overlapping channels (5 and 7) which > are likely drowning the signal on your ap. I don't see anything the > driver could do differently; this seems more an issue of your > environment being very busy. I vaguely recall you were comparing the > operation of the freebsd to windows. If so then perhaps the windows > driver was doing better because it switched to XR mode and operating in > XR mode you were able to punch through the noise to get to the ap. > freebsd does not support XR mode. > > Sam > Are there any plans to support this? What about fastframes/bursting? 10Mhz, 5Mhz channels? WDS? Virtual AP? Is there any place where i can read about this? Apologies if any of these are already in the works. -- Sten Daniel Sørsdal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0 weak connectivity
Sam> I've lost context about your problem but it appears you're having Sam> trouble associating with "trejago" sometimes. The failed scan shows Sam> that your rssi was only 6 when you were having problems which is a Sam> very marginal signal so I'm not at all surprised you're having Sam> trouble. You've got strong signal ap's on overlapping channels (5 Sam> and 7) which are likely drowning the signal on your ap. I don't see Sam> anything the driver could do differently; this seems more an issue of Sam> your environment being very busy. I vaguely recall you were Sam> comparing the operation of the freebsd to windows. If so then I also thought of the environment issue, but it seems to me that the problem might still be elsewhere. Initially I encountered problems when I set up AP to transmit at 12% of full power, so logically I assumed that this must be not enough, and turned the AP signal up to 25, 50, and finally to 100%. What's interesting is that even on 100%, SNR wasn't really different from when it was 12%, and again ath0 didn't associate. This is doubly strange because the neighbor APs are located behind 2-3 solid brick walls, and still their SNR is 5 times higher than from my AP which is just nearby. Even when distance to AP is <1m, SNR is still comparable. Of course, I cannot control their AP signal strength, but I'd be interested to measure the signal strength from my and their APs independently, I guess there should be some regulations about max signal power... Also, I tried another channel, switching to channel 13 - did not help at all. Sam> freebsd does not support XR mode. Are there plans for implementing XR mode for ath? -- Sincerely, Dmitry Karasik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0 weak connectivity
Dmitry Karasik wrote: > Hi Sam! > > Sam> I do not understand what "bad connectivity" means. > > I'm not a native speaker so I've apparently used a wrong term, I apologize > for the confusion. Instead I should've probably said "low signal strength". > > Sam> If you provide > Sam> information like the mac+phy revs for the card, hal version, and > Sam> statistics from programs like athstats then it might be possible to > Sam> identify what's wrong. Otherwise look at turning on debugging at the > Sam> net80211 layer with wlandebug. Both athstats and wlandebug are found > Sam> in src/tools/tools (under net80211 and ath respectively). > > Here it is: > > dmesg: > > mem 0xa840-0xa840 irq 11 at device 2.0 on pci4 > ath0: [GIANT-LOCKED] > ath0: Ethernet address: 00:14:a4:80:f6:74 > mac 5.9 phy 4.3 radio 3.6 > > sysctl -a | grep ath | grep hal: > > hw.ath.hal.version: 0.9.16.16 > hw.ath.hal.dma_brt: 2 > hw.ath.hal.sw_brt: 10 > hw.ath.hal.swba_backoff: 0 > > Output after wlandebug +debug scan is too large to be quoted on the list, > so please take a look here: http://www.karasik.eu.org/misc/ath0.html , > probably you can find anything suspicious? > I've lost context about your problem but it appears you're having trouble associating with "trejago" sometimes. The failed scan shows that your rssi was only 6 when you were having problems which is a very marginal signal so I'm not at all surprised you're having trouble. You've got strong signal ap's on overlapping channels (5 and 7) which are likely drowning the signal on your ap. I don't see anything the driver could do differently; this seems more an issue of your environment being very busy. I vaguely recall you were comparing the operation of the freebsd to windows. If so then perhaps the windows driver was doing better because it switched to XR mode and operating in XR mode you were able to punch through the noise to get to the ap. freebsd does not support XR mode. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0 weak connectivity
Hi Sam! Sam> I do not understand what "bad connectivity" means. I'm not a native speaker so I've apparently used a wrong term, I apologize for the confusion. Instead I should've probably said "low signal strength". Sam> If you provide Sam> information like the mac+phy revs for the card, hal version, and Sam> statistics from programs like athstats then it might be possible to Sam> identify what's wrong. Otherwise look at turning on debugging at the Sam> net80211 layer with wlandebug. Both athstats and wlandebug are found Sam> in src/tools/tools (under net80211 and ath respectively). Here it is: dmesg: mem 0xa840-0xa840 irq 11 at device 2.0 on pci4 ath0: [GIANT-LOCKED] ath0: Ethernet address: 00:14:a4:80:f6:74 mac 5.9 phy 4.3 radio 3.6 sysctl -a | grep ath | grep hal: hw.ath.hal.version: 0.9.16.16 hw.ath.hal.dma_brt: 2 hw.ath.hal.sw_brt: 10 hw.ath.hal.swba_backoff: 0 Output after wlandebug +debug scan is too large to be quoted on the list, so please take a look here: http://www.karasik.eu.org/misc/ath0.html , probably you can find anything suspicious? -- Sincerely, Dmitry Karasik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0 weak connectivity
I'm sorry that I don't have freebsd on my system to do more testing but I'm pretty sure it's the ath0 interface that's causing the issue. When the interface is down limewire starts normally but when it's up it takes about 3 minutes to load. I have tried upgrading to stable but it's still the same issue. I will try to reinstall to do some more testing. On 9/18/06, Emil Stoyanov <[EMAIL PROTECTED]> wrote: Radu Adrian Zdrinca wrote: > I have had similar problems with the driver. The signal quality in > Windows is higher. But there are other problems. For example, when I > start Limewire I have to wait for about 3 minutes before it loads. I > am sure this is a problem with ath interface. > If I recall correctly, Limewire is java-based p2p app and java on Linux and FreeBSD requires a bit more resources than on Windows (according to SUN's recommendations i read the last time). I guess this is due to different strategies for memory management in the implementation of Java VM. It depends on what machines you are running java - on slower ones, or such with less memory, the time for loading java vm, and the time for allocation of memory for bigger apps may vary quite a lot, but 3 minutes looks like more problem of slow dns resolving, if many peers are connecting to you, etc.. I suppose this is not related to problems with driver, but anything is possible, just better testing and more investigations can prove that.. Cheers, Emil ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0 weak connectivity
Radu Adrian Zdrinca wrote: I have had similar problems with the driver. The signal quality in Windows is higher. But there are other problems. For example, when I start Limewire I have to wait for about 3 minutes before it loads. I am sure this is a problem with ath interface. If I recall correctly, Limewire is java-based p2p app and java on Linux and FreeBSD requires a bit more resources than on Windows (according to SUN's recommendations i read the last time). I guess this is due to different strategies for memory management in the implementation of Java VM. It depends on what machines you are running java - on slower ones, or such with less memory, the time for loading java vm, and the time for allocation of memory for bigger apps may vary quite a lot, but 3 minutes looks like more problem of slow dns resolving, if many peers are connecting to you, etc.. I suppose this is not related to problems with driver, but anything is possible, just better testing and more investigations can prove that.. Cheers, Emil ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0 weak connectivity
Radu Adrian Zdrinca wrote: > I have had similar problems with the driver. The signal quality in > Windows is higher. But there are other problems. For example, when I > start Limewire I have to wait for about 3 minutes before it loads. I > am sure this is a problem with ath interface. How do you know the signal quality in Windows is higher? I know nothing about Limewire and cannot say why you think problems with it are related to ath. Regardless, read my response to the original poster; I can't offer advise w/o meaningful information. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0 weak connectivity
Dmitry Karasik wrote: > Hi, > > Has anyone experienced problems with ath0 giving bad connectivity on > 6.1-STABLE? My wireless card reported as Atheros 5212 rapidly loses > connectivity if I move it more than 2-3 meters away from the access > point, but the same notebook connects well from under windows. > > I tried both kernel with both old device ath_rate_sample and ath_rate_onoe, > tried to play with AP's settings, changed transmit rate and beacon > interval, nothing helps. One interesting thing though is that "ifconfig ath0 > scan" reports my station as configured to 119ms beacon interval, while > it is set to 100ms actually. > > Anything else I can try? > ifconfig ath0 scan doesn't report your local configuration, it triggers a scan and reports the scan results. If your local station thinks the beacon internal is 119ms when it's really 100ms then something is very confused but it's unlikely to cause "bad connectivity" (unless you're operating the station in power save mode which isn't currently possible). I do not understand what "bad connectivity" means. If you provide information like the mac+phy revs for the card, hal version, and statistics from programs like athstats then it might be possible to identify what's wrong. Otherwise look at turning on debugging at the net80211 layer with wlandebug. Both athstats and wlandebug are found in src/tools/tools (under net80211 and ath respectively). Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0 weak connectivity
I have had similar problems with the driver. The signal quality in Windows is higher. But there are other problems. For example, when I start Limewire I have to wait for about 3 minutes before it loads. I am sure this is a problem with ath interface. On 9/18/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Send freebsd-stable mailing list submissions to freebsd-stable@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freebsd.org/mailman/listinfo/freebsd-stable or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of freebsd-stable digest..." Today's Topics: 1. Re: Problems with auditd -- resolved (Cristiano Deana) 2. Re: Attention Julian Stacey (Wilko Bulte) 3. [Q] multisync irmc/irmc_bluetooth plugins (Dennis Melentyev) 4. Re: Polling and em0 (Eugene Kazarinov) 5. Re: Attention Julian Stacey (Julian H. Stacey) 6. Re: Polling and em0 (Robert Watson) 7. Re: agh! Guys, who's breaking -STABLE's gmirror code?! (Jo Rhett) 8. Re: Attention Julian Stacey (Jase Thew) 9. Re: [Q] multisync irmc/irmc_bluetooth plugins (Pav Lucistnik) 10. Re: [Q] multisync irmc/irmc_bluetooth plugins (Henrik Brix Andersen) 11. Re: RELENG_6 power button ignored after halt if ACPI enabled (Mark Kirkwood) 12. Re: bge watchdog timeouts still happening (Ronald Klop) 13. Re: Problems with auditd -- resolved (Ganbold) 14. ath0 weak connectivity (Dmitry Karasik) 15. Re: Problems with auditd -- resolved (Robert Watson) 16. Re: Problems with auditd -- resolved (Ganbold) 17. Re: Problems with auditd -- resolved (Robert Watson) 18. Re: AGH! Guys, who's breaking -STABLE's GMIRROR code?! (Oliver Fromme) 19. Re: Problems with auditd -- resolved (Ganbold) 20. Re: AGH! Guys, who's breaking -STABLE's GMIRROR code?! (Dave Horsfall) 21. Re: Problems with auditd -- resolved (Robert Watson) 22. Re: [Q] multisync irmc/irmc_bluetooth plugins (Dennis Melentyev) 23. Too dumb to mount as non privileged user ([EMAIL PROTECTED]) 24. Re: Too dumb to mount as non privileged user (George Potapov) 25. Re: Too dumb to mount as non privileged user (Jona Joachim) -- Message: 1 Date: Sun, 17 Sep 2006 17:08:25 +0200 From: "Cristiano Deana" <[EMAIL PROTECTED]> Subject: Re: Problems with auditd -- resolved To: "Robert Watson" <[EMAIL PROTECTED]> Cc: Joerg Pernfuss <[EMAIL PROTECTED]>, Ganbold <[EMAIL PROTECTED]>,[EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 2006/9/17, Robert Watson <[EMAIL PROTECTED]>: > I've just comitted a fix to syscalls.master and regenerated the remaining > system call files, which should correct the auditctl: Invalid Argument error > being returned by auditd. In short order, this fix should be on the cvsup > mirrors -- please let me know if it resolves the problem you were > experiencing. auditd up and running, tnx Robert. I will submit more information. -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ -- Message: 2 Date: Sun, 17 Sep 2006 17:48:36 +0200 From: Wilko Bulte <[EMAIL PROTECTED]> Subject: Re: Attention Julian Stacey To: Maxim Konovalov <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED], "Julian H. Stacey" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii On Sun, Sep 17, 2006 at 12:49:43PM +0400, Maxim Konovalov wrote.. > On Sun, 17 Sep 2006, 02:31-0600, Scott Long wrote: > > > Julian H. Stacey wrote: > > > > > [EMAIL PROTECTED] > > > > > > > > > >Message-id: <[EMAIL PROTECTED]> > > > >From: Kris Kennaway <[EMAIL PROTECTED]> > > > > > > > > > >lol, that's the stupidest thing I've heard all week. > > > > > > > > > Inflamatory. Refered to postmaster. > > > > > > > Julian, meet Kris. Kris has been the head of the FreeBSD ports team for > > a large number of years. He's also written and presented several papers > > on FreeBSD performance, among many other hobbies and interests. He's a > > pretty laid back and fun guy, with a sharp sense of humor. > > > > Kris, meet Julian. Julian has been a FreeBSD user, contributor, and > > advocate since before there was such a such a thing as 'FreeBSD', or > > even 'http' for that matter. I've never
ath0 weak connectivity
Hi, Has anyone experienced problems with ath0 giving bad connectivity on 6.1-STABLE? My wireless card reported as Atheros 5212 rapidly loses connectivity if I move it more than 2-3 meters away from the access point, but the same notebook connects well from under windows. I tried both kernel with both old device ath_rate_sample and ath_rate_onoe, tried to play with AP's settings, changed transmit rate and beacon interval, nothing helps. One interesting thing though is that "ifconfig ath0 scan" reports my station as configured to 119ms beacon interval, while it is set to 100ms actually. Anything else I can try? -- Sincerely, Dmitry Karasik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
