From: Lars Oeschey <oeschey@web.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bandwith thinking error
Date: Thu, 13 May 2004 21:16:14 +0000 [thread overview]
Message-ID: <40A3E59E.9040705@web.de> (raw)
In-Reply-To: <9999.143.164.102.13.1084370910.squirrel@vdr.oescheyhome.de>
Jason Boxman wrote:
>I imagine you set $DEV to ethX, right? (In the original script it was ppp0.)
>
>
>
yep...
> <>You'll need to patch your kernel to use either one and they both
> have IPTables
> components you will need to use to match traffic. IPP2P needs CONNMARK,
> which is available in patch-o-matic for Netfilter. Be advised that you
> need
> the CVS version of IPTables to use CONNMARK with 2.6. IPP2P and CONNMARK
> work well on my 2.4.24 kernel with the CONNMARK patch from patch-o-matic.
> (The non -ng variant.) I also recommend the CLASSIFY patch if you are
> going
> to be using IPTables anyway.
>
ah, I wanted to avoid kernel compiling since I run a specialized debian
that's mainly intended as vdr server... I'm a bit afraid of destryoing
something with vdr ;) I blew the system up a bit to make it a universal
server, which was easy with debian, but I still got away without kernel
compiling...
Lars
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-05-13 21:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 14:08 [LARTC] Bandwith thinking error Lars Oeschey
2004-05-12 15:28 ` Andreas Klauer
2004-05-13 7:06 ` Lars Oeschey
2004-05-13 13:17 ` Andreas Klauer
2004-05-13 13:48 ` Lars Oeschey
2004-05-13 14:23 ` Andreas Klauer
2004-05-13 18:59 ` Lars Oeschey
2004-05-13 20:01 ` Andreas Klauer
2004-05-13 20:13 ` Jason Boxman
2004-05-13 21:16 ` Lars Oeschey [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=40A3E59E.9040705@web.de \
--to=oeschey@web.de \
--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.