Hello Victor,
Friday, June 11, 2004, 5:21:05 PM, you wrote:
VC> +---+
VC> |debian13 |
VC> |eth0:192.168.0.13 |
VC> +---+
VC> |eth0
VC> |
VC> |eth0
VC> +--+
VC> |firewall/router(linux-box)|
VC> |which con
Tuesday, April 6, 2004, 9:59:55 PM, you wrote:
TL> hola listeros!
I do not understand that (Spanish?) language, but I guess you want
a tool which would output traffic statistics?
I have created for the ISP i work for, pretty simple tool.
If some people wanted, I could share it under GPL.
+-[ t
Thursday, February 5, 2004, 2:48:13 AM, you wrote:
B> So maybe I'm dense, but I thought that throughput limit on classes where
B> class-wide, not for each session in the class. In otherwords, if I limit
B> class A to 50KB/5s, every tcp session in that class fights for the same
B> 50KB/5s.
You
Wednesday, February 4, 2004, 11:15:17 PM, you wrote:
B> That's the closest thing I've seen to what I want, but it's not quite
B> there. From what I understand, this lets me identify all sessions that
B> have sent more than x bytes.
Right.
B> I want something that says "for every session going
Wednesday, February 4, 2004, 9:30:14 PM, you wrote:
B> Hey guys, I'm looking for a way to limit ingress throughput for each tcp
B> session to a destination port on my server. I've found lots of ways to
B> limit total throughput to a given port on an ip-level, but that's not
B> quite the same thing
Hello Sjaak,
Monday, December 29, 2003, 5:10:51 PM, you wrote:
SN> Hi
SN> Does anyone have expirience or advice and set me on the wright track if it
SN> is usefull to slowdown search engine spiders.
SN> I want to limit some spider how eating lott's of bandwith from my server.
SN> Is it possible
Hello Cezar,
CA> Hmm, that would become too complicated. There is no other way ?
Quick and dirty solution would be to mark packets on Router A by
changing the TOS to some known value
(iptables/ -t mangle -j TOS --set-tos ..)
and filtering by TOS value on Router B
(tc/ filter u32 match ip tos
Monday, November 3, 2003, 2:37:26 AM, you wrote:
AK> Am Saturday 01 November 2003 21:32 schrieb Peteris Krumins:
>> i wrote a few days ago but did not receive any answers.
AK> I did not receive/read this mail.
That one was about limits and data precision.
>> The example
Hello gentleman,
i wrote a few days ago but did not receive any answers.
I simplified the problem and even wrote a quick example
which demonstrates the innacurate rate precision:
tc qdisc del dev eth0 root >/dev/null 2>&1
tc qdisc add dev eth0 root handle 1: htb
tc class add dev eth0 par
Dear all,
I am an experienced unix administrator and a long time ago (1+ year)
I made traffic-shaping system for an ISP (~400 clients).
Each ip address requires 4 classes -
2 for incoming (internet->client), one for international traffic,
the other for local-country and border-cou
Thursday, September 25, 2003, 10:35:39 PM, you wrote:
WDW> Sorry, I must have missed it when reading the netfilter howto. I
WDW> found it later when reading through it again: approx 32,000 connections
WDW> per 512 megs of ram.
Wrong.
1 conntrack entry = 292 Bytes.
512*1024 = 524800 KiloBytes
5248
11 matches
Mail list logo