From: Bob Beers <bbeers@ieee.org>
To: bridge@lists.osdl.org
Cc: bbeers@ieee.org
Subject: [Bridge] bridge wlan-eth
Date: Tue, 15 Jun 2004 09:11:50 -0400 [thread overview]
Message-ID: <40CEF596.1090000@ieee.org> (raw)
Hi list,
I am not subscribed to this list, but I hope someone will
know the solution to my problem ...
I have checked the archives and there was a thread:
<http://lists.osdl.org/pipermail/bridge/2004-March/000224.html>
that did not really get resolved. I have discovered something
about this situation that I hope someone can shed more light on.
Using hostap driver in AP mode, with a netgear MA311 or
linksys WMP11, (both PCI), with older firmware
NIC: id=0x8013 v1.0.0
PRI: id=0x15 v1.0.7
STA: id=0x1f v1.3.6
bridge eth-wlan works great, but after "upgrading" to newer
firmware (to get essid hiding feature),
NIC: id=0x8013 v1.0.0
PRI: id=0x0015 v1.1.1
STA: id=0x001f v1.7.4
bridge no longer works, even though there is no apparent (to me)
indication of error.
Is there info somewhere that tells about what was "fixed" in
different firmware versions for prism chips, or better is there
some workaround in the bridge code that I don't yet know about
to overcome this issue?
I guess I will test all the firmware versions I can get onto
my cards and see where it broke, but if anyone already knows
where the problem really comes from, please let us all know.
Thanks,
-Bob
--
Bob Beers
MIEEE 2415966
next reply other threads:[~2004-06-15 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 13:11 Bob Beers [this message]
2004-07-20 13:52 ` [Bridge] Re: bridge wlan-eth Bob Beers
-- strict thread matches above, loose matches on Subject: below --
2004-03-17 17:13 [Bridge] " Christoph Kaminski
2004-03-17 17:34 ` Michael Renzmann
2004-03-17 17:40 ` Mark S. Mathews
2004-03-17 17:40 ` Stephen Hemminger
2004-03-17 18:00 ` Chris Shaw
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=40CEF596.1090000@ieee.org \
--to=bbeers@ieee.org \
--cc=bridge@lists.osdl.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.