RE: magle, filter & FORWARD

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ok, now that I have made the major mistakes and they
are out of the way, let me try this.

Netfilter is made up of 5 subsystems, Pre-routing,
Input, Forward, Output and Post-routing.  These
subsystems are governed by three tables, nat, magle,
filter.  The elements of these tables have the
following characteristics.  First there is a 'hook' or
subsystem identifier (i.e. PREROUTING, INPUT, FORWARD,
etc), then there is a condition and finally there is
an Action/Target.  All received packets begin in the
Pre-routing subsystem, the Pre-routing subsystem
accesses the nat table and looks for all it's hooks
(all elements with PREROUTING).  Then the same is done
with the mangle table.  A routing decision is made,
and the packet would either move into the Input
subsystem or the Forward subsystem were the tables for
those subsytems would be accessed and so on.  All
packets end up in the Post-routing subsystem before
leaving an interface.

I am intentionally ignoring user created hooks.


	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux