netdev
[Top] [All Lists]

Re: Deleting incoming network packets / sk_buff

To: Michael Renzmann <mrenzmann@xxxxxx>
Subject: Re: Deleting incoming network packets / sk_buff
From: Ben Greear <greearb@xxxxxxxxxxxxxxx>
Date: Sat, 14 Aug 2004 15:15:00 -0700
Cc: netdev@xxxxxxxxxxx
In-reply-to: <411E642C.9010708@xxxxxx>
Organization: Candela Technologies
References: <411E642C.9010708@xxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803
Michael Renzmann wrote:
Hi all.

I'm just making my first steps in kernel programming, and I have a few questions.

It's necessary for me to "delete" network packets that come in on a ethernet device after passing them to an userspace program (through a packet socket that the program has opened). My first idea was to write a kernel module that registers on the NF_IP_PRE_ROUTING netfilter hook and does its job. But there are two downsides on this approach:

1. I need to delete every packet, no matter if it is IP or something else. As far as I understood only IP-packets will pass the netfilter hooks, since the netfilter framework only works with IP traffic.

2. The solution also has to work for 2.2.x kernels, as long as there is any way to achieve this functionality for these kernel series and 2.4.x as well.

I continued to dig some documentation, and found a possible solution in a rather old phrack article [1]: "What we do is code our own kernel module that registers our packet_type{} data structure to handle all incoming packets (sk_buff's) right after they come out of the device driver." While the authors use this technique to implement some "protocol obfuscation" or an in-kernel packet sniffer, it seems to be a good way to reach what I want to do.

Now, what I'm wondering about is the way to "correctly" remove an sk_buff so that the upper layer won't see the corresponding packet. I somewhere read that the code for packet sockets have to clone the sk_buff before passing it to the socket, else it would be "lost" and could not be seen by following handlers.

There is no way that I am aware of to block packets from high-level protocols,
but you can disable the higher protocols (ie, set IP to 0.0.0.0).

You can also hack net/core/dev.c to stop the packets from going
up the stack, but it requires more than just a new kernel module,
you'd have to actually change dev.c.  (Search for BRIDGE).

Ben

--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc  http://www.candelatech.com


<Prev in Thread] Current Thread [Next in Thread>