From: Johannes Berg <johannes@sipsolutions.net>
To: Morgan Read <mstuff@read.org.nz>, linux-wireless@vger.kernel.org
Cc: sgruszka@redhat.com
Subject: Re: iwlegacy and bridging iwl3945...? (sort of)
Date: Mon, 05 Oct 2015 08:54:58 +0200 [thread overview]
Message-ID: <1444028098.1875.2.camel@sipsolutions.net> (raw)
In-Reply-To: <56118043.3080509@read.org.nz> (sfid-20151004_213850_404200_FF308D08)
On Sun, 2015-10-04 at 20:38 +0100, Morgan Read wrote:
>
> So, can I expect to be able to bridge my 802.11 connection to work
> with my KVM guests?
>
No, never over wireless, regardless of the driver.
(Unless you also control the software on the AP and can run openwrt or
such and use the Linux-specific 4-addr mode)
johannes
next prev parent reply other threads:[~2015-10-05 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 19:38 iwlegacy and bridging iwl3945...? (sort of) Morgan Read
2015-10-05 6:54 ` Johannes Berg [this message]
2015-10-07 7:16 ` Morgan Read
2015-10-07 7:34 ` Johannes Berg
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=1444028098.1875.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mstuff@read.org.nz \
--cc=sgruszka@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).