ath driver (Linksys WMP110 RangePlus) ar5416

2008-11-05 Thread Jason J. Hellenthal
Anyone know if the Linksys WMP110 RangePlus support will be added to 7-stable. I would rather use a native driver for this card for more features but the ndis driver seems to be working great for a couple of weeks now with no flaw. This is what the device reports in pciconf. [EMAIL PROTECTED]:1

Re: kern/128598: [bluetooth] WARNING: attempt to net_add_domain(bluetooth) after domainfinalize()

2008-11-05 Thread pluknet
2008/11/5 <[EMAIL PROTECTED]>: > Old Synopsis: WARNING: attempt to net_add_domain(bluetooth) after > domainfinalize() > New Synopsis: [bluetooth] WARNING: attempt to net_add_domain(bluetooth) after > domainfinalize() > > Responsible-Changed-From-To: freebsd-bugs->freebsd-net > Responsible-Change

Re: bin/128602: [an] wpa_supplicant(8) crashes with an(4)

2008-11-05 Thread linimon
Old Synopsis: wpa_supplicant crashes with an(4) New Synopsis: [an] wpa_supplicant(8) crashes with an(4) Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Nov 5 18:26:44 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). htt

Re: kern/128598: [bluetooth] WARNING: attempt to net_add_domain(bluetooth) after domainfinalize()

2008-11-05 Thread linimon
Old Synopsis: WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() New Synopsis: [bluetooth] WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed N

Probably typo in netintro(4) manpage

2008-11-05 Thread Ivo Vachkov
Hello all, I'm using FreeBSD CURRENT (as of 04 Nov 2008) and while reading netintro(4) i found something i think is typo. Near the end of the INTERFACE section there is an example: ... /* * Structure used in SIOCAIFCONF request. */ struct ifaliasreq { charifra

CARP performance tuning question.

2008-11-05 Thread pluknet
Hi. AT work we use device carp(4) under high load: The problem is that the server experiences a bad interactivity (from 70k states and very bad from 120-150k) i.e. when a network workload (and interrupts count) begin to increase. >From top(1): CPU states: 0.0% user, 0.0% nice, 0.4% system, 76