OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Workaround For Kismet And Skb Bug Invalid Truesize
zthird
post Jan 25 2009, 03:01 PM
Post #1





Group: Members
Posts: 22
Joined: 13-May 06
Member No.: 9,851



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.


Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 17th December 2014 - 08:03 PM