From 384fe01e6909f9f40147ee133a8f876f811a3a91 Mon Sep 17 00:00:00 2001 From: Ceri Davies Date: Tue, 7 May 2002 10:36:51 +0000 Subject: [PATCH] Bridges don't route, routers do. --- en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml index 53b0812d62..a4bdbee041 100644 --- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml @@ -372,7 +372,7 @@ host2.example.com link#1 UC 0 0 Either way, routing tables are set up so that each subnet knows that this machine is the defined gateway (inbound route) to the other - subnet. This configuration, with the machine acting as a Bridge + subnet. This configuration, with the machine acting as a router between the two subnets, is often used when we need to implement packet filtering or firewall security in either or both directions.