:
:
:Oops... sorry, I gave bad advise. I'm looking at the code. It recognizes
:'K' or 'k' so your specification was right. It's the 'b' verses 'B' that
:it's sensitive to, so if you say: kbytes/sec it will think it's kbits/sec,
:and if you say kBits/sec it will think it's kByte
On Thursday 22 January 2004 16:16, Matthew Dillon wrote:
> Oops... sorry, I gave bad advise. I'm looking at the code. It
> recognizes 'K' or 'k' so your specification was right. It's the 'b' verses
> 'B' that it's sensitive to, so if you say: kbytes/sec it will think it's
> kbits/sec, and i
Oops... sorry, I gave bad advise. I'm looking at the code. It recognizes
'K' or 'k' so your specification was right. It's the 'b' verses 'B' that
it's sensitive to, so if you say: kbytes/sec it will think it's kbits/sec,
and if you say kBits/sec it will think it's kBytes/sec.
:Hi,
:
:I'm still having trouble limiting bandwidth for emule ports using dummynet
:features.
:I'm using FreeBSD 5.2-current machine for firewall. It has 2 Intel pro 100
:cards and it is configured as a bridge.
:
:I'm doing bandwidth limiting in the following way:
:
:# eMule
:${fwcmd} pipe 59 co
On Thursday 22 January 2004 14:49, Ganbold wrote:
> Am I doing right? For what NIC should I implement filtering, outside or
> inside interface?
> When I see MRTG graphs for ipfw it still shows bandwidth more than it
> supposed to:(
A few points..
- The nic is not really relevant except as a way of
Hi,
I'm still having trouble limiting bandwidth for emule ports using dummynet
features.
I'm using FreeBSD 5.2-current machine for firewall. It has 2 Intel pro 100
cards and it is configured as a bridge.
I'm doing bandwidth limiting in the following way:
# eMule
${fwcmd} pipe 59 config bw 256k
6 matches
Mail list logo
