Re[2]: New Atheros card: channel reset error [sorry for posting of not ready message]

2009-02-11 Thread Lev Serebryakov
Hello, Sam. You wrote 12 февраля 2009 г., 02:46:08: > So the driver is mis-mapping the channel and causing the hal to reject > the request. If I recall this causes scanning to stop on RELENG_7 so > you'll want to force this channel to not be requested by disabling > dynamic turbo mode. I can'

IPv6 autoconfiguration fails

2009-02-11 Thread Bruce Cran
[forwarding from curr...@] I recently reinstalled -current on my laptop and have started seeing IPv6 autoconfiguration failing. I have two interfaces re0 and ath0: re0 is plugged in and gets an address via DHCP while I'm not using wireless at the moment so ath0 remains unconfigured. However it s

Re: Support for IPv6 tables in ipfw?

2009-02-11 Thread Kevin Oberman
> From: Raffaele De Lorenzo > Date: Wed, 11 Feb 2009 23:50:34 +0100 > > Hi, > I developed with Luigi (as mentor) and Mariano Tortoriello the first > release of ipfw with ipv6 extension. If you and the FreeBSD Community > think that the tables functional is a good feature i can develop it >

Re: New Atheros card: channel reset error [sorry for posting of not ready message]

2009-02-11 Thread Sam Leffler
Your panic on card eject has been fixed in HEAD. That was one of the changes I hoped to backport to RELENG_7 after the hal is brought back. Sam Adam K Kirchhoff wrote: I get similar errors, but only when trying to connect to a particular wireless network (at work). I can connect to the on

Re: New Atheros card: channel reset error [sorry for posting of not ready message]

2009-02-11 Thread Sam Leffler
Lev Serebryakov wrote: Hello, Freebsd-net. I'm getting this error on every operation with new Atheros MiniPCI card: ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x490 hal flags 0x150), hal status 12 status 12 is: HAL_EINVAL = 12, /* Invalid parameter to f

Re: Support for IPv6 tables in ipfw?

2009-02-11 Thread Raffaele De Lorenzo
Hi, I developed with Luigi (as mentor) and Mariano Tortoriello the first release of ipfw with ipv6 extension. If you and the FreeBSD Community think that the tables functional is a good feature i can develop it for IPv6 protocol. Ciao Raffaele On 11/feb/09, at 23:34, Kevin Oberman wrote:

Support for IPv6 tables in ipfw?

2009-02-11 Thread Kevin Oberman
With all of Luigi's excellent work on ipfw, I'd like to request that someone familiar with the code look at implementing support for tables for IPv6. While the IPv6 support in IPFW is generally a bit less mature than IPv4, the one functional thing that is completely missing is tables. Having them w

Re: New Atheros card: channel reset error [sorry for posting of not ready message]

2009-02-11 Thread Adam K Kirchhoff
I get similar errors, but only when trying to connect to a particular wireless network (at work). I can connect to the one I have at home, and do not get any errors. I have opened up a pr about it: http://www.freebsd.org/cgi/query-pr.cgi?pr=131162 In my case, if I then remove the wireless card

New Atheros card: channel reset error

2009-02-11 Thread Lev Serebryakov
Hello, Freebsd-net. I'm getting this error on every operation with new Atheros MiniPCI card: ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x490 hal flags 0x150), hal status 12 What does it mean? Maybe, card is broken? -- // Black Lion AKA Lev Serebryakov _

New Atheros card: channel reset error [sorry for posting of not ready message]

2009-02-11 Thread Lev Serebryakov
Hello, Freebsd-net. I'm getting this error on every operation with new Atheros MiniPCI card: ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x490 hal flags 0x150), hal status 12 What does it mean? Maybe, card is broken? # pciconf -lv a...@pci0:0:17:0: class=0x02 card

Re: unsafe C in netgraph/pppoed.c

2009-02-11 Thread Kostik Belousov
On Tue, Feb 10, 2009 at 10:57:39PM +0100, Roman Divacky wrote: > hi > > > struct pppoe_tag { > u_int16_t tag_type; > u_int16_t tag_len; > char tag_data[]; > }__packed; > > struct pppoe_hdr{ > u_int8_t ver:4; > u_int8_t type:4; > u_int8_t code; >