From: moony <moony@mindsnack.net>
To: linux-wireless@vger.kernel.org
Subject: Re: carl9170: Problems setting up Virtual Interface
Date: Wed, 14 Aug 2013 09:32:57 +0000 (UTC) [thread overview]
Message-ID: <loom.20130814T112720-982@post.gmane.org> (raw)
In-Reply-To: CAMJnVwm4Xp87pF7PHLP7vVqF-LYzsgeso7ZPzPwOC_39mwP_Kw@mail.gmail.com
Alex <alex9434@...> writes:
>
> Great! I now get an additional interface:
> wlan1-wlan0 Link encap:Ethernet HWaddr <deleted>
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Hi Alex,
did you get this to work? I'm using the same driver and procedure, but when
I try to bring up the second interface (with ifup wifi1), I get the error
device or resource busy... The first always comes up.
I don't know if vif is enabled by default on the kernelmodule. I tried to
compile it by myself (there is an option for the number of vif, and the
default is 1), but stuck on errors or missing dependencies, yet.
Best regards,
moony
next prev parent reply other threads:[~2013-08-14 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 19:46 carl9170: Problems setting up Virtual Interface Alex
[not found] ` <201107042202.27366.chunkeey@googlemail.com>
2011-07-04 20:11 ` Alex
2011-07-04 20:23 ` Christian Lamparter
2011-07-04 20:29 ` Alex
2011-07-04 20:42 ` Christian Lamparter
2011-07-04 20:54 ` Alex
2011-07-04 21:06 ` Christian Lamparter
[not found] ` <CAMJnVwnGKH7CtxuwnTTjp+747cwLpNtp=u8VE2QAahGY9Q813Q@mail.gmail.com>
2011-07-04 21:42 ` Christian Lamparter
2013-08-14 9:32 ` moony [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-04 20:08 Christian Lamparter
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=loom.20130814T112720-982@post.gmane.org \
--to=moony@mindsnack.net \
--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).