Displaying 4 results from an estimated 4 matches for "38kbps".
Did you mean:
32kbps
2005 Feb 09
2
relation between burst- and queue-size with low bitrate streams
...that the stream repeatedly skips (with pauses of around 20-30 seconds).
I've looked at various reasons for this behaviour such as bad connect speed
of the 56K modem and possible lack of bandwidth on the streaming server but
these do not seem to be the problem. The modem connect speeds are > 38Kbps
and there is enough bandwidth available to the streaming server.
I've switched on DEBUG logging and I am seeing these lines quite regularly:
[2005-02-09 20:38:57] DBUG source/send_to_listener Client has fallen too
far behind, removing
I have a hunch that the burst-size and queue-size might...
2004 Aug 08
0
working ftp shaping, i think
...#add the root qdisk
tc qdisc add dev eth0 root handle 1: htb default 26
#add main rate limit class
tc class add dev eth0 parent 1: classid 1:1 htb rate 100mbps
#add leaf classes
tc class add dev eth0 parent 1:1 classid 1:26 htb rate 100mbps
tc class add dev eth0 parent 1:1 classid 1:20 htb rate 38kbps
#filter traffic into classes
tc filter add dev eth0 parent 1:0 prio 0 protocol ip handle 20 fw
flowid 1:20
tc filter add dev eth0 parent 1:0 prio 0 protocol ip handle 26 fw
flowid 1:26
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9...
2004 Aug 08
1
shaping ftp traffic
I am trying to mark outbound passive ftp traffic with iptables and shape
it to 35KBytes. I am using the following script on the computer that
runs the ftp server.
It is not working correctly, it seems to limit ALL traffic. Cant file
share or anything.
Anyone might know what is wrong? It seems that I might need to add a
''lan limit'' so all traffic that is not marked still
2005 Feb 09
0
relation between burst- and queue-size with low bitrate streams
...atedly skips (with pauses of around 20-30 seconds).
>
> I've looked at various reasons for this behaviour such as bad connect speed
> of the 56K modem and possible lack of bandwidth on the streaming server but
> these do not seem to be the problem. The modem connect speeds are > 38Kbps
> and there is enough bandwidth available to the streaming server.
Issues to consider with modems are error rate (eg ifconfig) and whether
the modems keeps retraining. A modem retraining will add latency to the
stream making the client fall behind in the queue. Icecast will try to
send enough d...