Date: Sun, 20 Apr 1997 10:28:59 +1000 (EST) From: "Daniel O'Callaghan" <danny@panda.hilink.com.au> To: Chris Samaritoni <csamarit@ucsd.edu> Cc: questions@freebsd.org, isp@freebsd.org Subject: Re: Controlled bandwidth sharing Message-ID: <Pine.BSF.3.91.970420102257.10264m-100000@panda.hilink.com.au> In-Reply-To: <3.0.1.32.19970419125734.009d0c20@gateway>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 19 Apr 1997, Chris Samaritoni wrote: > We have at our disposal for outgoing bandwidth: > > . a router with a dedicated T-1 @ 1.5mbps (flat rate $$) > . a 10baseT switched port on a shared OC-3 (metered rate $$) > > Currently we are on the switched port -- current bandwidth requirements are > about 1mbps sustained and about 8mbps burst. Our provider wants us to move > to a T-1, but we'll lose the nice burst capacity if we move to the T-1. > Ideally, we'd like: > > . first 1.5mbps routed to the T-1 > . additional bandwidth routed to the switch when needed Is the metering inbound only? I would guess that you have more inbound traffic than outbound. If that is the case, you'll have to control the packets' disposition on your feed's side of the link. This is going to be tricky. I have a bandwidth limiter using divert(4) sockets which you might be able to use as a framework to write your own daemon for this. Alternatively, if you keep specific routing info on the FreeBSD box upstream of the link, you can take the code which reads route info packets and bytes and use the info to adjust the destination for particular routes as required, to do the balancing. Another possibility would be to use mpd in ppp-over-tcp mode and hack it to do bandwidth on demand. Danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.970420102257.10264m-100000>