A client had a problem with her iPad today.
She had just installed iOS 6 and now couldn’t connect to her Netgear WGT624v3
I discovered that there is a bug in IOS 6 which prevents connection
You can solve it quickly by downgrading your Netgear router firmware a few versions
You’re probably running WGT624v3 Firmware Version 2.0.26_1.01 (North America Only)
And you need to run WGT624v3 Firmware Version 2.0.21_1.0.1 (North America)
login to our router usually 192.168.1.1 go to the router upgrade menu on the right
select browse, navigate to your unzipped download and select upload
after a few minutes the router will reboot and the connection problem will disappear hopefully 🙂
Ok, heres how I’m doing it
I have an FTP Server on the network address 10.0.0.1
On the Raspberry Pi I installed curlftpfs which will enable me to connect to the ftp server
apt-get install curlftpfs
Now I need to make a mount point so in /mnt I create a folder called server
now I run
curlftps -o allow_other -o umask=000 usr:firstname.lastname@example.org /mnt/server
where usr = your servers ftp user name and pswd = ftp server password
The above command will mount the ftp server share in your new /mnt/server/ folder on the RPI, and you will be able to browse, read and write to this folder at will.
The command will have to be run once every time you restart the pi, its not persistent
Now for the actual back up command, I have chosen to use dd as the means of back up, not ideal it creates a large file, the same size as the SD card on the pi. My reason for this method is that the two times my pi has fallen over its been due to corrupt filesystem and has required the whole OS to be reinstalled. So my backup image needs to be a bootable whole disk image (.dmg)
The mount command is done and now I run the following:
dd bs=1M if=/dev/mmcblk0 of=/mnt/server/RPI_Backup.img
Where mmcblk0 is the rpi sd card, and RPI_Backup.img is the disk image on the server
I have a 16GB SD card and it takes about an hour to complete.
I haven’t written a script to automate it yet as I’m happy just to be able to do the whole disk backup at all while online as the previous methods involved removing the card from the rpi and using windiskimager on a pc (yuk) = downtime which is unacceptable.
Note: I am manually saving the .img images as a sequence on the server so i can maintain some sort of incremental system. RPI_Backup1.img >>> RPI_Backup2.img >>> RPI_Backup3.img etc, cumbersome but effective and way way easier than reinstalling raspbian removing all the crap and setting up everything just right!
Feel free to add corrections or comments
Well I needed a cheap UPS, my load requirements are low, approx 65 watts
2 x Raspberry Pi 8w
Synology Diskstation 410j (4x2TB) 39w
Netgear DGN3500 router 10w
Netgear Gigabit switch 8w
I bought the FSP Nano 800VA UPS from Scan.uk (my preferred supplier of tech) it cost £51.36, not bad
After considering a home made UPS, and pricing up what I would have to purchase, one from Scan was cheaper (and probably safer).
I have no idea of FSP’s reputation as a manufacturer, but they are big. Power supplies manufactured by FSP are sold by Antec, Sparkle Power International (SPI),OCZ, SilverStone Technology, Thermaltake, Nexus and Zalman under their own names. They are based in Taiwan
So they have the experience
With little expectations I unpacked it from the obligatory cardboard and polystyrene, a compact box, and overall, a compact unit.
It has a sealed lead acid battery, supposedly replaceable, one switch, two LEDs, and 2 standard UK 3 pin sockets. simple all plastic enclosure, boring and quite small for a UPS which is good.
There is no setup, just plug and play. After 8hrs initial charge I did the first disconnect test… a seamless switch over to battery/inverter accompanied by a single loud beep every ten seconds which could be heard throughout the house. There was an audible buzz from the inverter circuit while running off battery, but nothing too loud.
Assuming that there was full charge at the beginning of my test (there is no status display) with a load of 65 watts it sat there beeping annoyingly loud for 51 minutes.
Pretty much as expected. The rate of beeps doubled at 51 minutes which I assumed was the low battery warning, so the power was reconnected which happens seamlessly with a distinct relay click
The NAS, router and Pis had no problems throughout the test
So there you go, its been running for a few days now, and hopefully will blend into the background for a coupe of years before it needs attention
So far I would definitely recommend it with the caveat that I have little experience of its reliability
its been a fine 10 months since the first Raspberry Pi’s trickled into our eager hands
all expectations met, some exceded
I have used mine mainly for web servers and email servers, and basically messing around (i have 4)
but nothings perfect, there already has been a .1 upgrade to the ram, it went from 256 to 512 mb a couple of months ago, darned useful if you’re running apache2 with php5 and mysql like me. upgrade gratefully accepted
but there where a few hiccups along the way
1. its too sensitive to power drain from the usb port, regardless of the power supply you can easily drop the board voltage too low and the thing reboots, a problem with running wireless dongles. and reliability with powered usb hubs is poor, all too many power issues. its dead stable if theres nothing plugged into the usb port like my headless servers but problems arrise with power once the usb ports are used
2. the capacitor next to the power plug snaps off too easily, one of mine was delivered in this state, luckily it runs fine without.
3.the port arrangement is tricky, i know they had to fit a lot onto the board but at the moment wires head off in all directions making enclosure design hopeless so far, and the sd card sticks out too making a fully enclosed box tricky to design
4. sd card corruption, its happened a few times and its a nightmare forcing me to use dd every day on this server to create a whole disk backup, at least i can do it online
5. and lets have either pwer over ethernet or a sensible sturdy power connector, i don’r see any advantage to using usb at all
i’m sure i’ll think of more before the next version arrives
in the meantime, have as much fun with the Pi as i have
pin 2 is 5+
pin 6 is ground Heres the pinout for the whole GPIO connector
After struggling with low web server performance on this Raspberry Pi (running rasbian)I finally decided to change things, not an enticing prospect…
Its been running apache2, php5 and mysql(i)
For various reasons apache2 isn’t ideal in low memory situations, especially with mysql running too
The easiest option is to change from apache to something a little slimmer, after a quick read of some internets I decided to try lighttpd
the install is as folows:
apt-get install lighttpd
apt-get install mysql-server (only if you havent done it already)
apt-get install php5-common php5-cgi php5
apt-get install php5-mysql
service lighttpd force-reload
and that’s it, including the steps required to get lighttpd working with php
if you have apache installed on the same system change its listening port away from 80 by changing /etc/apache2/ports.conf
service apache2 reload will restart apache on its new port leaving lighttpd serving to port 80, job done
and a much more responsive stack it is too
certainly worth trying if you have been struggling with apache because its what you know 🙂