All of lore.kernel.org
 help / color / mirror / Atom feed
From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Help?  Router/Bandwidth throttle needed.
Date: Thu, 23 Jun 2005 03:06:44 +0000	[thread overview]
Message-ID: <42BA2744.702E6144@iswest.com> (raw)
In-Reply-To: <20050620194426.4E85C18133@www.idealconditions.com>

ICI Support wrote:
> 
> The webpage was helpful in some ways, but I think it is a step too advanced
> for me at this time.

I don't wish to be rude, but if you cannot get what you want from
rc.proxyarp then you need to hire someone with the expertise to do this
for you.

> I guess what I want to know is if the 'plan' I have is sound?

It is a sound plan.  Actually, I cannot think of any alternate; that's
why I did it this way.  So I'd call it the ONLY plan.
 
> I want to put a linux box between my cable modem and my lan.  It'll go from
> the cablemodem into eth0 then from eth1 to the LAN.

The only difference between what you describe and rc.proxyarp is that
the interfaces are switched.  You might like to know that rc.proxyarp
runs on an AMD K6 233 CPU with 192Mb RAM, 6Gb (IIRC) HD and 3 NICs; the
point is that it does not take a lot of "horsepower".  eth0 connects to
a 5 port switch, and the 4 computers with external IPs connect to that
switch.
 
> I just want to do complete passthrough (with packets intact) if possible
> from one side to the other.  This machine doesn't have to do NAT or
> anything.

That's exactly what rc.proxyarp accomplishes.
--
gypsy
 
> Then I want to throttle the bandwidth through that box intelligently (I kind
> of know how to do that from the Advanced Routing Howto.  I've done it on the
> other three servers to throttle the bandwidth down).
 
> Once all that is working, I'll deal with using iptables to firewall.
> 
> If this plan is sound, I guess I need to know the vague steps involved to
> accomplish the routing.  The throttling I can figure out myself.
> 
> -Michael
> 
> > -----Original Message-----
> > From: gypsy [mailto:gypsy@iswest.com]
> > Sent: Monday, June 20, 2005 10:09 PM
> > To: lartc@mailman.ds9a.nl
> > Cc: ICI Support
> > Subject: Re: [LARTC] Help? Router/Bandwidth throttle needed.
> >
> > ICI Support wrote:
> > >
> > > I hope this list is still active.  I'm an experienced Linux Sysadmin,
> > but I
> > > haven't done much in the way of routing.  Due to a decision made by my
> > > higherups, I need to jam a computer between my ISP and my LAN to do
> > > bandwidth throttling.
> > >
> > > My current setup:
> > >
> > > 1 Crappy Cable Modem (7Mb/768Kb connection) with a static IP.
> > > 4 servers (all have static, routable IPs) - One of which is running
> > NAT/DHCP
> > > (2 NICs) for 6 workstations (All using DHCP)
> > >
> > > I have 1 spare routable IP.
> > >
> > > My current setup has the cable modem plugged directly into my LAN.  But
> > it
> > > ends up this modem doesn't do intelligent traffic/bandwidth management.
> > I
> > > need a way to throttle and poll usage through the modem such that
> > neither
> > > uploads nor downloads will ever use the full capacity (and thus dominate
> > the
> > > router).
> > >
> > > Currently, the best I can do, is to throttle some of those 4 servers,
> > but
> > > that doesn't help me with the workstations.   So I figured I'd need to
> > jam a
> > > machine between the modem and the LAN to work as a 'gatekeeper' to
> > control
> > > the bidirectional traffic (and I could use it for a firewall too).
> > >
> > > Can someone help me on how I need to set this up?  I have a spare box I
> > > could easily put two NICs into, if needed, to make it the gatekeeper.
> > >
> > > -----
> > >
> > > Michael Yacht
> > > CTO
> > > Ideal Conditions, Inc.
> > > 5329 Beeler Street, #2
> > > Pittsburgh, PA 15217
> > > v: 412-325-1375
> >
> > Michael,
> >
> > I have exactly your setup except that I have 2 internet connections and
> > (at long last) neither is crappy.
> >
> > http://yesican.chsoft.biz/lartc
> >
> > The top part of that describes my setup.  Stop when you get to "Now we
> > have 2 providers".
> >
> > Short description:  eth0 points to the internal servers which have
> > external IPs and I shape the traffic going out on that interface.  eth1
> > points to the internet and I shape the traffic going out on that.  In
> > order to answer for the 4 internal machines, proxyarp is employed.  Each
> > of the 4 internal machines has a firewall, but these are a LOT quieter
> > since I put a firewall on this computer <grin>.
> >
> > You may also want to ftp andthatsjazz.org/pub/lartc
> > --
> > gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2005-06-23  3:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-20 19:59 [LARTC] Help? Router/Bandwidth throttle needed ICI Support
2005-06-21  2:08 ` gypsy
2005-06-22 14:31 ` ICI Support
2005-06-22 16:31 ` rsenykoff
2005-06-22 22:29 ` ICI Support
2005-06-22 23:55 ` rsenykoff
2005-06-23  0:31 ` Carl-Daniel Hailfinger
2005-06-23  0:45 ` ICI Support
2005-06-23  3:06 ` gypsy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42BA2744.702E6144@iswest.com \
    --to=gypsy@iswest.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.