On Sat, Mar 21, 2009 at 3:46 AM, Bjoern A. Zeeb
wrote:
> On Fri, 20 Mar 2009, Stefan Bethke wrote:
>
>> Am 20.03.2009 um 19:51 schrieb Kevin Downey:
>>
>>> I did not notice a heads up about this, but recently (maybe in the
>>> last few weeks?) wlan devices on
I did not notice a heads up about this, but recently (maybe in the
last few weeks?) wlan devices on -CURRENT no longer show information
like what ssid they are associated with. How can I find this
information now?
this what the current output looks like:
wlan0: flags=8843 metric 0 mtu 1500
ethe
On Fri, Sep 5, 2008 at 7:43 AM, Milan Obuch <[EMAIL PROTECTED]> wrote:
> [ snip ]
> Could anybody comment on wireless interface?
I could not get the internal wifi to work with ndis wrapper. It
appears that using the rtw driver netbsd, openbsd, and dragonflybsd
all support this chipset. I found a (
On Jan 25, 2008 7:41 AM, Yousif Hassan <[EMAIL PROTECTED]> wrote:
> Hi Pyun YongHyeon,
>
> First, I'd like to say thank you for sending this and trying to resolve
> my (and others') problems with bfe driver.
>
> First the good news - your patch appears to solve nearly all of the
> issues I've disco
On 1/15/07, Sam Leffler <[EMAIL PROTECTED]> wrote:
John Nielsen wrote:
> On Monday 15 January 2007 15:54, Lars Stokholm wrote:
>> John Nielsen wrote:
>>> On Monday 15 January 2007 12:54, Lars Stokholm wrote:
Hi, I hope someone can help me with this, before I go mad (no pun
intended.) :)
On 8/21/06, Pat Lashley <[EMAIL PROTECTED]> wrote:
> > Actually, that is IPv4 Link Local Addressing. Zeroconfig includes
that,
> > Multicast DNS, Service Discovery and anything else that removes the
need
> > for manual configuration.
>
> Yeah, I actually know that. It's just that I've developed
dhclient also is behaving erratically.
ov 9 22:34:59 zifnab kernel: ath0: link state changed to DOWN
Nov 9 22:35:00 zifnab /usr/sbin/cron[26924]: (root) CMD (/usr/libexec/atrun)
Nov 9 22:35:01 zifnab dhclient[24653]: connection closed
Nov 9 22:35:01 zifnab kernel: Nov 9 22:35:01 zifnab dhclient[246
ath0: mem 0xe001-0xe001 irq 10 at device 9.0 on pci0
ath0: Ethernet address: 00:0f:3d:ae:ad:b8
ath0: mac 5.9 phy 4.3 radio 4.6
when I use wpa_supplicant and dhclient the card ends up in a loop scanning
for aps, and everyone in awhile will associate with my ap, then a minute or
so later it
On 8/10/05, Sam Leffler <[EMAIL PROTECTED]> wrote:
> Giovanni P. Tirloni wrote:
> > Sam Leffler wrote:
> >
> >> Kevin Downey wrote:
> >>
> >>> I am running a generic kernel with all the debugging knobs.
> >>> if I use BitTorrent
I am running a generic kernel with all the debugging knobs.
if I use BitTorrent or Gnutella in X the computer reboots after a few minutes.
>From the console it drops into the debugger deal. But will not give me
a crash dump.
Under the assumption that something was wrong with the ath driver I
tried
FreeBSD zifnab 6.0-BETA1 FreeBSD 6.0-BETA1 #3: Sat Jul 23 00:11:23 PDT
2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SEE_NO_EVIL i386
ath0: mem 0xe401-0xe401 irq 11 at device 8.0 on pci0
ath0: Ethernet address: 00:0f:3d:ae:ad:b8
ath0: mac 5.9 phy 4.3 radio 4.6
while trying to transfer
Awesome. I have been thinking about tracking current anyway. Thanks a bundle.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
I have a dlink card that uses the ath0 driver. a DLW520. And when a
try to connect to an AP I get an error in dmesg "ath: association
failed (reason 25)" followed by the BSSID of the AP. Is there a list
of "reasons" somewhere? I have tried on an open AP a closed AP with
WEP w/o WEP and I always ge
13 matches
Mail list logo
