--- On Thu, 23/2/12, Julian Calaby <julian.calaby@xxxxxxxxx> 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 -- 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
