Connect to WiFi or Create An Encrypted DHCP Enabled Ad-hoc Network as Fallback
In this post I describe how I have configured my Raspberry Pi (RPi) to first attempt to connect to WiFi and if that fails, create and use an ad-hoc network as fallback (in this way I can always reach the RPi via SSH). The blog post is based on the following “How To” from the Raspberry Pi forum: http://www.raspberrypi.org/phpBB3/viewtopic.php?t=19517&p=190855 – however, I have introduced a level of more detail and a couple of modifications in order to get faster boot time and support for multiple wireless networks (see my previous RPi blogt post suvery for details on which parts of that “How To” I think are good as well as which I think can be improved).
Checking Your Raspberry Pi Board Version
In order to find out what hardware revision you have you can run the following command at the command prompt or via a terminal window :
NOTE : The Revision number given in cpuinfo file is the hardware revision number. This is not the same as the Raspberry Pi Revision.
Building A Raspberry Pi VPN Part One: How And Why To Build A Server
Free, unencrypted wireless is everywhere, but you shouldn’t be checking your bank account on it unless you don’t mind somebody else snooping. The solution? A virtual private network, or VPN.
Note: An update has been pushed to Raspbian to flip the screen ( rotate it by 180 degrees ) for a better desktop viewing angle. This makes it upside-down in our stand, so you’ll need to change a setting to flip it back.
To do this, open
/boot/config.txt in your favourite editor and add the line:
If you’re using one of our stands, you wont be able to pull the legs out and flip it upside-down since the leg locking mechanism wont work this way. Also, you wont get an HDMI cable or, more importantly, the power cable in without it standing off the desk surface so we recommend using it with this rotation which is great for desktop usage anyway.