Raspberry Pi runs with Raspian, a Debian compiled for ARM architecture. Pi has an ethernet adapter and usually also an USB WLAN adapter is attached in order to be able to access Pi wireless. Given this hardware you can use the Raspberry Pi as an ethernet to WLAN bridge and/or as an access point with a cable connection. The following article explains how to create an ethernet to WLAN bridge on Debian and Raspberry Pi running Raspbian but will work also on other Linux distributions.
Raspberry Pi runs with Raspian, a Debian compiled for  ARM architecture. Pi has an ethernet adapter and usually a USB WLAN adapter is also attached in order to be able to have wireless access to Pi. Given this hardware you can use the Raspberry Pi as a  ethernet to WLAN bridge and/or as an access point with a cable connection. The following article explains ho to create a ethernet to WLAN bridge on Debian and Raspberry Pi running Raspbian.
Update March 1st, 2014: Until kernel 3.6.11+ everything works as described below. Starting with 3.10.25+ ist doesn't work any more and a router has to be configured.
Update March 2018: There exists another way to create a kind of bridge by using an arp proxy. See here.

A lot of people are interested in a Raspberry Pi and want to get some idea about the operating system running on Pi without the need to buy a Pi first. I actually searched for a convenient way to test a backup script called raspiBackup I wrote for the Raspberry Pi. A nice way to evaluate Raspbian or to run any tests is to use QEMU to emulate the Raspberry Pi. Note that special Pi hardware like GPIO et al cannot be simulated. It's just the processor which is simulated. You need a Raspbian image and a system with Linux or Windows. Today I configured my system to run a Pi in QEMU and in the following article I explain step by step how I installed and configured QEMU on my Debian based Linux. The image has a networking connection right after startup and will use the existing host network connection  with NAT. Finally a script is provided which executes the steps described and simplifies the image creation process.

From time to time Raspberry Pi has networking issues. The following script analyzes Pi for common configuration errors and collects various network information, which provides a starting base for people who want to help to solve the issue, if the information is posted in a forum. Right now English and German are supported languages. If you want to help to get support for other  languages into the script just contact the script author (you find the eMail address at the beginning of the script header).

External IPs and MAC adresses together with SSIDs and wpa keys are masqueraded in the output.

Create .xbmc/userdata/keymaps/mouse.xml to hold the following mouse mappings which will switch the mouse buttons:

Raspberry Pi is a very nice hardware which can be used to solve various problems. I notice an increasing number of questions how to get access to the local PI from the internet. From a technical point of view that's not a problem: Just forward the required ports from your router to your Pi and disable on xbmc the firewall. This may cause you serious trouble because some folks from the internet will be able to access your Pi and even your local systems in your LAN. You should follow some rules in order to keep them out.


Raspberry PI owners should make sure access to their Pi from the internet is secure. It's possiblet o use ssh tunneling but the most secure and universal method is to use OpenVPN. That way all ports on Pi can be accessed from a remote client via the internet in a secure way. The following article describes how to install and configure OpenVPN on Pi and how to install and configure an OpenVPN client to access your Pi from the internet on a secure way. This configuration uses the simple variant which only allows one client at a time to connect and is suffient in most cases. The client configuration description covers Linux and Windows7.

The actual final raspxbmc version of February 2nd 2013 works perfect compared to the previous code drops. I have a Hama MCE remote control and it now works perfectly. Even the mouse pad works fine out of the box. Unfortunately the Context menu doesn't work - at least that's what I thought and read in the net. I spent hours to find a way to get this fixed and finally detected the file /opt/xbmc-bcm/xbmc-bin/share/xbmc/system/keymaps/hama_mce.xml on my pi and detected that contextmenu function is already mapped to a key on my hama MCE. But I didn't expect this key to be the contextmenu key.

Since a cople of weeks I own a Raspberry Pi. It's a nice toy. On one SD I installed XBMC. The other one has Raspbian. It took some time for me to get the Realtek 8192 USB WLAN stick to work. Now everything works fine.
Unfortunately I just got a kernel panic when I restarted the Pi. It's because I unplugged the power cable to restart the Pi quickly. Until now that's the way I did it until now and it worked fine. Even this tiny raspberry should be shut down the controlled way. Actually this was no big deal to recover: I plugged the SD card into a crad reader, connected it on my linux labtop and ran fsck on both partitions. Then my Pi started successfully again. 

cron usually runs on Linux per default. Unfortunately my script didn't run which I added to the crontab on raspxbmc.  That's because cron is not enabled on raspbxbmc per default. The following link explains in detail how to activate cron on xbmc.  Then everything works like a charme.


I backup my xbmc config on my raspberry pi with Linux and rsync.

On windows it's unfortunately not that easy. That's why I describe in the following paragraph how to create a backup on windows and how to restore a previous backup. In addition I provide two windows cmd files which execute the commands in sequence and make the backup and restore much easier. Three tools are requiered on windows: putty, pscp und plink which can be downloaded from the putty page. If you kick off the backup command with the at command on windows you will have an actual backup all the time.