From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: "Luis R. Rodriguez" <mcgrof-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Nick Kossifidis
<mickflemm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Georgy Berdyshev
<codingmaster-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: wireless netns work
Date: Thu, 18 Jun 2009 23:48:14 +0200 [thread overview]
Message-ID: <1245361694.6495.2.camel@johannes.local> (raw)
In-Reply-To: <43e72e890906181443g54269d1bm7ce24dcb46e7e921-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
On Thu, 2009-06-18 at 14:43 -0700, Luis R. Rodriguez wrote:
> For example, I see you used mac80211_hwsim and was able to use two
> wlan interfaces to talk to each other. This seems great for testing
> purposes but it remains unclear to me the advantage of testing with
> separate namespaces vs creating two wlan interfaces on one namespace
> with mac80211_hwsim.
You cannot ping within one namespace and have the packets actually flow
over the virtual 'air'.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-06-18 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 12:35 wireless netns work Johannes Berg
[not found] ` <1245328543.13790.31.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-06-18 12:55 ` Johannes Berg
2009-06-18 17:16 ` Nick Kossifidis
2009-06-18 21:43 ` Luis R. Rodriguez
[not found] ` <43e72e890906181443g54269d1bm7ce24dcb46e7e921-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-18 21:48 ` Johannes Berg [this message]
2009-06-18 22:04 ` Luis R. Rodriguez
[not found] ` <43e72e890906181504i3b48b1fbj88fe485890e5f1a0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-18 22:06 ` 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=1245361694.6495.2.camel@johannes.local \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=codingmaster-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mcgrof-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=mickflemm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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