From 4749e0f21959f44b4f67e49012cb4c6750c9dde1 Mon Sep 17 00:00:00 2001 From: Bart De Schuymer Date: Tue, 6 Aug 2002 17:25:33 +0000 Subject: clarify the word "hook". verb: attaching software onto a hook --- docs/br_fw_ia/br_fw_ia.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'docs/br_fw_ia') diff --git a/docs/br_fw_ia/br_fw_ia.html b/docs/br_fw_ia/br_fw_ia.html index 1e88c7d..bc58773 100644 --- a/docs/br_fw_ia/br_fw_ia.html +++ b/docs/br_fw_ia/br_fw_ia.html @@ -112,8 +112,8 @@

There are five hooks defined in the Linux bridging code. The sixth hook (BROUTING) is added by the ebtables patch. - The hooks are places in the network - code where software can hook itself in to process the + The hooks are specific places in the network + code on which software can attach itself to process the packets/frames passing that hook.


@@ -154,7 +154,7 @@

Figures 2b and 2c give a clear view where the - ebtables chains are hooked into the bridge code. + ebtables chains are attached onto the bridge hooks.

When an NIC enslaved to a bridge receives a frame, the frame @@ -277,10 +277,10 @@

Figures 3a and 3b give a clear view where the - iptables chains are hooked into the IP code. When the br-nf + iptables chains are attached onto the IP hooks. When the br-nf patch is compiled into the kernel, the iptables chains are - also hooked in the hooks of the bridging code. However, - this does not mean that they are no longer hooked into their + also attached onto the hooks of the bridging code. However, + this does not mean that they are no longer attached onto their standard IP code hooks. For IP packets that get into contact with the bridging code, the br-nf patch will decide in which place in the network code the iptables -- cgit v1.2.3