The amount of different user-replaceable Linux firmware images has risen rapidly. These embedded systems are designed by collaborative volunteers and replace the stock firmware images used by NAS or WiFi AP manufacturers. Typically, the image contains a ARM-compatible Linux 2.6 kernel along with (backwards engineered) WiFi drivers, bundled with standard iptables packages for network security. But how well do these embedded devices perform while routing / bridging up to gigabit network bandwidths? What are the limits of their memory buses, CPU:s, free memory space?

Purchase 3-5 network devices and compare k different embedded distributions along metrics of routing, bridging, OpenVPN bandwidth. Present the data and analyze how the firmwares differ in this aspect, if at all (are the differences in UI and packaging only?). Evaluate whether manufacturers are supporting or hindering this kind of volunteer work.

Alternative firmwares:

• dd-wrt
• OpenWRT
• Tomato
• stock firmware images

Skills needed: Compatible hardware devices must be researched from the firmware projects' web sites. Previous experience with Linux administration, routing, iptables, bridges, and WiFi strongly encouraged.

Focus gauge

• Theory 2/5: basic performance comparisons
• Coding / Implementation 3/5: difficulties will almost certainly be found, finding bottlenecks can be hard
• Reading 5/5: clues to be searched from user and dev forums