Skip to contentSkip to conversation

invalid packets default behaviour

DISCUSSION Ed White 1 participant 1 message Nov 29, 2002 netfilter

lore
Share & tools
lore

Ed White

author
#0 lore raw

Hi,

I've read this old mail on archive
(http://lists.netfilter.org/pipermail/netfilter/1999-September/002583.html)

/*
Well, you have to keep a sliding map of data in the current window anyway, and a pointer to the last match you're looking for. It's like this:

1) Checksum packet. If bad TCP checksum, drop it.
2) If it's outside current TCP window, drop it.
3) If packet's data doesn't match what's already in the map, or drop it.
4) Place packet in map.
5) If there are `holes' in the map before this packet, drop it.
6) Search from last match pointer to first hole: for each match, flag it (return, call matchfn, whatever your library does) and update match pointer.
*/

Is that part related to the default Netfilter behaviour ?

I would like to know if today Netfilter automatically drop invalid packets(header too short, bad checksum, etc...)
If no, is there a module under development to do it ? How could I log them ?

Thanks.

Ed