From: Bob Beers <bbeers@ieee.org>
To: bridge@lists.osdl.org
Subject: [Bridge] Re: bridge wlan-eth
Date: Tue, 20 Jul 2004 09:52:05 -0400 [thread overview]
Message-ID: <40FD2385.7000601@ieee.org> (raw)
In-Reply-To: <40CEF596.1090000@ieee.org>
Bob Beers wrote:
apparently a bunch of nonsense ...
Sorry for the noise on the list, but let me close this thread,
just incase someone hits it in the archives during a search.
The hardware I was testing on had (unknown to me) changed, for the worse.
I can't say exactly what in the hardware was causing the problem, but
I'm not using it any more.
The newer firmware does support bridging between eth and wlan just fine.
--
Bob Beers
MIEEE 2415966
prev parent reply other threads:[~2004-07-20 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 13:11 [Bridge] bridge wlan-eth Bob Beers
2004-07-20 13:52 ` Bob Beers [this message]
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=40FD2385.7000601@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox