Skip to contentSkip to conversation

Netfilter Design

DISCUSSION Ryan Hagelstrom 3 participants 3 messages Jun 24, 2003 – Jun 26, 2003 netfilter

lore
Share & tools
lore
#0 lore raw

I'm curious why Netfilter was designed like it was allowing for the redirection of IP packets rather than going with a design of a generic Intermediate driver that allows the capture and injection of any type of packet along with packets that may not have been incoming on the NIC or coming down through the stac? It seems the current design works good for what it does, but it seems going with an IM design and building netfilter as a offshoot of the IM may have been a more generic and a good building block for other projects. Take the inability to orgianlly capture ARPs. That could have been entirelly avoided if it wasn't so restrictive.

Also, this isn't the only list like this but why on earth in this day and age do the archives not have a search feature, but rather download and do search yourself. I feel that a lot of the repeat questions and "search the archives" responses could be eliminated if it was not so much of a pain in the ass to search the archives.

Ryan Hagelstrom

#1 lore raw
Quoted 5 lines · Ryan Hagelstrom

I'm curious why Netfilter was designed like it was allowing for the redirection of IP packets rather than going with a design of a generic Intermediate driver that allows the capture and injection of any type of packet along with packets that may not have been incoming on the NIC or coming down through the stac?

Because netfilter hooks are placed in layer three stacks (e.g. IPv4), and thus don't receive (or pass on) any other types of packet. Another issue is, that if you inject a packet into the network stack, there are dozens of internal data structures you need to fill in (just look at all the members of 'struct sk_buff'. However, how can any userspace process (I assume you are talking about such) know of reasonable values for lots of in-kernel structure pointers?

Quoted 5 lines

It seems the current design works good for what it does, but it seems going with an IM design and building netfilter as a offshoot of the IM may have been a more generic and a good building block for other projects. Take the inability to orgianlly capture ARPs. That could have been entirelly avoided if it wasn't so restrictive.

What is 'IM' ? And btw, there are netfilter hooks in the ARP code in recent kernels.

Quoted 5 lines

Also, this isn't the only list like this but why on earth in this day and age do the archives not have a search feature, but rather download and do search yourself. I feel that a lot of the repeat questions and "search the archives" responses could be eliminated if it was not so much of a pain in the ass to search the archives.

This is because the distribution installed on our listserver (debian woody) does ship mailman 2.0.x, which in turn doesn't provide a list archival software that includes a search function.

I'd rather keep the installation as close as possible to the mainline woody distribution - this way I don't need to manually build packages in case of security updates, etc.

[yes, the recent switch to exim4 already introduces custom packages...
but the increasing amount of spam and the need for html filtering was too important]

And yes, I'd also love to have searchable archives on a couple of other list servers (all woody) that I'm maintaining :(

Until debian sarge becomes stable, you will most likely have to stick to marc.theaimsgroup.com for searching netfilter lists.

Quoted 1 line

Ryan Hagelstrom

Signature · 5 lines
- Harald Welte <[email protected]>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie
#2 lore raw
In reply to Ryan Hagelstrom
Quoted 6 lines · Ryan Hagelstrom

[...]
Also, this isn't the only list like this but why on earth in this day and age do the archives not have a search feature, but rather download and do search yourself. I feel that a lot of the repeat questions and "search the archives" responses could be eliminated if it was not so much of a pain in the ass to search the archives.

I know it's not the best solution, bu it's definitely the best search engine : google :) You can simply use the 'site:' keyword of google (i.e. site:lists.netfilter.org) OK, it won't feature the very recent posts, but it's better than nothing.

example:
http://www.google.com/search?hl=en&q=Netfilter+Design+site%3Alists.netfilter.org

Finally, there are already existing proper search engine for the netfilter and netfilter devel mailing lists:

netfilter searchable archive:
http://marc.theaimsgroup.com/?l=netfilter&r=1&w=2

netfilter-devel searchable archive:
http://marc.theaimsgroup.com/?l=netfilter-devel&r=1&w=2

Have a nice day,

Fabrice.
--
Fabrice MARIE

"Silly hacker, root is for administrators"
-Unknown