From owner-freebsd-current@FreeBSD.ORG Wed Oct 13 19:38:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8B5A16A4CE for ; Wed, 13 Oct 2004 19:38:00 +0000 (GMT) Received: from sage.ts.co.nz (sage.tasman.net [202.49.92.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4CA043D2D for ; Wed, 13 Oct 2004 19:37:59 +0000 (GMT) (envelope-from marcos@ThePacific.Net) Received: from sage.ts.co.nz ([172.16.21.1]) by sage.ts.co.nz (8.12.11/8.12.10) with ESMTP id i9DJbvJU012091 for ; Thu, 14 Oct 2004 08:37:57 +1300 Received: from [172.16.20.10] (gateway-nelson.thepacific.net [202.49.95.33]) by sage.ts.co.nz (8.12.11/8.12.10) with ESMTP id i9DJZtmr010129; Thu, 14 Oct 2004 08:35:55 +1300 Message-ID: <416D8311.8090406@ThePacific.Net> Date: Thu, 14 Oct 2004 08:33:37 +1300 From: "Marcos Biscaysaqu - ThePacific.net" User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040910) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Leffler , freebsd-current@freebsd.org References: <200410131634.37118.jhugo@icomtek.csir.co.za> <416D5081.3030305@errno.com> In-Reply-To: <416D5081.3030305@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ath hostap - long delays between wifi clients via ath AP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Oct 2004 19:38:00 -0000 He there. I had the same problem even with more clients, I never could fix it, the only weird thing on the traffic is the continuous Ierrs and Oerrs errors. Another weird problem it is on the clients Im start to get ping over 200ms when the normal is 2ms and the only way to fix it is login on the box and run "wicontrol -i ath0 -L" and the ping come back to normal other thing is the connection doesn't work very well or doesn't work at all when the signal quality of the client is more than 35-38. I can't fix this problems, Im only allowed to test. I tried the atheros freebsd driver for more than a year, on different situation, hardware, version, etc. always with the same problem it is a problem with the driver?? or the chipset is not good enough??? cheers Marcos Biscaysaqu Thepacific.net Sam Leffler wrote: > Johann Hugo wrote: > >> Hi >> >> I've been playing with ath hostap mode today when I noticed someting >> very strange. Ping delays are very high (100 - 200ms) between two >> wifi clients connected to the same ath hostap AP, but if I ping the >> hostap AP itself, the delays are fine (1.7ms - 11b mode). >> >> Here is my setup: >> >> client 1 ------------ ath hostap AP ------------- client 2 >> >> I have tried various configs and combinations, all with the same result: >> - hostap in 11g mode >> - hostap in 11b mode >> - ath clients >> - wi (lucent) clients >> - hostap with 5.3-BETA6 , HAL 0.9.6.3 >> - hostap with 5.3-BETA7 , HAL 0.9.6.3 >> - hostap with 5.3-BETA4 , HAL 0.9.11.6 , net80211+ath-20040818.patch >> - Senao 5354 minipci with atheros 5212 >> - Dlink DWL-AG520 with atheros 5212 >> - hostap with wi (Intersil - actiontec minipci) - works fine, no problem >> >> If I add another subnet (alias) to the ath interface and I route >> between the clients then it works fine. The problem is only between >> clients on the same subnet working through an ath hostap AP. Is >> bridging done inside the HAL ? >> >> Are there any one else using an ath hostap AP that can do a ping test >> between two clients to see if they get the same results. > > > Packets between wireless clients are bridged entirely in the net80211 > layer and should have less overhead than going through the bridge. > You are likely seeing tx retransmits related to the incorrect 11g > implementation in -current. Try running a 3rd station to sniff the > traffic. > > Sam > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > >