Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 19 Aug 2007 10:42:05 -0300
From:      Nenhum_de_Nos <matheusber@gmail.com>
To:        "Ian FREISLICH" <ianf@clue.co.za>
Cc:        freebsd-current@freebsd.org
Subject:   Re: hostapd and atheros - anyone else with dropping connections ?!
Message-ID:  <4956a5e50708190642t284f5142r137a85b77f4bd2c4@mail.gmail.com>
In-Reply-To: <4956a5e50708190624t4168ed02nbbc25f107cde94fc@mail.gmail.com>
References:  <matheusber@gmail.com> <4956a5e50708081849s393be47bv931310df0e59fb66@mail.gmail.com> <E1IJAnd-0000Tn-Ra@clue.co.za> <4956a5e50708190624t4168ed02nbbc25f107cde94fc@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 8/19/07, Nenhum_de_Nos <matheusber@gmail.com> wrote:
> On 8/9/07, Ian FREISLICH <ianf@clue.co.za> wrote:
> > Nenhum_de_Nos wrote:
> > > I have a wifi atheros card:
> > >
> > > ath0@pci0:10:0: class=0x020000 card=0x3a131186 chip=0x0013168c rev=0x01 hdr=0
> > x00
> > >     vendor     = 'Atheros Communications Inc.'
> > >     device     = 'AR5212, AR5213 802.11a/b/g Wireless Adapter'
> > >     class      = network
> > >     subclass   = ethernet
> > >
> > > and an hostapd AP.
> > >
> > > from time to time, I need to restart hostapd. and this time is not long.
> > >
> > > I'll update now and try again.
> > >
> > > if anyone is having the same issue, please say :)
> >
> > I'm having a similar issue on similar and more recent hardware (5212
> > and 5006), but not with hostap.  Have you tried 'arp -d -a' on
> > either or both of the hosts?  I find this fixes my disappearing
> > wireless connectivity.
> >
> > Ian
> >
> > --
> > Ian Freislich
>
> no good for me, I waited till now to see the issue and test. when I
> did the "arp -d -a", I got no wifi connection back, and as bonus, I
> cant get in the ap box using ssh, just now when I had direct access to
> it(monitor and keyboard directly attached). Trying to kill arp -d -a,
> that is still running, doesnt work even when killall -9 is used.
>
> I tryed to update my current machine, but it keeps killing the gcc
> process, as there is not ram enough for everyone, and dmesg says it
> has been killed. another weird issue, dmesg keeps saying:
>
> ath0: ath_rx_proc: no mbuf!
>
> my present dmesg has just this entries ...
>
> I'll try to update current, but this is not easy as usually was/should be. :(
>
> this is a Athlon XP 1700+ 512MB PC2100 running -CURRENT from July 29.
> I have mldonkey and Folding at home running, but before this current,
> I could do all three jobs just fine.
>
> I'll csup again and let hust gcc be alone,
>
> if anyone has any hints,
>
> thanks
>
> matheus

just a small update, every program I run on it begins running, but
never ends. even control+C works ... well, at least csup now is in
this way, and although I can ping any other host, I cant ssh anyone.
I'll reboot and try again.

matheus

-- 
We will call you cygnus,
The God of balance you shall be



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4956a5e50708190642t284f5142r137a85b77f4bd2c4>