From: Morgan Read <mstuff@read.org.nz>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Cc: sgruszka@redhat.com
Subject: Re: iwlegacy and bridging iwl3945...? (sort of)
Date: Wed, 07 Oct 2015 08:16:26 +0100 [thread overview]
Message-ID: <5614C6CA.7060701@read.org.nz> (raw)
In-Reply-To: <1444028098.1875.2.camel@sipsolutions.net>
On 05/10/15 07:54, Johannes Berg wrote:
> On Sun, 2015-10-04 at 20:38 +0100, Morgan Read wrote:
>>
...
>
> (Unless you also control the software on the AP and can run openwrt or
> such and use the Linux-specific 4-addr mode)
>
Thanks for the follow up.
That's certainly a possibilty - I have in the past had Gargoyle on my
router but, I hadn't installed it on my present router yet because it
wasn't supported but, I see as of May the tplink c7 archer is
supported... Perhaps it's time for an upgrade.
However, before I go down that route are any of the options for bonding,
which again seem as if they would work, actually a reality?
http://www.codekoala.com/posts/bonding-eth0-and-wlan0-arch-linux/
https://docs.fedoraproject.org/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Network_Bonding.html
Then would the example at the bottom of this page work:
https://docs.fedoraproject.org/en-US/Fedora/18/html/System_Administrators_Guide/s2-networkscripts-interfaces_network-bridge.html
That is, bridging the bonded interfaces?
This is the most appropriate set up for my use.
Many thanks
M
--
Morgan Read
UNITED KINGDOM
<mailto:mstuffATreadDOTorgDOTnz>
Confused about DRM?
Get all the info you need at:
http://drm.info/
next prev parent reply other threads:[~2015-10-07 7:16 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
2015-10-07 7:16 ` Morgan Read [this message]
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=5614C6CA.7060701@read.org.nz \
--to=mstuff@read.org.nz \
--cc=johannes@sipsolutions.net \
--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).