Workaround For Kismet And Skb Bug Invalid Truesize Options

[zthird]

when running kismet the console interface is bombed with messages such as
"SKB BUG: Invalid truesize (320) len=222, sizeof(sk_buff)=160"
networks are still detected.
run
dmesg -n2;kismet
to launch kismet and the errors will disapear (be hidden)

note:
dmesg -n
-nlevel
Set the level at which logging of messages is done to the con-
sole. For example, -n 1 prevents all messages, expect panic
messages, from appearing on the console. All levels of messages
are still written to /proc/kmsg, so syslogd(8) can still be used
to control exactly where kernel messages appear. When the -n
option is used, dmesg will not print or clear the kernel ring
buffer.