From: Johannes Berg <johannes@sipsolutions.net>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: Dan Williams <dcbw@redhat.com>, wwguy <wey-yi.w.guy@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: 2.6.38-rc7, iwlagn warning
Date: Tue, 08 Mar 2011 20:39:15 +0100 [thread overview]
Message-ID: <1299613155.3734.8.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTinJ3RU+6asQrOmKdW6-EkL8Jw2BXOTuZKqw_Vdu@mail.gmail.com>
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.
In any case, I'll look more into the warning, but even if I fix the
warning it won't really work any better for you until you manage to fix
the dnsmasq thing -- maybe file a bug against Ubuntu.
johannes
next prev parent reply other threads:[~2011-03-08 19:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 3:27 2.6.38-rc7, iwlagn crash Mathias Burén
2011-03-04 13:46 ` John W. Linville
2011-03-04 15:17 ` wwguy
2011-03-04 22:23 ` Mathias Burén
2011-03-05 3:45 ` Mathias Burén
2011-03-05 9:45 ` Mathias Burén
2011-03-05 9:54 ` Mathias Burén
2011-03-05 14:09 ` Johannes Berg
2011-03-05 23:45 ` Mathias Burén
2011-03-08 15:17 ` 2.6.38-rc7, iwlagn warning Johannes Berg
2011-03-08 16:22 ` Mathias Burén
2011-03-08 16:26 ` Johannes Berg
2011-03-08 16:45 ` Johannes Berg
2011-03-08 17:13 ` Mathias Burén
2011-03-08 17:18 ` Johannes Berg
2011-03-08 17:54 ` Mathias Burén
2011-03-08 18:16 ` Dan Williams
2011-03-08 19:10 ` Mathias Burén
2011-03-08 19:39 ` Johannes Berg [this message]
2011-03-08 19:40 ` Johannes Berg
2011-03-08 20:05 ` Dan Williams
2011-03-08 17:27 ` Johannes Berg
2011-03-08 15:18 ` 2.6.38-rc7, iwlagn crash Johannes Berg
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=1299613155.3734.8.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.buren@gmail.com \
--cc=wey-yi.w.guy@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.