From: ph4ke <deff@sadomain.co.za>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] New member
Date: Mon, 03 Nov 2003 10:29:45 +0000 [thread overview]
Message-ID: <marc-lartc-106785538526846@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106784862220876@msgid-missing>
Hi Edmund
Thanks for responding so soon.
That works fine for shaping traffic that likes to talk on fixed ports, like
smtp of pop3, but really do much when you want to start limiting things like
outbound http or ftp traffic.
regards,
cilliè
On Monday 03 November 2003 09:04, you wrote:
> Cillie,
> I too have experience similar problems. I have since resorted to mark
> the IP addresses for the respective tc classifiers as such :
>
> Tc filter add dev eth0 parent 1:0 protocol ip prio 7 u32 match ip src
> (IP address) classid 1:10
>
> This seem to work for me. By the way, im using a patched RH9 2.4.20-18.
> Iptables 1.2.8-9.
>
> Regards
> edmund
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-11-03 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 8:37 [LARTC] New member ph4ke
2003-11-03 10:29 ` ph4ke [this message]
2003-11-03 10:35 ` Edmund Turner
2003-11-03 11:17 ` ph4ke
2003-11-04 3:54 ` Edmund Turner
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-106785538526846@msgid-missing \
--to=deff@sadomain.co.za \
--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.