Displaying 4 results from an estimated 4 matches for "105kbps".
Did you mean:
100kbps
2006 Mar 05
0
tweaked shaping rules
...-j MARK --set-mark 3
iptables -t mangle -A BW-OUT -p tcp --sport 50000:51000 -j RETURN
# clear the qdisc
tc qdisc del dev eth1 root
#add the root qdisk
tc qdisc add dev eth1 root handle 1: htb default 10
#add main rate limit class and 2 leafs
tc class add dev eth1 parent 1: classid 1:1 htb rate 105kbps ceil 105kbps
tc class add dev eth1 parent 1:1 classid 1:10 htb rate 45kbps ceil
105kbps prio 0
tc class add dev eth1 parent 1:1 classid 1:11 htb rate 40kbps ceil
105kbps prio 1
tc class add dev eth1 parent 1:1 classid 1:12 htb rate 20kbps ceil
105kbps prio 2
#filter traffic into classes
tc filte...
2006 Mar 05
0
revised shaping rules, please take a look
...ue
doesn''t get full. I run a ftp server 24/7, do normal email, some ssh,
web surfing and some downloading. I have a cable modem with 10mbit
download and 1mbit upload. The router is a linux box running IPCOP and
eth1 faces the internet and eth0 faces the LAN.
I want to set my cap at 105kbps (slightly less than 1mbit) for all
outbound traffic. I want ftp traffic to send at the full 105kbps
without affecting my download speed or ssh ability. I also want the ftp
to send at the full 105kbps UNLESS I am sending an email. I think the
following rules will do that.
#!/bin/bash
# clea...
2006 Mar 04
3
my shaping rules wont work on nat box
I am currently running the following script on an internal machine to
shape outbound ftp and email traffic.
I am trying to move the script to my nat router (ipcop with 2 nic cards)
so that it shapes the whole network and not only the outbound of 1 box.
I have cable modem -> ipcop (eth1) >(eth0 - 192.168.1.1) >
192.168.1.100 and 192.168.1.101.
The scripts works great running on
2001 Jan 27
3
[OGG IS BEST, BUT UNUSABLE! (very important)]
...t be determined by ear).
I encode this piece with Lame VBR -V 1 and I'M COMPLETELY SURE IT'LL BE ABOUT 98% transparent to the original. Sometimes the piece
will be encoded at 200 kbps, sometimes 105 kbps (these are real cases). It'll almost never (98%) contain artefacts, even the
latter-105kbps file.
Now, the same difficult piece which was classified by Lame's sophisticated algorithms as a 200kbps put to OGG with ABR 128kbps.
What the output will be like?:
- it'll be encoded at about 145 kbps - not 128 kbps (which is still not enough, even for OGG)
- it'll sound as a piece of...