I have been debating whether or not I should put this up, however after much testing I have concluded that it is safe, it works and many other people have used this method, it goes without saying that this is still quite dangerous to do as nobody knows why D-Link doesn’t allow the downgrade to take place and they may believe it can cause bricked routers.
There is firmware floating around that allows a D-Link DIR-655 to downgrade to pre-1.3x firmware (and also to other countries’ firmware), here are the results of my testing:
First I factory reset my router, it was running the 1.33NA b01 firmware, then I firmware upgraded it to the DIR655A4_FW131RUB10 firmware file that I will make available at the end, this is a modified version of an official Russian firmware, (apparently 2 bytes is all that has been changed).
Once this was complete I was running the modified firmware, as you can see it is still in English.
Then I was free to upgrade/downgrade to any firmware I wished, so I decided to try the official Australian Firmware 1.21 and this worked perfectly.
Here is the chklst.txt info on the firmware to prove it downgraded successfully.
Remember that this is the North American firmware so while it is compatible with other countries’ hardware it cannot be downgraded to pre 1.3x NA firmware OR to any other country’s firmware, so once you go NA, you can’t go back.
Please visit the D-Link forums post about it here before you install the firmware as this doesn’t have support from the usual places. Feedback can be left in this forum post.
Also let us know how it goes in the comments below.
Recently I moved my site to a new VPS run by me, the whole process went smoothly and after removing a few server specific .htaccess commands the site was up and running again.
I noticed however that the HTML5 video files that I have been using on a trial basis had stopped working with a big X in the middle of the video frame, but only in Firefox.
This indicates many possible problems with the video, some of which I could immediately dismiss as the file worked fine and other browsers such as Chrome had no issues playing it.
I remembered that it’s important to make sure the mime types are set correctly in apache, easily done with a modification of the .htaccess file in the site’s root directory, however I already had them in place, after trying different things I finally realised that nginx was serving the files directly so I did the following steps:
Open up the Nginx mime type configuration file, eg: /etc/nginx/mime.types
Paste these lines after the last video mime type, in my case it was avi:
Restart nginx, it should then serve ogg video correctly to Firefox users.