Coleman Kane wrote: > If you are looking for a reliable test case, this might be it for you, > but I think you need a wlan interface to test it with: > * Install net/avahi from ports > * Set avahi_daemon_enable="YES" in rc.conf > * Configure VAP params for wlan0 card in rc.conf > * Log in and run "dhclient wlan0" to trigger the panic > > Actually I was able to panic the kernel right away with the 802.11 code, just by joining a multicast group with mtest(8) on the wlan interface. i.e. # mtest j 224.0.0.2 192.168.x.x -> boom I believe I've found the symptom, but the root cause I don't fully understand. Sam indicated that the VAP code is using ifma's in some nested way between the ifnets which comprise the VAP's member interfaces. A workaround is pending.... cheers BMSReceived on Tue Mar 17 2009 - 12:41:58 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:44 UTC