All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Boxman <jasonb@edseek.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Hardware solution? (or v.easy software fix instead)
Date: Thu, 20 Jan 2005 22:21:00 +0000	[thread overview]
Message-ID: <200501201721.00234.jasonb@edseek.com> (raw)
In-Reply-To: <27251cb80501201407a89427a@mail.gmail.com>

On Thursday 20 January 2005 17:07, ajpearce wrote:
<snip>
> So I need an answer to avoid arguments.
>
> - Is there a plush hardware solution to the problem?

You could always get one of those Linksys routers that runs Linux and 
configure Linux traffic control on it.

<snip>
> If I go for the computer option and I'm able to pull it off I might as
> well make it a fileserver and use it as a single computer to download
> stuff on (so bittorrent, eDonkey and so we have 1 computer left on and
> not 3. If so what approach would you take for this? Use my own setup
> but binary parts to be sure it will work including kernel, iptables
> and iproute? - or should I take a distro setup for this and add stuff
> to that instead? I need:

L7-Filter hasn't been picking up Kademilia so filtering eDonkey tends to be 
difficult.  ipp2p might be better about this, but I haven't tried it.  I just 
filter based on IP for p2p since I only have a single box that does any p2p.

<snip>
> http://www.metamorpher.de/fairnat/

fairnat ought to let you share bandwidth out between groups of machines, so 
you and your roommate ought to be able to split up the bandwidth.

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

  reply	other threads:[~2005-01-20 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 22:07 [LARTC] Hardware solution? (or v.easy software fix instead) ajpearce
2005-01-20 22:21 ` Jason Boxman [this message]
2005-01-20 23:17 ` ajpearce

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=200501201721.00234.jasonb@edseek.com \
    --to=jasonb@edseek.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.