Date: Fri, 06 Jul 2001 11:37:37 -0700 From: Bakul Shah <bakul@bitblocks.com> To: Wes Peters <wes@softweyr.com> Cc: "Louis A. Mamakos" <louie@TransSys.COM>, Ruslan Ermilov <ru@FreeBSD.ORG>, Deepak Jain <deepak@ai.net>, net@FreeBSD.ORG Subject: Re: fastforwarding? Message-ID: <200107061837.OAA27501@illustrious.cnchost.com> In-Reply-To: Your message of "Fri, 06 Jul 2001 00:35:04 MDT." <3B455C18.EB10C5DC@softweyr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> This discussion has devolved into yet another idiotic bikeshed. Nobody
> claimed anwhere along the line that fastforwarding was a solution to
> all routing ills, suitable for use in a core router, or acceptable for
> any of the wildly esoteric CRAP espoused in the past 10 or 12 messages
> in this thread. If you don't like fastforwarding, don't use it, but
> don't get in the way of people who use it and maintain it.
I don't think you realize that as implemented it is not
suitable for *any* router with even a single host that will
send to hundreds of thousands of distinct ip addresses over
any period of time. It doesn't matter if all the router has
is a single default route in its route table because it
creates a new cache entry for *every* destination address to
which it successfully forwards a packet. Consider
H ---- R ----> internet
R, a freebsd machine running fastforwarding code, has a
single default route to an upstream machine. Now on H
all you have to do is something like
<init msg>
a = <initial host addr>
while (a++) {
to.sin_addr.s_addr = htonl(a);
sendto(s, msg, msglen, 0, (struct sockaddr*)&to, sizeof to);
}
and R's cache will be filled up real quick.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107061837.OAA27501>