From: Johannes Berg <johannes@sipsolutions.net>
To: Daniel Wagner <wagi@monom.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: No local loopback for mac80211_hwsim test setup
Date: Fri, 03 Apr 2009 21:30:32 +0200 [thread overview]
Message-ID: <1238787032.11352.1.camel@johannes.local> (raw)
In-Reply-To: <20090403123822.GA26100@toronto053.server4you.de> (sfid-20090403_150647_912363_CB6A5CE6)
[-- Attachment #1: Type: text/plain, Size: 225 bytes --]
On Fri, 2009-04-03 at 14:38 +0200, Daniel Wagner wrote:
> So my question is this possible what I'd like to do? If so, what's the
> trick to get it working?
It's not possible locally, unfortunately, afaik.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-04-03 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 12:38 No local loopback for mac80211_hwsim test setup Daniel Wagner
2009-04-03 19:30 ` Johannes Berg [this message]
[not found] ` <1238787032.11352.1.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-04-07 19:07 ` Daniel Wagner
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=1238787032.11352.1.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wagi@monom.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).