Linux wireless drivers development
 help / color / mirror / Atom feed
From: Hin-Tak Leung <htl10@users.sourceforge.net>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	Attila Fazekas <turul64@gmail.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Herton Ronaldo Krzesinski <herton@canonical.com>
Subject: Re: [PATCH] rtl8187: Add Ad-hoc mode
Date: Thu, 23 Feb 2012 02:27:20 +0000 (GMT)	[thread overview]
Message-ID: <1329964040.38655.YahooMailClassic@web29503.mail.ird.yahoo.com> (raw)
In-Reply-To: <CAGRGNgXOjKZQqF_JrAA0hyqcsn8TZWHd9OysqOMrE5_JrmnRjA@mail.gmail.com>

--- On Thu, 23/2/12, Julian Calaby <julian.calaby@gmail.com> wrote:

> If it's anything like how it works on Ubuntu, when you start
> an Ad-Hoc
> network with NetworkManager, it chooses an IP range based on
> some
> internal logic (usually in the 10.0.0.0/8 private network)
> sets it's
> IP to something sensible then starts a DHCP server for
> everyone else
> on the network, so everyone should get a valid IP.

Thanks - that would make sense. (I have no experience setting up an ad-hoc network).

OTOH, just so that we have established the basics - I would shutdown networkmanger/wpa_supplicant and do things manually if I were to test prototype driver patches though. There are many reasons why ad-hoc mode itself might work but one cannot ping, other than the patch not working or the hardware not behaving. The latter is in the tcp/ip layer and quite a lot higher than the wifi mac layer - if one had iptables/netfilter blocking icmp echo, for example. I'd probably just look at the packet stats from iwconfig/ifconfig, and may be firing up wireshark. It is up to Attila to show that it does work, and Larry to show that it does not :-).

Hin-Tak

      parent reply	other threads:[~2012-02-23  2:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19 19:54 [PATCH] rtl8187: Add Ad-hoc mode Attila Fazekas
2012-02-19 21:19 ` Larry Finger
2012-02-19 23:17   ` Hin-Tak Leung
2012-02-21 17:44     ` Attila Fazekas
2012-02-22 21:51       ` Hin-Tak Leung
2012-02-22 23:35         ` Larry Finger
2012-02-23  0:44           ` Hin-Tak Leung
2012-02-23  0:59             ` Julian Calaby
2012-02-23  2:17               ` Larry Finger
2012-02-23  2:27               ` Hin-Tak Leung [this message]

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=1329964040.38655.YahooMailClassic@web29503.mail.ird.yahoo.com \
    --to=htl10@users.sourceforge.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=herton@canonical.com \
    --cc=julian.calaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=turul64@gmail.com \
    /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