ath0 timeout was "Re: (more) bugs fixed in -HEAD, AP mode is now mostly (again) stable!"

Vincent Hoffman vince at unsane.co.uk
Mon Mar 19 22:18:39 UTC 2012


On 19/03/2012 21:46, Adrian Chadd wrote:
> Oh, thankyou for reporting it! I'm glad you pointed this out to me.
>
> It really does highlight the need for better (any) driver/stack
> debugging and tracing code. Doing this with printf() and a lot of
> study is .. Not scalable.
>
> Let me know how iperf goes!
>
Sending from my FreeBSD server to my OSX laptop
jhary at ostracod $ iperf -c 10.10.10.242 -t 60
------------------------------------------------------------
Client connecting to 10.10.10.242, TCP port 5001
TCP window size: 32.5 KByte (default)
------------------------------------------------------------
[  3] local 10.10.10.1 port 57369 connected with 10.10.10.242 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-60.0 sec   154 MBytes  21.4 Mbits/sec



>From my laptop to the server
vhoffman at macbook
(22:14:45 <~>) 0 $ iperf -c 10.10.10.1 -t 60
------------------------------------------------------------
Client connecting to 10.10.10.1, TCP port 5001
TCP window size:  129 KByte (default)
------------------------------------------------------------
[  3] local 10.10.10.20 port 53111 connected with 10.10.10.1 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-60.1 sec   125 MBytes  17.4 Mbits/sec


I'm not sure sort of speed would be expected, I'll benchmark my laptop
against a server at work

Vince
>
> Adrian
>
>
>
> Sent from my Palm Pre on AT&T
>
> ------------------------------------------------------------------------
> On Mar 19, 2012 2:26 PM, Vincent Hoffman <vince at unsane.co.uk> wrote:
>
> On 19/03/2012 05:35, Adrian Chadd wrote:
> > Hi,
> >
> > Please try this patch:
> >
> >
> >
> > Adrian
> Well its not a scientific test but its survived iperf traffic and rsync
> traffic that was causing hangs before.
> I'll put it back in usage as it was with a SMP kernel and let you know
> if i do see any hangs in the future.
>
>
> Thanks for your work on this.
>
> Vince



More information about the freebsd-wireless mailing list