From: Morgan Read <mstuff@read.org.nz>
To: linux-wireless@vger.kernel.org
Cc: sgruszka@redhat.com
Subject: iwlegacy and bridging iwl3945...? (sort of)
Date: Sun, 04 Oct 2015 20:38:43 +0100 [thread overview]
Message-ID: <56118043.3080509@read.org.nz> (raw)
https://wireless.wiki.kernel.org/en/users/drivers/iwlegacy
('$ ethtool -i wlp16s0' says 'driver: iwl3945' but
https://wireless.wiki.kernel.org/en/users/drivers/iwl3945
links here
https://wireless.wiki.kernel.org/en/users/Drivers/iwlwifi
then here
https://wireless.wiki.kernel.org/en/users/drivers/iwlegacy
So, running fedora 21, I assume the above means my driver is iwlegacy)
Hello Folks,
I have a deceptively simply questions;
Will this iwlegacy driver driving iwl3945 hardware work as per this
How To here:
https://wiki.debian.org/BridgeNetworkConnections#Bridging_with_a_wireless_NIC
?
That How To provides (to a novice) a comprehensive explanation to the
problem of bridging a wireless connection that seems to be universal to
all wireless connections. But, there are other explanations of the
wireless bridging problem which make me suspicious it might not work...
Warning here:
http://www.linux-kvm.org/page/Networking#public_bridge
Explanation here:
http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge#It_doesn.27t_work_with_my_Wireless_card.21
So, can I expect to be able to bridge my 802.11 connection to work with
my KVM guests?
(I'm setting up an old laptop to run as a home server.)
Many thanks for your help.
Morgan.
--
Morgan Read
UNITED KINGDOM
<mailto:mstuffATreadDOTorgDOTnz>
Confused about DRM?
Get all the info you need at:
http://drm.info/
next reply other threads:[~2015-10-04 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 19:38 Morgan Read [this message]
2015-10-05 6:54 ` iwlegacy and bridging iwl3945...? (sort of) Johannes Berg
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=56118043.3080509@read.org.nz \
--to=mstuff@read.org.nz \
--cc=linux-wireless@vger.kernel.org \
--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).