Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Art Reisman <astormchaser2002@yahoo.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] New howto for Linux to dynamically throttle IP
Date: Wed, 06 Nov 2002 20:28:33 +0000	[thread overview]
Message-ID: <marc-lartc-103661466825097@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103655433629821@msgid-missing>



"David Boreham" <david_list@boreham.org>
 Wrote a good question regarding the linux arbitrator
 (www.apconnections.net for details)


"Interesting. Care to say why you didn't build on the
existing
traffic shaping technology in the kernel ? etables, tc
etc ?"


Response ... 
I suppose if somebody had suggested I look into these
aspects before I started I might have? I posted quite
a bit on ways to do this before starting. Not knowing
squat about LINUX.... Did not get much useful help
although people tried...

When I found the existing bridge stuff , I knew I had
a base for what I needed
so I just stuck this stuff right in the middle,
originally I did not intend to open it up (the
source). Just wanted to see if I could do it. What I
am really trying to do is find a solution for making a
turn key. self configuring, throttling product, such
that people can take it and plug it in. Talked with my
friends at Cisco and Yahoo and other ISP's and
determined there was not anything that matched what I
wanted to do. (there probably is just could not find
it) Hindsight tells me to be more useful I should have
studied Linux a bit more, but heck without a goal I
would never have even opened the kernel up...

On another note, it was really hard for me to navigate
the kernel, at first I could not get cscope up and 
had to do lots of grepping and finding to chase paths
throught the kernel. Also to be honest I am much
better at conceptualizing how to solve complex
problems than I am at looking at code and figuring it
out. I can do the  latter but don't really enjoy it
much.

Is there any well written text a level above code on
IPCHAINS and other kernel burgeoning features that I
can read to painlessly form a  conceptual picture? 



Thanks


Art
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2002-11-06 20:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06  3:44 [LARTC] New howto for Linux to dynamically throttle IP traffic Art Reisman
2002-11-06 17:08 ` David Boreham
2002-11-06 20:28 ` Art Reisman [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=marc-lartc-103661466825097@msgid-missing \
    --to=astormchaser2002@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox