Date: Wed, 16 Feb 2000 22:47:04 -0700 From: Chris Fedde <chris@fedde.littleton.co.us> To: Tony Rini - Network Operations <tony@thegrid.net> Cc: questions@FreeBSD.ORG Subject: Re: Cable and DSL Routing Message-ID: <200002170547.e1H5l4V04540@fedde.littleton.co.us> In-Reply-To: Your message of "Wed, 16 Feb 2000 11:19:40 PST." <38AAF84C.EB4AEFC9@thegrid.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Tony Rini - Network Operations writes:
+---------------
| DSL --\
| |---- FBSD---Hub--My Internal Lan
| Cable-/
+---------------
I'd re-draw this as follows
+------------+
+-ISPA---DSL-----+xl0 |
Internet-+ | FBSD fxp0+-----[hub]--+ home lan
+-ISPB---Cable---+xl1 |
+------------+
A single inbound tcp connection is not going to balance traffic
between the two links. Traffic will traverse the link associated
with the destination IP address. This means that Internet content
for a single session will only download at the data rate associated
with that link, not at the sum of the two links. If you have lots
of users on the "home lan" and are sufficiently clever then you
might figure out a way to play with source addresses and balance
sessions over the links. Then on average your loading may approach
the sum of the two bandwidths but still any single session receives the
available bandwidth of one link.
If you have LOTS of outbound traffic then perhaps you can set up
your webservers or MTAs so that they bind to the appropriate IP
addresses on the box. Then you can probably flood both links with
pictures or commercial e-mail until one or both ISP's shut you down.
BTW. Dynamic Internet backbone routing is a bit complex. It is significantly
more complex than simply setting up routed to listen for rip
broadcasts then route them. Not only are there technical
issues such as the shear size of the routing table (> 75,000 routes)
<url:http://www.telstra.net/ops/bgptable.html>; but there are financial,
political and even theological issues that will come into play before
this setup is operational.
Install MRTG from the ports collection and turn on an the agent.
Set MRTG up to watch the traffic on your interfaces and watch your
traffic patterns. If nothing else you will get some numbers to
use in your arguments with your ISPs :-)
chris
__
Chris Fedde <chris@fedde.littleton.co.us>
303 773 9134
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002170547.e1H5l4V04540>