From: Marcel Holtmann <marcel@holtmann.org>
To: Dan Williams <dcbw@redhat.com>
Cc: Arend van Spriel <arend@broadcom.com>,
Erwin Van de Velde <erwin.vandevelde@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Florian Fainelli <florian@openwrt.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Master mode support in iwlagn?
Date: Thu, 31 May 2012 18:52:04 +0200 [thread overview]
Message-ID: <1338483124.1817.53.camel@aeonflux> (raw)
In-Reply-To: <1338474236.2242.1.camel@dcbw.foobar.com>
Hi Dan,
> > > I have one ethernet connection and want to share that connection over
> > > wireless, preferably in AP mode although I guess ad hoc mode is possible too.
> > > Just not sure if NetworkManager supports that.
> >
> > NetworkManager does support ad-hoc, but your hardware need to support
> > beacon transmission for that as well. You could consider buying an AP.
> > They are not that expensive ;-)
>
> The problem with Ad-Hoc as "hotspot" is that many devices like Android
> phones simply ignore adhoc networks due to security issues (as stupid as
> that may be, since anyone can set up an AP-mode network too). Which is
> why real AP mode is nice, but clearly not all wifi hardware is going to
> support it.
the security issue is the missing proper encryption for IBSS networks.
Even while in theory you can have RSN, but who is really supporting this
on the other end.
For example ConnMan ignores IBSS networks as well for the exact above
reason. And it only provides Tethering via AP mode with RSN. If the
hardware does not support it, then you can not use Tethering.
We have enough crappy Windows machines and printers trying to play IBSS
tricks all the time. We do not need any extra ones ;)
Regards
Marcel
next prev parent reply other threads:[~2012-05-31 16:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 12:09 Master mode support in iwlagn? Erwin Van de Velde
2012-05-30 12:31 ` Johannes Berg
2012-05-30 15:02 ` Erwin Van de Velde
2012-05-30 22:32 ` Dan Williams
2012-05-31 7:40 ` Johannes Berg
2012-05-31 9:03 ` Erwin Van de Velde
2012-05-31 9:09 ` Johannes Berg
2012-05-31 9:20 ` Florian Fainelli
2012-05-31 9:57 ` Erwin Van de Velde
2012-05-31 12:01 ` Arend van Spriel
2012-05-31 12:16 ` Erwin Van de Velde
2012-05-31 12:26 ` Arend van Spriel
2012-05-31 12:32 ` Johannes Berg
2012-05-31 14:23 ` Dan Williams
2012-05-31 16:52 ` Marcel Holtmann [this message]
2012-05-31 17:00 ` Johannes Berg
2012-05-31 20:00 ` Marcel Holtmann
2012-05-31 18:22 ` Erwin Van de Velde
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=1338483124.1817.53.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=arend@broadcom.com \
--cc=dcbw@redhat.com \
--cc=erwin.vandevelde@gmail.com \
--cc=florian@openwrt.org \
--cc=johannes@sipsolutions.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).