So look like the fastforward is done at the either
input/output? the so called layer 2?
======================================
WWW.XGFORCE.COM
The Next Generation Load Balance and
Fail Safe Server Clustering Software
for the Internet.
======================================
----- Original Message -----
From: Clark Gaylord <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 29, 2001 4:58 AM
Subject: Re: fastforwarding?
> On Wed, Jun 27, 2001 at 10:39:20PM -0600, Wes Peters
wrote:
> > Ruslan Ermilov wrote:
> > > On Mon, Jun 25, 2001 at 06:47:41PM -0400, Deepak
Jain wrote:
> > > > ...
> > > > What does the fastforwarding option do that the
normal forwarding option
> > > > doesn't?
> > > >
> > > See inet(4).
> >
> > The description there isn't very forthcoming.
fastforwarding caches
> > the results of a route lookup for destination
addresses that are not
> > on the local machine, and uses the cached route to
short-circuit the
> > normal (relatively slow) route lookup process. The
packet flows
> > directly from one layer2 input routine directly to
the opposing
> > layer2 output routine without traversing the IP
layer.
>
> I notice the man page points out that this prevents
the use of
> ipfilter, etc. The first packet(s?) do get forwarded
by the usual
> process (yes?), so does this imply that at least a
"deny X" would
> still work (as the first packet would get denied and
hence the
> cache does not get populated)? What are the
limitations to ipfw
> and friends working right in conjunction with
fastforwarding?
>
> Clark
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-net" in the body of the
message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
