Slashdot Mirror
Dutch Experimental IPv6 MP3 Stream Relay
Remco den Besten writes "In order to promote the IPv6 protocol, some Dutch enthousiasts deploy an IPv6 MP3 stream relay server.
So, do something different with your IPv6 connectivity and listen to the streams offered!
See & listen (both IPv4 and IPv6)."
to see an honest admission of what people really are using the internet for and see it's early implementation with IPv6... This will convince an interminable number of those who were sceptics for the sake of being so...
A patent-encumbered lossy audio compression scheme. I cringe every time I hear it. Why couldn't it be flac streaming?
-Libertarian secular transhumanist
Yeah I know what FLAC is, but streamed? I mean, first you have the issue of encoding flac in realtime, but the bitrate on flac is far too high for most connections. Also the entire point of icecast and shoutcast is they scale to slow and fast connections pretty much transparently.
Worse.
You use KaZaA on your university's connection, they can track it all to your uni, and that's where it stops.
You use KaZaA with IPv6 on your uni's connection, and they can track it straight to your computer.
I know you were joking, but apparently this is kind of a problem for TV actors. Some shows that now shoot in HDTV, the actors don't like it because you can see too much detail, ie. flaws in their appearance, things makeup doesn't cover enough for such a high resolution. Supposedly once they get the hang of lighting things differently for HDTV, they should be able to go around the problem.
Can you imagine people watching "Friends" and realizing 'Hey... Wait a second, Poebe looks like she's 73 years old!'
Even if I load the ipv6 module in linux and use ipv6 applications. Doesn't my ISP have to route ipv6 packets before I can even use it?
Tom
Someday, I'll have a real sig.
Q. How do I install the IPv6 Protocol for Windows XP or Windows XP with Service Pack 1 (SP1)?
A.
To install the IPv6 Protocol for Windows XP:
1. Log on to the computer running Windows XP with a user account that has privileges to change network configuration.
2. Open a command prompt. From the Windows XP desktop, click Start, point to Programs, point to Accessories, and then click Command Prompt.
3. At the command prompt, type:
ipv6 install
Wow, it was literally that easy, now what did it actually do ?
Erm, FLAC is rather fast at encoding, provided you stick to the more sane settings and avoid --super-secret-totally-impractical-compression-le
It's fine for LAN situations; fileserver under stairs, player under TV, stream over network. The sort of people who would do something like this are precisely the sort of user who would appreciate lossless compression.
Of course I will be send-pr'ing the thing, so watch your favourite FreeBSD ports mailinglist.
I'll post it to my website when I have tested it ;)
Oh, you just want the ipv6 patch I made from it? Go ahead, take it. Just go to your xmms 1.2.7 source root and do a patch -p0, oh well, y'all know the drill.
Have fun listening :)
If you're going to push for a major networking change with streaming media, go for multicast instead. It has a huge direct benefit for streaming media.. The stream source would only need bandwidth for one stream, not one stream multiplied by the number of listeners.
Look up AEIOU from 1994 and see what we could be running today if it hadn't been essentially ignored or dismissed at the time.
The basic idea in a nutshell: you have your IPv4 addresses still, and you encapsulate another 32 bit address inside that. Taken to the extreme, it basically gives you a network of 2^32 addresses for every one of the existing 2^32 IPv4 addresses.
When you're stuck with a single IP address from your ISP for whatever reason, your logic works like this: connect to my real IP address A, then bounce through the gateway to real system B.
AEIOU would essentially work like that. The packets would have a destination of A like any other IPv4 header, and A would look inside (at the IP options, perhaps) to push it along to B.
It stands for "Address Extension by IP Option Usage", and that was about 10 years ago. Just think - everyone on consumer grade DSL/cable modems could have a single dynamic address with the freedom to use an entire Internet worth of internal addresses. And yet, that entire internal space would be able to talk to any host on the outside if they wanted to do it. All this happens transparently - the systems in the middle handle it like any other IPv4 packet.
Big deal. It's a tunnel, so to speak. The "outer" IP address forms the equivalent of the "routing part" of an IPv6 address, and the "inner" IP address plays the role of the "host part" of an IPv6 address. So far so good, but you obviously get only one benefit of IPv6, only half of it (64bit, semistatically divided into only 32bits routing/host parts) and at the cost of special packet treatment on the clients and gateway routers (because the clients have to add the complete target address and the gateways have to resolve the internal address to pass the packet on to the right internal machine.) NAT (2^48 addresses) is a better (more transparent to the clients) solution to this problem, and it still sucks. If you're going to these lengths just to get longer addresses, you might as well go for the real thing.
If you want to listen to Nectarine radio in IPv6, point your player to (IPv6 only): nectarine.ipv6.oulu.fi:8002 or nectarine.ipv6.oulu.fi:8004 or nectarine.ipv6.oulu.fi:8006 for different bitrates. Replace nectarine with sik1 if you wish to access the IPv4 stream instead. I set the IPv6 portion up something like a year ago, and it's been working reliably ever since.