I’ve been struggling with my dd-wrt setup lately. So I started looking around for potential alternatives. One thought was to use a Raspberry Pi as router, but I was worried about its performance. So I did a few tests.
Posts tagged ‘linux’
All of my data is stored on my NAS, from where it is automatically backed up daily. But doing photo-editing on a remote file was slow, especially over WiFi and/or VPN. So I decided to store all photo’s locally, but without loosing the automatic backups. I solved this problem with a Launchd agent to watch the directory for changes (and run every hour anyway), and rsync for the actual transfer.
Additional challanges were that user permissions needed to be synced across as well. (Usernames did match on both machines, but UIDs did not)
I had some difficulties creating a bootable USB stick on MacOSX. Most guides use
dd to put the image on the stick, but this failed to boot on my linux machine…
This article was very helpful, and confirms what I was thinking. The main difference is that this method makes a MBR partition table, adds MBR boot code and puts the data onto the first partition (as opposed to putting the data straight onto the disk).
I have a home server with a Western Digital Caviar Green WD20EARS 2TB disk in it. Recently, I’ve come across this post explaining that this drive’s IntelliPark parks the head after only 8 seconds of being idle. Linux by default caches disk access for 30 seconds on an idle system, leading to up to 120 load/unload cycles per hour!
ZSH has some pretty nifty TAB-completion. But I found the git completion to be slow, especially on large repo’s. I wasn’t the only one. Some suggest to disable the context-aware completion completely, but I prefer to this solution which just upgrades the completion logic to the latest version.
I was a bit afraid that getting an UMTS USB stick to work under Linux would be an impossible task. Turns out to be reasonably simple. These notes are for a Huawei K4505 HSPA+ USB stick, as provided by Proximus (Vodaphone group).
As mentioned before, when switching to IPv6 (or more realistically, to dual stack) one of the things that might not work out of the box is VPNs. I decided to put some effort in it to get it to work anyway.
Together with most of the , we tested IPv6 on World IPv6 day last week. I won’t go into details on what IPv6 is and why it’s important. Although IPv6 has been tested intensely in isolated networks, this is the first time it was tested on such a large scale. Technically, the participants would just add AAAA-records for their websites to DNS. This small change causes a huge effect. Since most browsers are configured to prefer IPv6 AAAA-records over IPv4 A-records, this causes all IPv6-connected users to suddenly connect over IPv6 instead of IPv4.
For the most part, this major changeover happened without as much of a hitch. In fact, if I hadn’t known it was World IPv6 day, I wouldn’t have noticed anything. But I’m not a normal web-user, so I did notice some issues.
I regularly watch log files in real time using the highly appreciated tail -f command. But I usually find myself manually inserting newlines to give a visual clue of which log-lines happened together. Obviously the timestamps in the lines tell you the full story, but it’s not that visually appealing.
I assume I don’t have to introduce the concept of spam. Fighting spam can be done on different levels. A first line of defense is the mail server receiving them. There are several checks it can perform. Here is my configuration of Postfix.