Re: kern/143622: [pfil] [patch] unlock pfil lock while calling firewall hooks

The following reply was made to PR kern/143622; it has been noted by GNATS. From: Max Laier To: bug-follo...@freebsd.org, gleb.kurt...@gmail.com Cc: Subject: Re: kern/143622: [pfil] [patch] unlock pfil lock while calling firewall hooks Date: Mon, 8 Feb 2010 02:55:41 +0100 Please no. The rm

Re: HT rate set in net80211 not changeable for STA

Alexander Egorenkov wrote: On Sat, Feb 6, 2010 at 10:52 PM, Sam Leffler > wrote: The advertised rate set should be initially set according to the capabilities of the device. There were no devices > 2x2 when I wrote the code so MCS15 is the max. To support

Re: kern/143627: [ieee80211] [panic] A bug in ht_send_action_ba_addba causes net80211 to send malformed ADDBA response frames

Old Synopsis: [ieee80211] A bug in ht_send_action_ba_addba causes net80211 to send malformed ADDBA response frames New Synopsis: [ieee80211] [panic] A bug in ht_send_action_ba_addba causes net80211 to send malformed ADDBA response frames Responsible-Changed-From-To: freebsd-bugs->freebsd-net Res

Re: HT rate set in net80211 not changeable for STA

On 7 Feb 2010, at 08:41, Alexander Egorenkov wrote: > But my device is a 2T2R device and supports MCS32 (HT duplicate mode). I wouldn't worry about MCS 32 for now. If you can get your device to do MCS 15, you're probably in a good shape already. MCS 32 would just come as a bonus and I'm not su

Re: How does rpc.lockd know where to send a request

Julian Elischer wrote: > > try swapping the addresses on the interface. The original posting said that 10.0.0.99 is an address assigned to a CARP interface, not an alias assigned to an ethernet interface. As such, both are primary addresses on their respective interfaces, so there is nothing to

Re: HT rate set in net80211 not changeable for STA

On Sat, Feb 6, 2010 at 10:52 PM, Sam Leffler wrote: > The advertised rate set should be initially set according to the > capabilities of the device. There were no devices > 2x2 when I wrote the > code so MCS15 is the max. To support such devices you need to do more than > just grow the rateset.