Here's a 'map' of my network 'plan':
+-------+ +--------+ +-------+
| Dumb | | Linux | | Linux |
| Cable +---+ Bridge +----+-----+ DHCP/ +----> Bunch of workstations
| Modem | | w/ QoS | | | NAT | on 192.168.10.X
+-------+ +--------+ | +-------+
X.X.X.62 Eth0 X.X.X.61 | Eth0 X.X.X.57
Eth1 ??? | Eth1 192.168.10.1
|
|
+-----> 3 more servers: X.X.X.58->60
The X.X.X IPs are routable IPs, just didn't feel like spamming you with the
#s.
Can you walk me through how some of those configs you have (particularly
your bridging script) would work with this?
While I've been dealing with Linux for about 13 years now, I haven't EVER
had to do any routing stuff, and this is really starting to stymie me. I'm
a programmer, not a sysadmin, by job description. I'm just the closest
thing we have to a sysadmin (and good at all the non-advanced stuff).
Also, any reason I'd have to use FC? I'm rather partial to Slackware (only
because it is on lots of my machines already, and I like standardizing on 1
distro for my ease of management). I know slackware has iptables, tc,
etc... since I've already enabled single-host throttling on 2 other Linux
servers (.57 and .58 on my network).
-Michael
> -----Original Message-----
> From: rsenykoff@xxxxxxxxxxxxxxx [mailto:rsenykoff@xxxxxxxxxxxxxxx]
> Sent: Wednesday, June 22, 2005 12:31 PM
> To: Support@xxxxxxxxxxxxxxxxxxx
> Cc: gypsy@xxxxxxxxxx; lartc@xxxxxxxxxxxxxxx; lartc-bounces@xxxxxxxxxxxxxxx
> Subject: RE: Help? Router/Bandwidth throttle needed.
>
> > The webpage was helpful in some ways, but I think it is a step too
> advanced
> > for me at this time.
> >
> > I guess what I want to know is if the 'plan' I have is sound?
> >
> > 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.
> >
> > 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.
> >
> > 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
> >
>
> Michael,
>
> You're on the right list. Your plan is very doable. A solution would be
>
> -------- --------- -------
> | cable|-----| linux |----| LAN |
> |modem | | bridge| -------
> -------- | w/QoS |
> ---------
>
> Just so happens I have a HOWTO on my website. You'll need to tweak the
> shaping for your own needs. For your servers you could do a total max
> limit (so users still always get some bandwidth) and implement SFQ
> (fairness queuing) so that if multiple servers are getting hit, they
> divide the bandwidth up as fairly as possible. Using src and dest IP the
> servers could be isolated. Then you could lump all other traffic together.
> Or my preference is to create another class for say port 80, or any other
> apps, that is above the default (bulk traffic).
>
> Here's the HOWTO
>
> http://www.burnpc.com/website.nsf/all/3a64a6369757819686256f960068ad75!Ope
> nDocument
>
>
> HTH,
> -Ron
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
