On 02/22/2012 06:59 PM, Julian Calaby wrote:
Hi,
On Thu, Feb 23, 2012 at 11:44, Hin-Tak Leung
<htl10@xxxxxxxxxxxxxxxxxxxxx> wrote:
--- On Wed, 22/2/12, Larry Finger<Larry.Finger@xxxxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
