Linux wireless drivers development
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: htl10@users.sourceforge.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: Wed, 22 Feb 2012 20:17:10 -0600	[thread overview]
Message-ID: <4F45A1A6.1040500@lwfinger.net> (raw)
In-Reply-To: <CAGRGNgXOjKZQqF_JrAA0hyqcsn8TZWHd9OysqOMrE5_JrmnRjA@mail.gmail.com>

On 02/22/2012 06:59 PM, Julian Calaby wrote:
> Hi,
>
> On Thu, Feb 23, 2012 at 11:44, Hin-Tak Leung
> <htl10@users.sourceforge.net>  wrote:
>> --- On Wed, 22/2/12, Larry Finger<Larry.Finger@lwfinger.net>  wrote:
>>> I fixed and tested your patch. With it, I certainly see the
>>> beacons and I was
>>> able to use NetworkManager to connect once. However, I was
>>> never able to ping
>>> from either end of the network to the other.
>>
>> Do you need something manual set-up like "ifconfig wlan1 192.168.0.1" for one box and "ifconfig wlan1 192.168.0.2" for the other box in the IP layer to work? I haven't quite got my head around this one - how network manager agrees for each for go into a private tcp/ip network, given there are three(?) private ranges to use, and setting up host names, and what ip adresses to assign... and since there is no dns for a network of two, it would have to ping by ip address?
>
> 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.

Actually, I was assigning the IP for both ends and not using DHCP. My test 
network was a trivial one that was not connected to the outside world - only two 
isolated computers that should have been talking to each other. I expected a 
wireless NULL cable.

I could see the iwconfig from each end being part of the cell and each end had 
an IP address, but no ping data flowed between them.

Larry




  reply	other threads:[~2012-02-23  2:17 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 [this message]
2012-02-23  2:27               ` Hin-Tak Leung

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=4F45A1A6.1040500@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=herton@canonical.com \
    --cc=htl10@users.sourceforge.net \
    --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