Playstation 3 as a Media Player: m2ts.

Sony’s Playstation 3 is one of the best media players around: it can play Blu-ray Discs, pictures, music, videos and finally, games. One of the best uses for the PS3 is the ability to stream content from a media server through DLNA. Nothing of what is written above is any news, nor does it brings any big issues to anyone.

Now, let’s assume I have a number of media players at home, and I need to find a container that is supported by them all (PS3 included) but also must support all the functionalities I need (HD and subtitles). There things get tricky.

PS3 supports a number of containers out of the box: .ts, .avi and .m2ts, but is only able to support HD content on .m2ts files. To most people the big issue is that .mkv files are not supported at all, so we’re left with only 2, as .avi files don’t support h.264: .ts and .m2ts. On the other hand, there’s no way to play subtitles on HD content without burning it onto the picture itself.

MPEG2 transport stream (.ts), is a container designed for the transmission of live content, for instance Digital Television and DVB streams in general. It is immensely flexible as most professional containers derive from them, for instance AVCHD and m2ts. Unfortunatly, for the purpose of this post, it is to flexible, as it supports everything you can through at it: video, pictures, music, binaries, subtitles, and each one of them in at least 5 different formats. The problem lies on the immense number of formats and codecs that TS supports, which makes the support for ALL OF THEM spotty.

Derived from MPEG2 Transport Stream comes M2TS, is in fact is MPEG2 Transport Stream with some limitations: the supported codecs and formats are limited to AC-3, DTS (and HD versions), VC-1 and H.264, and subtitles from bitmapped to text, and that it, around 1000th of what is supported by the full blown MPEG2 transport stream. The advantage is that, as it limits thinks, support for it is also easier, and this is exactly what happens. .m2ts is supported by PS3 on all H.264 Full High Definition glory, both as a file and from any DLNA server, which the whole point. Unfortunatly, it still doesn’t supports subtitles, not even Bluray’s native format PGS (Presentation Graphics), which is a shame (at least until System Software 3.41). The up side on this is that most all other media players support .m2ts and PGS subtitles, and on top of this, is also supported by all other devices that support AVCHD, which makes it accessible from brands such as Sony, Panasonic and LG and on their equipments. So unless Sony decides to supports DIVX HD (and MKV), this is the best container to be supported by PS3 on the log run

So at the end, we got a container which is supported by PlayStation3, and at the same time is supported by everyone else and it supports subtitles, which is the furthest I could get on achieving all the goals.

Now, how to generate .m2ts files? Extremely easy, for windows, Linux and OSX just use TSMuxer, which is able to convert MKV to .ts or .m2ts, and adding subtitles as we needed. For Snow Leopard users, please use this version, as there is some issues with the latest version of TS Muxer. Please give a heads up in case that link dies, as I still have the required files.

HTC Magic tethering with Linux and OSX Snow Leopard without Android’s root permissions

Editor’s Note: Unfortunately, my HTC died just before I finished posting this, so not all steps were thoroughly tested although I did test the end results on both Snow Leopard and Linpus.

For all those still waiting for HTC to update it’s Magic smart phone to Android 2.2, where not a lot of options for tethering you device with Linux or OSX machines: root it, pay for PDAnet (and it only works on OSX), or follow the following steps :)

How it works

Android 1.6 doesn’t offer any capability to use a cell phone as a simple UMTS Modem, as almost every single cell phone I know does, including my old Nokia E61i, which allows for USB and Bluetooth tethering out of the box. There’s a single application which allows for USB tethering, which is PDANet, and it is expensive.Another alternative, is to root your Android cell phone, thus braking any warranty you might still have, and for some models, it’s a pain, and install a custom IPTables module, making the phone a router. Finally, the way I found easier: use a program called AZlink, which is basically an OpenVPN emulator. It emulates the OpenVPN interface to the host machine, but it doesn’t really any of the security stuff, it simply acts as an generic IP proxy and sends all traffic trough Android’s adb application for debugging.

Most steps are shared between operative systems, so here goes:

Step Snow Leopard Linpus Linux
1 On you Android phone, enable “USB Debugging” at Settings -> Applications -> Development
2 Download the current Android SDK. Versions for Windows, Snow Leopard and Linux, are available at Android’s development website.
3 Extract the SDK, then navigate to the folder where the adb application is, usually on the tools directory
4
Create/edit/save a rules file for udev to allow your machine to see your devicesudo vi /etc/udev/rules.d/91-android.rules

SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", SYMLINK+="android_adb", MODE="0666", OWNER="USERNAME"

If you have an HTC(instead of Motorola) Android phone – use this rule instead of the one above:

SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", SYMLINK+="android_adb", MODE="0666", OWNER="USERNAME"

5 Set the appropriate permissions to the rules file you just created.

sudo chmod a+r /etc/udev/rules.d/91-android.rules
6 Restart udev to load the new rule.

sudo restart udev

7 Connect your Droid to the computer with the USB cable and then use the following adb command to check for your device.

adb devices

example:
adb devices
List of devices attached
040364FA0901E011

8 Install openvpn on your computer so you can connect to your device with it.
(you need to have macports installed on you system)sudo port install openvpn
Install openvpn on your computer so you can connect to your device with it.Linux (Fedora, Linpus and every distro using Yum):

sudo yum install openvpn
sudo /etc/init.d/networking restart

9 Install openvpn on your Android. Note: the line “adb install” actually installs the azilink application on your Android device. After azilink is installed, an icon that looks like a flying insect will appear on your Android in the applications area.

wget http://azilink.googlecode.com/files/azilink-2.0.2.apk
adb install -r azilink-2.0.2.apk
wget http://azilink.googlecode.com/files/azilink.ovpn

10 Create a replacement resolv.conf file to be copied over to your /etc directory at run-time with the following contents:

domain lan
search lan
nameserver 192.168.56.1

11 Now create a very small script to start the modem, called “start modem.sh” with this text:

adb forward tcp:41927 tcp:41927
sudo cp resolv.conf /etc/
sudo openvpn --config azilink.ovpn

Download this file, into the directory of adb.
12 It seems that openVPN and Snow Leopard don’t get along so well on the TUN drivers, so it’s a good idea to install TunnelBlick. Remember to allways open TunnelBlick, but it’s not necessary for anything else.
13 Set your new script to be executable.

chmod 755 start_modem.sh

14 On your Android, launch the azilink app and place a checkmark by “Service active” so it can receive the connection from your machine.
15 Start the application on the terminal.

./start_modem.sh

Results

If everything went accordingly to plan, on your terminal you should have something of this sorts:


Thu Jul 15 19:35:13 2010 OpenVPN 2.1_rc15 i386-redhat-linux-gnu [SSL] [LZO2] [EPOLL] built on Nov 30 2008
Thu Jul 15 19:35:13 2010 WARNING: --ping should normally be used with --ping-restart or --ping-exit
Thu Jul 15 19:35:13 2010 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
#If you get the following line on OSX, you need to use the above configuration file
Thu Jul 15 19:35:13 2010 ******* WARNING *******: all encryption and authentication features disabled -- all data will be tunnelled as cleartext
Thu Jul 15 19:35:13 2010 TUN/TAP device tun0 opened
Thu Jul 15 19:35:13 2010 /sbin/ip link set dev tun0 up mtu 1500
Thu Jul 15 19:35:13 2010 /sbin/ip addr add dev tun0 local 192.168.56.2 peer 192.168.56.1
Thu Jul 15 19:35:13 2010 Attempting to establish TCP connection with 127.0.0.1:41927 [nonblock]
Thu Jul 15 19:35:13 2010 TCP connection established with 127.0.0.1:41927
Thu Jul 15 19:35:13 2010 TCPv4_CLIENT link local: [undef]
Thu Jul 15 19:35:13 2010 TCPv4_CLIENT link remote: 127.0.0.1:41927
Thu Jul 15 19:35:23 2010 Peer Connection Initiated with 127.0.0.1:41927
Thu Jul 15 19:35:24 2010 Initialization Sequence Completed

As soon as it started, with first important task was to test if going to the Droid impacted the performance of the connection, so I did a quick speedtest: and no, it’s still at the contracted 2Mbps. Great! It’s not anything worth writing home about, but good enough to use in case of emergency (although I’ve used less than 300Kbps, and it was well worth the trouble)

When you’re finished – hit ctrl+c at the Terminal from which you started the connection script. Then uncheck “Service active” in Azilink on your Android.

Plastic Fiber and the Status of the Home network

Probably, one of the most important technologies ever invented for the home is plastic fiber, POF (plastic optical fiber). Unfortunately, it’s mostly unknown to most people, unless you work on the industrial grade networks.

POF is basically the same technology as the old S/PDIF optical cable, but with a XXI century technology, from 2Mbps to 100Mbps (1Gbps already in the works, or maybe available) full duplex. What’s the advantage? Size. POF cables are between 1.5 and 2mm wide and extremely flexible. Those compare with Ethernet cables which are around five times thicker and far less flexible. This is not really important when building a new home, but extremely relevant when cabling an existing home. This cables are thin enough to be installed on wall tubing besides existing phone cables, or near the floor.

Well, POF is already well established on both industrial environments and on the automotive industries. It offers distinct advantages over traditional networking standards, based on copper wiring or glass fiber. POF is virtually immune to electrical interference, as are all fiber interfaces, but it also offers ease of installation and high flexibility. To put things on context, there are usually no connectors, crimping tools nor expensive fusion equipment. You simply cut the end and plug it into the device. These capabilities makes it perfect for usage on a car (remember Toyota’s problems with accelerators :) ), or on a noisy, dirty, high powered factory.

POF KIT from Netgear

POF KIT from Netgear

As far as the home is concerned, devices are comparably small. Most plastic fiber adapters are smaller than the power adapters needed for operation, as the picture can demonstrate. Each pair of adapters cost around 60 US$ and switches (yes, they do exist) cost around 200US$ which is far higher than comparable ethernet switches, but the market is so limited I haven’t yet seen one… Which brings us to the reason why this isn’t a widespread technology: as it requires new cables, there’s little perceived need for it, as far as manufacturers go. It competes against already available technologies such as powerline and ethernet over coax, which are already vastly available, even on retail. POF, on the other hand, has limited availability on retail, but is somewhat available to cable and fiber operators, but even on those, there is no widespread use.

As far as performance goes, plastic fiber goes as close as possible to Fast Ethernet, as it is capable for real throughputs of 98+ Mbps and non measurable added latency. Reasons for such resemblance to Ethernet include using the same technologies in terms of packet dealing, it’s store and forward, as well as error correction schemes, CRC32. For all purposes and means, it is based on good old 100Base-FX (or 1000Base-X for Gbit)

On the other hand, plastic fiber doesn’t have any of the drawbacks of most competing technologies: it scales linearly with the number of devices (it’s a point-to-point technology), it doesn’t has to withstand an heterogeneous infra structure (power cables, coax) and the cost is small, specially if we take into account that’s not a widespread technology.

For completion’s sake, plastic fiber devices and cables are readily available in Europe and Australia, but I haven’t stepped upon any store on the US. Showing it’s industrial origin, the body managing anything POF related is the POF Trade Organization, and the automotive and industrial usage is done by ODVA. The specs are defined at IEC 60792-2-40 as A4 type of fibers. Apart from the brands linked above, adapters are also available from big names such as Netgear and Motorola, so this isn’t such a niche product as people may think, even at home.

Main contenders

Wifi (802.11a/b/g/n)

For sure, the most ubiqious of them all, present on virtually every single household of the civilized world. It offers speeds starting at measly 1Mbps up to 300Mbps (although 600Mbps are possible), on paper. Although WiFi is the easiest way to deploy a home network, it’s performance is most time lackluster. Actual speeds are around 40% of what is advertized. On a top of the line 802.11n dual stream, channel bonding network, from the 300Mbps theoretical throughtput, one should not expect more than 140Mbps actual troughput. This on optimal conditions. From these values, there’s a long way down:

  • capabilities: devices that although supporting 802.11n, don’t have enough antennas, devices that don’t support 802.11n, which is by far the most common setup, even devices that only support 802.11b, which aren’t as rare as you might think.To make things worst, although higher standards are backward compatible, there is some performance penalty associated. So, unless you only allow 802.11n devices to connect, forget about trying to reach those 300Mbps, and start thinking on 60MbpsOn the other hand it’s not that bad, specially if we take into account that 54Mbps Wifi only delivered 21-25Mbps. Unfortunatly, all but the most recent cell phones and laptops support 150Mbps networks (I haven’t found any that support 300Mbps, but I haven’t searched either…).
  • Interfence: the 2.4Ghz band, is one of the ISM bands and it is packed. From microwaves to Wireless Phones, everything that required some bandwidth and a fair amount of range was developed on this band. If this wasn’t enough, the sheer number of already deployed wireless networks only makes things worst. From my living room, I can easily detect more than 30 other networks. To make things even worst, there are only 3 non overlaping channels, 1, 6 and 11. In sum, the more successful the thing is, the worst it gets. Obviously, one can say “let’s use the 5Ghz band!”. Yes, event if all, and I mean ALL, of your devices support 5Ghz Wifi (and this excludes ALL cell phones and most laptops), going to 5Ghz brings a huge handycap: range, as we can see bellow.
  • Range: all measuments I mentioned before are with line of sight. Again, things tend to slow down as you increase the amount of things put in the way, and specially walls, cement walls. I usually count 3 walls. After the third wall, forget about it. If we’re talking of the 5Ghz band, then things get even worse. One wall and that’s it.

So, if you can avoid all the above problems, you still need to make sure devices not only are able to see each other, they need to do it reliably. The second and third most obvious usages for a home network are Video and VoIP, both of each require low packet loss, low jitter and constant throughput, and wireless networks offers low packet loss, and that’s it. As most users know, wireless network work wonderfully when accessing the internet, were retransmissions pose no problem, jitter is irrelevant, and minimum throughput is higher than 1Mbps. VoIP may be within reach, but for video, we’re still ways to go. Even with line of sight, trying to access a good quality HD content (at up to 20Mbps) is all but impossible.

Finally, we have the cost and architecture, and those, everyone knows. It’s a point-to-multipoint architecture with dirt-cheap equipment. Again, everything comes back as us. As with all point-to-multipoint architectures, as you start adding more equipments, things begin to slow down, again. To put things clear, the advertised speed is the SUM off all devices within the network.

In sum, wireless networks are great to have on a laptop, but little else.

Powerline (PLC)

Someone had the wonderful idea of trying to reuse the existing power cables as a medium to carry information. It does have it’s advantages, it’s present virtually everywhere and it’s not impaired by the presence of walls. On the other hand, it’s main advantage is also it’s main disadvantage: the power cables. Unlike Cat5E or Coaxial cables, power cables were not designed to carry information, they’re not balanced, shielded, unbiased, etc, so, they’re possibly the worst possible medium to carry information. They’re not that much different from phone lines, and as such, powerline systems were designed in the same way. Power cables suffer from every kind of interference possible, on all bands you can imagine, from AM radio, to high frequency terrestrial TV (which again, resembles phone lines). To overcome all this difficulties, powerline systems are mostly based on OFDM schemes, so all interfering channels can be switched off and trust me, it happens VERY frequently. All powerline systems go to great lengths to overcome the problems caused by interference, by using all the advanced error correction techniques, such as Turbo Codes, LDPC and adaptive bit rates. The end result, is that on optimal conditions, speeds of up to 200Mbps are possible now, and up to 600Mbps in the near future. However, on real conditions, I never managed to get more than 20Mbps…

One detail to take into account is the issue of interference with CB radios. As most PLC devices work near the 30Mhz band, on non shielded cables, interference with CB will be very insensely present, to the point of rendering it completely unusable within a radius of several km. Interference with other PLC networks on the neighborhood can also affect performance.

Finally, there is the issue of “all poweline schemes”, because there were too many of them, all incompatible between themselves:

HomePlug AV Adapter by Devolo

HomePlug AV Adapter by Devolo

Homeplug AV – The original Powerline spec. From 2000 on, this association released several versions of the Homeplug standart: Homeplug 1.0 (max 14Mbps physical, although some proprietary versions reached 85Mbps), Homeplug AV (max 200Mbps physical) and more recently, Homeplug GreenPHY (max 10Mbps physical) for very low power devices. Currently, there is a huge number of HomeplugAV compatible devices, all working at an advertised top throughput of 200Mbps, although it’s not possible to achieve more than 185Mbps even on optimal conditions. Backwards compatibility between Homeplug 1.0 and HomeplugAV is not mandatory, and at most, 16 devices may be connected in the same segment. More recently, some devices labelled as “Homeplug AV 2.0” have appeared on the market, claiming 500Mbps throughout, but those are P1901 draft devices. Interesting, great attention has been taken for the “to the home” powerline infrastructure, known as BPL, so that it is interoperable with it “in the home” breathen. Manufacturers implementing this technology includes Devolo (known for offering 85Mbps solutions in the first place), Netgear (as usual…) and Belkin. Curiously, Echostar is using the technology on some of it’s set top boxes. Homeplug is a supporter of P1901. The operating frequencies are 2-28Mhz. More information at the Homeplug’s website.

Atheros is the main silicon supplier.

UPA Adapters by DLink

UPA Adapters by DLink

Universal Power Line Association (UPA) – Formed in 2005 as an alternative to Homeplug AV. Some manufacturers managed to get a relevance presence on the ISP market, but little to none on retail, where’re they’re mostly unknown. Netgear and Corinex are probably the most known of them. The association has had little development after it’s inception. The sole published specification called for 200Mbps PHY bandwidth. Usage is mostly limited to service providers, but some products can be found on retail.. The operating frequencies are 0-30Mhz. UPA is a supporter of G.hn so any effort will be present there. More information on UPA’s website.

HD-PLC – This is basically a Panasonic brand for their Powerline products. As a novelty, they added a whole new PHY protocol, wavelet OFDM, which supported PHY throughputs of up to 210Mbps. Apart from the little increase on maximum speed, they also promise to enhance the resiliency, so the the actual MAC throughput is closer to the maximum performance. How close do they got it I have no idea, as HD-PLC devices are not available outside Asia. The interesting thing, is that this new PHY protocol is one of the 2 PHY protocols supported on P1901. The operating frequency is 4-28Mhz. Further development will be done through P1901. More information can be accessed on the HD-PLC Alliance’s website.

Netgear P1901 Adapter

Netgear's Powerline AV 500, one of the first P1901 devices available, marketed as Powerline AV

IEEE P1901 – This is a IEEE working group formed in 2009, with the purpose of gathering the whole of powerline based technologies, and in 2010 the first version of the specs was published, containing 2 different PHY layers, which are… incompatible between themselves. (Why on earth would a standardization working group be allowed to create a spec with 2 incompatible PHY is something completely out of my understanding… or not). Both PHY specs are coming from each of the big supporters: HomePlug and HD-PLC. Currently there is no final spec, but equipments based on the last draft are already available, and with considerable performance levels. The draft spec calls for 544Mbps of maximum PHY throughput, but performance will vary. Apart from the PHY discussion, most effort was put on making sure that several powerline based technologies would coexist on the same physical installation (but not comunicate with each other), so that P1901 devices will not disrupt other pre existing devices and technologies, such as HomePlug or UPA, which are not compatible with P1901, or even things as ZigBee which also use powerlines, although for a completely different purpose. This Inter-System Protocol is highly advertised as a technology breakthrough. Little information on P1901 is available on the working group’s website, but it’s our best place for information on the status.

… and hopefully on the near future G.nh.

Coaxial Cable based

The only other medium readily available at home is the coaxial cable. This may not be universal, as it is more present on regions where cable and satellite services (and even fiber) are dominant, and less where DSL is the most frequent. This medium provides the best electrical characteristics possible (apart from high grade optical fiber), and surpasses even Cat6A cable. Although it was present on the dawn of the whole “Ethernet” thing (remember thin Ethernet) is has mostly disappeared. The original Ethernet was based on shared medium coaxial cable, (50?, hence the “thin” Ethernet, as the cables are indeed thinner than the current 75? cables.
Is works quite fine for small networks, but at the time only large corporations had the need (and the money) for networks, and for “large” networks this solution wasn’t scalable at all (to put numbers here, anything more than 10 users on the same segment is looking for trouble). On the other hand, it only supported 10Mbps of shared bandwidth. Fortunately, science came up to new ways of tapping it’s potential, and nowadays, if we take the example of DOCSIS 3.0, a single coaxial cable can support bandwidths of up to 6Gbps, for 5000 users at a distance of several Km. This is how far we’ve gone.
This presented a great opportunity for cable, and today fiber operators to tackle the problem of having to reliably transmit traffic within the household, easily, cheaply, and most important, reliably.

Features such as QoS and arbitration was present from day one, as it is a main requirement for transmitting video and voice, and at reasonable speeds (135Mbps). On the other hand, the maximum number of simultaneous connected devices on the same segment is also relatively low (up to 8 on MOCA 1.0), but this is of little relevance, as typical home networks have fewer than 10 total ethernet ports. The low device count easily becomes an advantage if we take into account that this is a shared medium and QoS is a requirement (it would make any sense to allow to connect several tenths of devices, it the available bandwidth is shared between all of them). Finally, on the coaxial side, there are far fewer players on the market.

HomePNA 3.1 Adapter from Motorola

HomePNA 3.1 Adapter from Motorola

HPNA – HomePNA, originally known as Home Phoneline Network Alliance, developed a solution of home networking based on already existing phone lines, which are present on most homes. Unfortunately, phone lines share most of the same restrictions of PLC, but to a lesser degree: there are far less interference and the cables are at least Cat3 compliant. Fortunately, the latest version of HPNA, HPNA 3.1 brought the support for coaxial cables, and the maximum speed up to 320Mbps. The operating frequencies for this technology are between 0 and 70Mhz, depending on the medium being used. Although it’s been around since the beginning of the home networks, HPNA is now mostly limited to providers, mainly home gateways and Set Top Boxes, and availability on retail is very limited. More information at the alliance’s web site. Further development on HPNA will be very limited, as they’re top supporters of G.hn.

UPA – yes, the same UPA as for powerline. UPA simply changed the electrical interface to support coaxial cable, mostly on the same way HPNA did. The maximum theoretical speeds are the same, but the real ones are not nearly the same, in the order of 70Mbps+ . Curiously, the operating frequency is 0-30Mhz, which is too near from the DOCSIS operating frequency for upstream traffic, which starts at 30Mhz.

MOCA Adapter from Netgear

MOCA Adapter from Netgear

MOCA – Multimedia over Coax Association, was the original body responsible for gathering a specification for coaxial based home networking. Coming from the likes of AT&T and DirectTV it is clear that this solution was mainly designed to fit the needs of the cable and satellite operators, where the coaxial cable is sure presence on the customer’s homes. At the same time, care was taken to ensure that the frequency range used wouldn’t impact existing services, such as DOCSIS or analor or digital TV, which is not the case with HPNA nor on UPA over coaxial. The initial version, MOCA 1.0 released on 2006, allowed for 135Mbps of MAC trhoughput, shared by up to 8 devices, which even a this stage, are enough devices for most homes. A year later, in 2007, MOCA 1.1 was released, with a top speed of 175Mbps of MAC throughput on up to 16 devices. Interesting enough, thus last July saw the birth of MOCA 2.0, which is a complete revamp of the whole MOCA spec. This new version calls for up 800Mbps of MAC throughput when using two bonded 100Mhz channels shared by up to 16 devices, and up to 1Gbps of MAC throughput on the new point-to-point mode. One important detail to take into account is backwards compatibility: all MOCA versions are backward compatible without performance degradation on the higher version devices. To ensure compatibility with all other services offered by cable and satellite operators, MOCA’s operating frequencies are far from both, between 875Mhz and 1.5Ghz, so there’s always an available frequency. More information available at the MOCA Alliance. In the long run, MOCA will be an competitor to G.hn.

HomeGrid or G.hn – Finally, in the near future, there will the G.hn to rule over all home networking technologies. G.hn is ITU’s attempt to organize the home network, regardless of the specific medium being used, and at the same time, maximize for both speed and reliance. To achieve all those goals, G.hn uses specific profiles for each medium. For instance, when coax is being used, a higher modulation (4096QAM) and lower FEC can be used, whereas on powerline environments, lower modulations and higher FEC will be used. This results on the highest possible throughput for each medium, up to 1Gbps on coax. The main device on a G.hn network is a Homegrid device, which is the coordinator of all G.hn networks, so a single device enables powerline, coax and phoneline networks, which the user may choose accordingly to the availability of outlets on a specific location, and bandwidth requirements. As the PHY spec is share between all mediums, a single controller is necessary, and any number of terminal adapters. You can’t get any simpler than this. After the standard is finalized, all topic regarding certification, marketing and business development will be taken care by the Homegrid Forum.

Competing technologies have a few advantages, though: Ethernet can offer gigabit speeds (although with some cavecats), powerline supports a one to many architecture (which can bring some advantages) where it works, and ethernet over coax (HomePNA, MOCA, etc), mostly works. WiFi is not really an option, specially when refering to walled buildings where you cannot take more than 10Mbps sustained for granted.

Let me summarize things:

Technology Maximum Throughput Typical Packet Loss Topology Cost Pros Cons
POF 100Mbps Now
1Gbps Future
0% Point-to-point
  • Extremely low Packet loss and Latency
  • Cost is the biggest disadvantages, but only against ethernet. Also, the point-to-point topology also increases de overall cost, but no compromises on performance
  • Requires dedicated cabling, but again, that’s the whole goal
Ethernet 1Gbps 0% Point-to-point
  • Around 1US$ per meter of CAT6
  • 8-port Gigabit switch at 50US$
  • Low cost of adapters and switches
  • Highest performance possible
  • Extremely low Packet loss and Latency
  • Requires Cat5E or Cat6 cable, which is hard to install on pre installed homes
Ethernet over Coax HomePNA (320Mbps)
MOCA (175Mbps – 1Gbps MOCA 2.0)
less than 10% point-to-multipoint
  • Around 70 US$ per adapter (MOCA 1.1)
  • Extremely easy to install on existing homes
  • Easy to extend
  • Low baseline performance
  • Performance decreases as more nodes are added
  • Some instalation quircks are sometimes necessary
  • Imcompatible with DOCSIS
Powerline 200 Mbps

1Gpbs (Future)

~ 50% Point-to-multipoint
  • around 70US$ per adapter
  • The least complex solution as it simply reuses the existing electrical cabling
  • Sometimes it works
  • When it does it’s slow
  • HUGE packet loss
  • High latency (around 10ms)
  • Very picky with the electrical installation: the better the installation, the worst it works.
  • Phone chargers and computer PSUs are specially problematic.
http://www.pofto.org

Next Episode: Plastic Fiber on the Home Network

Sorry for the delay, as the latest article on Plastic Fiber is not yet out of the oven. It should be ready by Saturday.

On the other hand, where’s other article already on the making.

Top Applications for Android

For all purposes, I’m a proud owner of an HTC Magic, obviously running Android. Out of the box, the Hero offers little: browser, email client (although Exchange support is included, thanks to HTC), and little more. Compared from my old Nokia E61e, it was a world appart: the browser really works! The internet is finally on the subway (private joke, sorry) and not exclusively limited to very basic less than ok mobile sites. This was already OK by me, but a brand new world appeared as soon as I got into Android Market, where there’s always an App that fits your needs. Well, not really all, but close enough…
After a few months, here’s my current list of favorite apps:

1. Google Listen – my far the most used app. It’s a fairly simple podcast fetcher and player, with a Google based podcast search engine. Although the search functionality is nothing worth of writing home about, the fetcher and player do work as expected. Plain and simple. On top of this, it also offers useful configuration possibilities as “only download when WiFi is connected” or “Update frequency”. No ads around which is nice.

2.WiFi Analyser -this app goes precisely for it’a name. It has 3 main functionalities: channel analysis, AP analysis and a spectrum graphic. It lets you f

ind out which is the less crowded 802.11 2.4Ghz channel, and which APs are interfering with any other. The following screen shots are self explanatory. The latest version has opt out

ads which is neither good nor bad…

3. WiFi switch – this is not an App, but a widget instead. It is as simple as effective. It shows the current connected SSID and connects or disconnects when pressed. No settings, no messing around, just works.

4. Call Meter NG and NetCounter – those are two separate apps, but their goal is closely related: showing usage statistics for voice calls and internet usage. Although both are far from perfect and ad supported, they are useful enough for me to use them fairly frequently.

5. Games! – you had to see it coming… there is at least a gazilion games available on Android Market, for every

possible taste and color. For me, I’m somewhat a GPL fan, so I recommend some classics:

Cardio Trainer example

Finally, after taking some weight, I needed something to keep track of the workouts. The solution: Cardio Trainer. This is a very complete app, specially taking into account it is mostly free, at least for 95% of all it’s usage: GPS tracking, calorie counter and historical recording of all workouts, including high resolution graphs. It’s an extremely well featured and well done app.

And for the time being, this is almost all. Apart from the last one: this post was totally written on the WordPress app. Only the formatting and pictures were done outside. Regardless, it’s quite an amazing feat, taking into account I’m talking id a cellphone. Remarkable.

Generating random files

Why on earth would someone want to generate files of random content (not files with random name) ?

Well, there is one big reason to do it: generate incompressible files. This seems a small reason, but there are a number os usage scenarios (apart from proving that random content is incompressible), most focus on transmitting files.

Although is transparent to most people, but some tools do background compression namely, https, IPSEC and SSL VPNs, etc, and as such, trying to measure real world performance on those require incompressible content.

First, how to generate it (assuming you can talk *NIX) ?

dd if=/dev/urandom of=random.file bs=1m count=100

Where:

if – Input file, in this case the virtual file /dev/urandom

of – Output file, the name of the destination file

bs – Block Size, the default block size for dd is 512bytes, which makes sense when copying files, but not terribly useful when creating files with a determined size. In this case 1MB

count – number of blocks to be copied

In this case, I needed to create a 100MB file of random content.

The result:

> dd if=/dev/urandom of=random.file bs=1m count=100
100+0 records in
100+0 records out
104857600 bytes transferred in 13.460029 secs (7790295 bytes/sec)

Now, how random is it? Hard to tell, but we can test how compressible it is:

> ls -la random.file
-rw-r--r--  1 user  staff  104857600 Jun 13 11:58 random.file
>gzip random.file > ls -la random.file* -rw-r--r-- 1 user staff 104874303 Jun 13 11:58 random.file.gz

As you see, the compressed is bigger than the uncompressed file. This is caused by the headers required by the compression scheme.

But for anyone wondering if gzip is not good enough, here’s with 7zip:

> 7za a random.file.7z random.file 

7-Zip (A) 9.04 beta  Copyright (c) 1999-2009 Igor Pavlov  2009-05-30
p7zip Version 9.04 (locale=utf8,Utf16=on,HugeFiles=on,2 CPUs)
Scanning

Creating archive random.file.7z

Compressing  random.file
Everything is Ok
> ls -la random.file*
-rw-r--r--  1 user  staff  104857600 Jun 13 11:58 random.file
-rw-r--r--  1 user  staff  106280801 Jun 13 12:15 random.file.7z

As you can see, the 7zip version is even larger than the gzipped file. So, this is a truly incompressible file.

Switch to our mobile site