03-20-2003
A few comments here... Streaming audio is not file oriented. You can't wait for the entire file to download. This is used, for example, by radio stations to "transmit" over the internet.
And playing software doesn't buffer as much as it can...it will typically buffer a few seconds worth. It could buffer minutes or hours worth, but that kind of delay would be annoying. I'm not thrilled with the 10 second delay I now have.
Last night I tried listening to some internet radio on my laptop via a 56k dialup. I connected at a real speed of 44kb and it was adequate provided that I didn't do anything else over the internet. 96kb divided among 25 users is not going to be enough bandwidth.
Some of the websites of some internet radio stations claimed that they could deliver a good signal even with a 28kb dialup. I could find no claim that less bandwidth might work.
I had better luck with internet radio stations on my continent. A couple of times European stations drained my buffer. I am guessing that this related to Internet congestion rather far from my laptop, but I have no way to prove that.
I would rather listen to my stereo anyway.
6 More Discussions You Might Find Interesting
1. Solaris
This is weird, so I'm hoping someone here knows solaris and how it handles pipes...
OK... here goes...
Theres this log file, right? I want to tail -f it, grep that, gzip that, then pipe that into more commands. Well thats easy, right?
tail -f file | grep pattern | gzip | otherstuff...
... (1 Reply)
Discussion started by: sannik
1 Replies
2. Linux
Please, Anybody knows how can i configure Mozilla Browser to play M$ Windows Media in Linux??
I know konqueror can be set to play *.ASF or *.ASX files with the kmplayer application. But Mozilla doesn't give me the option to choose an expecifc application to play this files.
Is there any file in... (2 Replies)
Discussion started by: Dmitri-br
2 Replies
3. Shell Programming and Scripting
Hi,
I'm have a tcl application using expect. The application is connecting to a unix box and is running a script. What i need my app to do is show the output of the console as the script runs in realtime. At the moment, it my app is waiting until the script finishes and then dumps what is... (0 Replies)
Discussion started by: Phi01
0 Replies
4. Shell Programming and Scripting
Can someone help me of doing something like this
send.sh
#!/bin/bash
for last; do true; done
echo $* | gammu sendsms TEXT $last
every thing is good except that when i launch the script like this
./send.sh This is the message i want to send +63922XXXXXXX
it turned out the message of... (2 Replies)
Discussion started by: arturo322
2 Replies
5. UNIX for Advanced & Expert Users
Hi,
There are three type of buffering: Fully buffered,line buffered,and unbuffered. The goal of the buffering provided by the standard I/O library is to use the minimum number of read and write calls.
I understand that decrease write() calls when use output function output data to a file ,... (4 Replies)
Discussion started by: Edward114
4 Replies
6. Shell Programming and Scripting
The old buffering problem again, in a very specific case. On FreeBSD this time, but it's the generic line-buffered vs fully-buffered problem.
I'm trying to pick an available bluetooth speaker (all named audio_N), by pinging all of them en mass and taking the first to respond.
The... (10 Replies)
Discussion started by: Juha Nurmela
10 Replies
LEARN ABOUT NETBSD
tftp-proxy
TFTP-PROXY(8) BSD System Manager's Manual TFTP-PROXY(8)
NAME
tftp-proxy -- Internet Trivial File Transfer Protocol proxy
SYNOPSIS
tftp-proxy [-v] [-w transwait]
DESCRIPTION
tftp-proxy is a proxy for the Internet Trivial File Transfer Protocol invoked by the inetd(8) internet server. TFTP connections should be
redirected to the proxy using the pf(4) rdr command, after which the proxy connects to the server on behalf of the client.
The proxy establishes a pf(4) rdr rule using the anchor facility to rewrite packets between the client and the server. Once the rule is
established, tftp-proxy forwards the initial request from the client to the server to begin the transfer. After transwait seconds, the pf(4)
NAT state is assumed to have been established and the rdr rule is deleted and the program exits. Once the transfer between the client and
the server is completed, the NAT state will naturally expire.
Assuming the TFTP command request is from $client to $server, the proxy connected to the server using the $proxy source address, and $port is
negotiated, tftp-proxy adds the following rule to the anchor:
rdr proto udp from $server to $proxy port $port -> $client
The options are as follows:
-v Log the connection and request information to syslogd(8).
-w transwait
Number of seconds to wait for the data transmission to begin before removing the pf(4) rdr rule. The default is 2 seconds.
CONFIGURATION
To make use of the proxy, pf.conf(5) needs the following rules. The anchors are mandatory. Adjust the rules as needed for your configura-
tion.
In the NAT section:
nat on $ext_if from $int_if -> ($ext_if:0)
no nat on $ext_if to port tftp
rdr-anchor "tftp-proxy/*"
rdr on $int_if proto udp from $lan to any port tftp ->
127.0.0.1 port 6969
In the filter section, an anchor must be added to hold the pass rules:
anchor "tftp-proxy/*"
inetd(8) must be configured to spawn the proxy on the port that packets are being forwarded to by pf(4). An example inetd.conf(5) entry fol-
lows:
127.0.0.1:6969 dgram udp wait root
/usr/libexec/tftp-proxy tftp-proxy
SEE ALSO
tftp(1), pf(4), pf.conf(5), ftp-proxy(8), inetd(8), syslogd(8), tftpd(8)
CAVEATS
tftp-proxy chroots to /var/chroot/tftp-proxy and changes to user ``_proxy'' to drop privileges.
BSD
May 31, 2007 BSD