From: "Francois Barre" <francois.barre@gmail.com>
To: "Michael Buesch" <mb@bu3sch.de>
Cc: bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org,
"Alexander Tsvyashchenko" <lists@ndl.kiev.ua>
Subject: Re: [PATCH, RFT] bcm43xx: AccessPoint mode
Date: Wed, 28 Jun 2006 21:27:16 +0200 [thread overview]
Message-ID: <fd8d0180606281227m309b0fcr94bc42c4c5247000@mail.gmail.com> (raw)
In-Reply-To: <200606191107.34602.mb@bu3sch.de>
Hi all,
Sorry for answering years after the patch post, I didn't have time to
test this take2 patch before. I had a first look at it a couple of
days ago, but... you know, that was not my day.
> Well, it does not work 100%, but at least it's very promising.
> We are able to create a bssid and correctly send beacon frames out.
[...]
For my very own situation, that is :
- Apple Mini with a BCM 4306 (BigEndian)
- Linux/Win32 boxes with USB and PCMCIA wifi cards (mostly 802.11b usb
at the moment)
Current status is this one :
- master mode functionnal
- dhcp serving, good uptime
- no encryption, WEP or WPA of any kind tested yet
- a nice 1.2MB/s bandwidth (I'm testing with a 802.11b at client side,
and AFAIK, bcm43xx does not handle 802.11g yet, does it ?)
*BUT* a big issue : I got a per-connection hang-up at client side on
strong workloads, for both win32 and linux client side, with my usb
dongle (which is running ndiswrapper on *nux, sorry for that, I'm
ashamed of it, silly me, I know, but well... No choice, and the device
was given me free of charge so...).
Typical scenario is a ssh session on one hand and a ftp transfer on
the other. The ftp hangs, while the ssh session stays up and going.
I got no problem with the PCMCIA card (a rock-solid WG511T), on both
linux and win32.
Of course, the bcm43xx does not say anything about this (if it had
said so, I would have posted logs along with this complain), so my
conclusion would be :
Why on earth is this a per-connection issue ? where do I miss
something ? if I'm really missing packets on one connection, why is
the other one continuing to live ? I may have forgotten a subtle
detail of the TCP/IP behaviour here... Or may that be all about window
scaling and fragmentation ? I can not see anything else... I would at
least like to know what to test, as I'm a little bit confused here.
Yes, I'll try to dig around the ip window and timeout stuff by tonight...
Anyway, I would like to thank again and again Alexander and Michael
for the work done, that is really impressive. Great work !
Best regards,
F. B.
next prev parent reply other threads:[~2006-06-28 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 9:07 [PATCH, RFT] bcm43xx: AccessPoint mode Michael Buesch
2006-06-22 15:30 ` Jiri Benc
2006-06-22 19:08 ` Alexander Tsvyashchenko
2006-06-23 11:26 ` Jiri Benc
2006-06-23 18:19 ` hostapd patch for d80211 Jiri Benc
2006-06-23 21:13 ` Michael Buesch
2006-06-24 2:17 ` Jouni Malinen
2006-06-28 19:27 ` Francois Barre [this message]
2006-06-28 19:39 ` [PATCH, RFT] bcm43xx: AccessPoint mode Michael Buesch
2006-06-28 19:50 ` Francois Barre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fd8d0180606281227m309b0fcr94bc42c4c5247000@mail.gmail.com \
--to=francois.barre@gmail.com \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=lists@ndl.kiev.ua \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.