All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Thiele <karme@karme.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] mdns/avahi troubles
Date: Fri, 04 Dec 2015 14:17:45 +0100	[thread overview]
Message-ID: <87610eqrnq.fsf@karme.de> (raw)
In-Reply-To: <56615349.9000801@green-communications.fr> (Nicolas Cavallari's message of "Fri, 4 Dec 2015 09:48:09 +0100")

Nicolas Cavallari <Nicolas.Cavallari@green-communications.fr> writes:

> On 03/12/2015 21:40, Jens Thiele wrote:
>> Hi,
>> 
>> sometimes (when the wlan stick was idle for some time?) I see no answers
>> to mdns requests => mdns lookup fails.
>> 
>> Can't provide a lot of detail yet, but maybe this is a old known bug
>> already fixed?
>
> This is most likely a problem with Avahi; Its latest release is 3 year
> old and it has many known issues.  At least one of them can cause it
> to not publish DNS records so it will not answer queries for them, and
> it is still not fixed in Avahi's Git yet.
>
> If a packet dump on godlady does not show replies, then Avahi didn't
> reply and ath9k is not to blame.

with a different stick (Ralink Technology, Corp. RT5370 Wireless
Adapter) it seems to work just fine
=> imho unlikely avahi's fault here

regarding the traffic dump i was very unclear:
the dump is from the requesting host, and yes i also should also take a
dump on the host that is supposed to answer

jens

PS: i have seen similar problems with other sticks - often a workaround
was to disable power saving

-- 
Prisirah - Building digital photo frames for family and friends using
open-source hardware. http://karme.de/prisirah/

      reply	other threads:[~2015-12-04 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-03 20:40 [ath9k-devel] mdns/avahi troubles Jens Thiele
2015-12-04  8:48 ` Nicolas Cavallari
2015-12-04 13:17   ` Jens Thiele [this message]

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=87610eqrnq.fsf@karme.de \
    --to=karme@karme.de \
    --cc=ath9k-devel@lists.ath9k.org \
    /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.