Child pages
  • Delivering live video streams to YouTube over IPv6

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


In all of these set-ups we used to run the actual content delivery systems ourselves, from our own networks.

The latest incarnation however is a cloud-based set-up which uses Wowza Streaming Engine to relay a video stream to YouTube and takes advantage of the new Youtube Live features to deliver the content to users.

This set-up has several benefits over the systems that we used to run locally:

  • More scalable. YouTube can distribute video much better than any locally run system. In our case we had a limit of 1GB/s, so anything over a few hundred visitors would mean the video stream got jerky and dropped out. This used to happen when someone posted a link to the stream on a popular forum such as , thereby DoSing the video stream (wink).
  • Multiple bit rates. We used to do transcoding into various lower bit rate streams, so that users on slow connections (mobile phones) could also watch it. This required an expensive plugin, which needed careful configuration, and which put a significant CPU burden on the streaming server. Google does this now, so no plugin needed, no CPU load, and less complex configuration.
  • Youtube works on much more many different devices. Many mobile devices have dedicated apps for YouTube, which makes sure it plays well on those devices.
  • Less support issues for end users. YouTube is the defacto standard for viewing video content on the Internet, so end users will have few issues with it.
  • Users can post comments. While it is possible for users to comment on the stream, we had to disable it because eventually the comments filled up with trolling messages.
  • Stream has a recording backlog of 4 hoursVCR capability. You can actually skip back in time by 4 hours, which is handy if you missed some action (smile).
  • Production side is IPv6-only. can be purely IPv6 (despite the general rule "What an engineer can do, is rarely what he should do "). Both the camera and the relaying system do not need to be publicly available. The camera just needs to communicate with the relaying system, which in turn needs to talk to YouTube. Since YouTube is dual stack, this means that both the camera and the relaying system can be purely IPv6:.


Gliffy Diagram
namewebcam live setup


Configuration of the camera

The camera is an Axis Q1755, which is mounted outside our office on the 4th floor of Singel 468 in Amsterdam. 


It runs Wowza Streaming Engine software (WSE). We have a perpetual license for the software. The management interface is HTTPS/Apache.

Follow the instructions on and install WSE.


See on how to do that.

The RTMP push out to YouTube is done to two host names ( and Initially I had put these hostnames in my ip6tables configuration, but eventually the cam went offline. Turns out that the IP addresses are not stable - which is perfectly valid. But because the ip6tables rules only get loaded and thus resolved at boot time, eventually the host names would start resolving to something else, and the outgoing stream would get blocked by the ip6tables script. Since there is no such thing as "Google IP ACL" I had to open up outgoing TCP port 1755 to the entire Internet. Not a big deal, but something to keep in mind.



  • YouTube Live is only be available on channels that have at least 100 subscribers. I'm guessing that this is done by YouTube to prevent random users to clog from clogging up their network with sleeping cat video webcam streams without there being any viewers for it. Either way, the TERENA YouTube channel already had 100+ subscribers so we were all good to go.
  • YouTube Live will is not be available to users in Germany: This is a political issue that we can't solve.