From: Jouni Malinen <j@w1.fi>
To: Bjarke Istrup Pedersen <gurligebis@gentoo.org>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Problem with bridges and wireless NIC's
Date: Mon, 1 Mar 2010 09:59:53 +0200 [thread overview]
Message-ID: <20100301075953.GA32038@jm.kir.nu> (raw)
In-Reply-To: <9c30dffe1002281458w5705378fj52f36c5d352593fb@mail.gmail.com>
On Sun, Feb 28, 2010 at 11:58:10PM +0100, Bjarke Istrup Pedersen wrote:
> There is a problem when trying to create a bridge containing a normal
> NIC and a wireless NIC, and using hostapd.
>
> The problem is, that it is not possible to create a bridge containing
> a wireless NIC, if it hasn't been setup first.
>
> Does anyone have a solution for this?
How about first creating the br0, then starting hostapd, and finally
adding wlan0 into br0?
> (The commit that introduced this problem is
> ad4bb6f8883a13bb0f65b194dae36c62a02ac779 , reverting it solves the
> problem).
I don't know whether I would call that a solution, but well..
> For more info, please have a look at this bug report:
> http://bugs.gentoo.org/show_bug.cgi?id=298824
I'm not sure whether I understood the description correctly, but this
sounds like a limitation in the way the network setup is done. Forcing
br0 to be created with wlan0 before wlan0 has been configured is not
going to work. I would consider removing wlan0 from the static
configuration of br0 and just creating br0 with eth0 with the setup
scripts and allowing hostapd to add wlan0 into br0 once the interface
has been configured properly (support for this was added in hostapd
0.7.1).
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2010-03-01 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 22:58 Problem with bridges and wireless NIC's Bjarke Istrup Pedersen
2010-03-01 7:59 ` Jouni Malinen [this message]
2010-03-01 8:12 ` Bjarke Istrup Pedersen
2010-03-01 10:53 ` Jouni Malinen
2010-03-01 11:40 ` Bjarke Istrup Pedersen
2010-03-01 13:18 ` Jouni Malinen
2010-03-01 23:14 ` Bjarke Istrup Pedersen
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=20100301075953.GA32038@jm.kir.nu \
--to=j@w1.fi \
--cc=gurligebis@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).