Re: [LARTC] Load balancing / Traffic shaping project looking for help

2005-01-12 Thread micah milano
This looks really nice! I really would like to try it out, but there
is no code on the sourceforge site released yet. Unfortunately I am
not the person you are looking for as my understanding of the advanced
routing concepts is not that good yet, thats why I am interested in
your tool :)

How much of this actually works?

micah


On Wed, 12 Jan 2005 12:59:07 -0500, Aaron Wolfe <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> I've managed to create a web based interface to some of the advanced
> routing capabilities in Linux.  Currently it is functional (and
> pretty, i think :) although far from perfect.  I'm looking for people
> with better programming skills and/or understandings of advanced
> routing concepts in Linux than I have who'd like to help out with the
> project.
> 
> The overall goals are:
> #1 to make advanced routing and traffic shaping very easy for those
> just getting started
> #2 allow admins to easily backup or restore multiple versions of an
> entire linux router's configuration (fw, routing, traffic shaping,
> interface settings etc) via a single text file, much like a cisco
> router
> #3 make it all pretty enough that the nontechnical CIO types say "wow"
> and let us use linux routers in production more often.
> 
> The current system is a collection of perl CGI scripts and a
> background process that keeps an eye on things.  It supports high
> availability via the heartbeat project and uses Julian Anastasov's
> kernel patches to support load balanced routing with dead gateway
> detection.  The background process can start a dialup connection if
> all other connections have failed.
> rrdtool is used to generate lots of pretty graphs locally, and the
> system supports snmp and zabbix remote monitoring.
> 
> If you're interested (and especially if you'd like to help!) please
> check out the project page:
> 
> http://sourceforge.net/projects/kdtrg/
> 
> thanks
> -Aaron
> ___
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
___
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


Re: [LARTC] realtime trafic monitor

2004-11-25 Thread micah milano
I've found pktstat to be almost exactly what you are looking for.


On Mon, 22 Nov 2004 19:25:31 -0600, Josh Nerius <[EMAIL PROTECTED]> wrote:
> tcptrack provide the functionality you are looking for.
> 
> http://www.rhythm.cx/~steve/devel/tcptrack/
> 
> Josh Nerius
> 
> 
> 
> 
> On Mon, 22 Nov 2004 13:25:08 +0200, Gogu Ionut <[EMAIL PROTECTED]> wrote:
> >
> >
> > Hello !! i search a small utility (console based) to view the traffic on
> > real time made by 1 user (ip ) ...something like :
> >
> > 192.168.1.2  11 kbps
> > 192.168.1.3  111 kbps
> > 192.168.1.4  88 kbps
> > 192.168.1.5  64 kbps
> >
> > Thanks!
> >
> > ___
> > LARTC mailing list / [EMAIL PROTECTED]
> > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> >
> 
> 
> --
> Math problems? Call 1-800-[(10x)(13i)^2]-[sin(xy)/2.362x]
> 
> 
> ___
> LARTC mailing list / [EMAIL PROTECTED]
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


[LARTC] Shaping weirdness

2004-08-13 Thread micah milano
I've been following the HOWTO, and reading mailing list discussions
about throttling bandwidth, and have had some success, but I just want
to tie off some loose ends. Essentially what I am wanting to do is to
keep our bandwidth usage below 1megabit, because if we go over we get
charged for that traffic. I've used some of the examples from the
HOWTO to limit our bandwidth, but I find that it gets limited to
*half* what I specify. If I specify 256, bandwidth tests (using iperf)
show that things are clamped at 128, that makes me scared that I am
doing something right.

I'm using cbq, I've seen some people suggest using htb instead because
it is more reliable and easier to configure, but I thought i'd get
what the HOWTO says working first, and then investigate alternatives.

I've got a machine that sits in front of the network, has the internet
plugged into eth0 and the other side plugged into eth1, and I am doing
the following:

#!/bin/bash
LIMITDOWN=256
LIMITUP=256
DEV=eth0
DEV2=eth1

# clean up qdiscs
tc qdisc del dev $DEV root 2> /dev/null > /dev/null
tc qdisc del dev $DEV2 root 2> /dev/null > /dev/null

# limit up- and downlink
tc qdisc add dev $DEV root handle 1: cbq avpkt 1000 bandwidth 100mbit
tc qdisc add dev $DEV2 root handle 2: cbq avpkt 1000 bandwidth 100mbit

tc class add dev $DEV parent 1: classid 1:1 cbq rate ${LIMITDOWN}kbit \
allot 1500 prio 5 bounded isolated
tc class add dev $DEV2 parent 2: classid 2:1 cbq rate ${LIMITDOWN}kbit \
allot 1500 prio 5 bounded isolated

tc class add dev $DEV parent 1: classid 1:2 cbq rate ${LIMITUP}kbit \
allot 1500 prio 5 avpkt 1000
tc class add dev $DEV2 parent 2: classid 2:2 cbq rate ${LIMITUP}kbit \
allot 1500 prio 5 avpkt 1000

tc filter add dev $DEV parent 1: protocol ip prio 16 u32 match ip dst \
0.0.0.0/0 flowid 1:1
tc filter add dev $DEV2 parent 2: protocol ip prio 16 u32 match ip dst \
0.0.0.0/0 flowid 2:1

tc filter add dev $DEV parent 1: protocol ip prio 16 u32 match ip src \
0.0.0.0/0 flowid 1:2
tc filter add dev $DEV2 parent 2: protocol ip prio 16 u32 match ip src \
0.0.0.0/0 flowid 2:2

tc qdisc add dev $DEV parent 1:1 sfq perturb 10
tc qdisc add dev $DEV parent 1:2 sfq perturb 10

tc qdisc add dev $DEV2 parent 2:1 sfq perturb 10
tc qdisc add dev $DEV2 parent 2:2 sfq perturb 10
___
LARTC mailing list / [EMAIL PROTECTED]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/