On Tue, 2011-03-08 at 20:39 +0100, Johannes Berg wrote: > On Tue, 2011-03-08 at 19:10 +0000, Mathias BurÃn wrote: > > > > Could you also grab /var/log/daemon.log or /var/log/NetworkManager.log, > > > whichever one exists? And just to make sure, when this problem > > > happens, there is only one wpa_supplicant running at the time, right? > > > Is something like wicd also running? > > > > > > The logs there look like something external is telling the supplicant to > > > disassociate, which could be NM or some other tool, but NM should not be > > > exhibiting this behavior if NM itself was used to start the adhoc > > > network. > > > dameon.log http://www.2shared.com/file/9ntZ37Q9/daemon.html > > > > I think the problem is Ubuntu-related, I can see error messages about > > dnsmasq (which NetworkManager uses for its DHCP purposes, right). I > > set the phone to static IPs, then suddenly the whole thing started > > working. No warning in dmesg... > > Yeah -- if you configure /etc/dnsmasq.conf to not listen on all > interfaces, or you just disable it, then it should all work. NM should also not just loop continuously trying to reactivate the adhoc connection when it fails. Maybe a few times, but certainly not forever. Dan -- 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
