> I'm not too familiar with avahi but I guess the .local is some kind of
> multicast thing... does this help?
>
> I can't think of a good reason to zero the mcast hash after a reset.
>
> diff --git a/drivers/net/wireless/ath/ath5k/base.c
> b/drivers/net/wireless/ath/ath5k/base.c index 1287ded..1e6e
On Mon, Nov 02, 2009 at 07:09:29PM -0500, CSights wrote:
> Hello,
> I'm having a problem with the ath5k module found in kernel 2.6.31.5 and
> accessing ".local" addresses on the network.
I'm not too familiar with avahi but I guess the .local is some kind of
multicast thing... does this help
Some new observations:
If I restart avahi the .local computers are once again accessable
(pingable).
If I ping "nimby.local" (the computer with ath5k wireless card) it will
work
for about 120 seconds (aka 2 minutes). Then "nimby.local" is no longer
resolvable to a IP a
Hello,
(Sorry wireless mailing list readers, just discovered ath5k had its own
mailing list!)
I'm having a problem with the ath5k module found in kernel 2.6.31.5 and
accessing ".local" addresses on the network.
What I've observed so far is that when I first boot the comput
Hi,
I have been browsing the driver code for some backoff related stuff.
Specifically, I am looking for a way to count the number of backoffs on
AR5212 based cards. I have seen a backoff count register for AR5210 but
cannot find any such thing for AR5212.
Also, what is "Backoff persistence factor
