Re: Kernel logging firestarter events to syslog and console

2006-03-31 Thread HEHO
Anthony Simonelli a écrit, le 31.03.2006 05:27 : > Mar 27 21:25:25 debian kernel: ABORTED IN=wlan0 OUT= > MAC=00:0f:66:a1:89:28:00:12:17:27:5b:71:08:00 SRC=167.104.0.82 > DST=192.168.1.103 LEN=40 TOS=0x00 PREC=0x20 TTL=48 ID=34256 PROTO=TCP SPT=443 > > How do I stop this? hello, to *completly* s

Re: Kernel logging firestarter events to syslog and console

2006-03-31 Thread Florian Kulzer
Anthony Simonelli wrote: Hey there, just upgraded to kernel image 2.6.8-3-686 and now all of the blocked connections from firestarter are logged in syslog and displayed at the console such as the following: Mar 27 21:25:25 debian kernel: ABORTED IN=wlan0 OUT= MAC=00:0f:66:a1:89:28:00:12:17:27:5b

Re: Kernel logging firestarter events to syslog and console

2006-03-31 Thread Sumo Wrestler (or just ate too much)
Anthony Simonelli wrote: Hey there, just upgraded to kernel image 2.6.8-3-686 and now all of the blocked connections from firestarter are logged in syslog and displayed at the console such as the following: Mar 27 21:25:25 debian kernel: ABORTED IN=wlan0 OUT= MAC=00:0f:66:a1:89:28:00:12:17:27

Kernel logging firestarter events to syslog and console

2006-03-30 Thread Anthony Simonelli
Hey there, just upgraded to kernel image 2.6.8-3-686 and now all of the blocked connections from firestarter are logged in syslog and displayed at the console such as the following: Mar 27 21:25:25 debian kernel: ABORTED IN=wlan0 OUT= MAC=00:0f:66:a1:89:28:00:12:17:27:5b:71:08:00 SRC=167.104.0.