Bits


FRITZ!Box DynDNS mit eigener Domain über he.net

Möchte man seine FRITZ!Box bzw. das dahinter liegende Netzwerk von außerhalb erreichen, führt auf Dauer kein Weg daran vorbei die IP-Adresse der FRITZ!Box auf eine Domain zu mappen. Klassisch kann man hierfür Dienste wie DynDNS (nicht mehr kostenlos) oder NoIP nutzen. Auch AVM selbst bietet einen Service für seine FRITZ!Box Kunden namens MyFRITZ.

Alle Dienste haben jedoch den Nachteil, dass man (gratis) keine eigenen Domains verwenden kann. In diesem kleinen HowTo zeige ich, wie man sich kostenlos mit der eigenen Domain ein DynDNS zusammenbaut.
(mehr …)


Backup your Synology DSM 5.1 encrypted to remote server with Duply and Duplicity

I own a Synology DS713+ NAS for my local TimeMachine backups and to store media files like videos, music and photos.

It is a great NAS with an intuitive and clear webinterface. But the NAS is at home. The same place where my Macs are, which backup to the Synology. If I want to have a good backup strategy in case of fire, water or Godzilla, I have to put the data to another place, outsite of my home.

I have a server in a datacenter for some projects, which will be a good target for my remote backup. Synology have some tools in the DSM for remote Backups but just for AmazonS3, Glacier or rsync compatible servers. Sure I could use rsync, but I don’t want to have my private data unencyrypted on remote host.

For the remote server i use duply and duplicity to backup important data to a remote host and i love it. Wouldn’t it be nice to use that tool combination also for Synology backups? Here is the tutorial:

(mehr …)


Varnish IP forwarding to apache and nginx

When you install varnish-cache on your server, you will notice that the IP your backend receives is always your localhost (IPv4 127.0.0.1, IPv6 ::1).

That’s a problem for different cases:

  1. The log doesn’t contain IP information (e.g. if you use an analytic tool like webalizer that scans the log for unique users)
  2. Local statistic tools (like piwik) gets confused
  3. You can’t use the PHP variable $_SERVER[‚REMOTE_ADDR‘] because it always returns 127.0.0.1

To fix this here’s the solution for apache and nginx webservers:

(mehr …)


Tracking Tapatalk users with Piwik (Update)

Piwik is a nice open-source, self hostable tracking system like Google Analytics. It lists all the standart information like user browser, os, referral and associated metrics.

For the iPod-Forum i use this systems to get a chronological overview of the usage. I also use the integration of Tapatalk to get an optimized view for mobile users on iOS, Andorid and other mobile OS. What i missed is an integration of Tapatalk into the Piwik analytic tool, so i did it by myself.

All additional Code is used on your own risk! I used Piwik 1.12 to test it.

Tapatalk useragent
Thats the main problem. I hoped to get the mobile device out of the Tapatalk http useragent. I logged the useragents for a few hours, and received a lot of different agents:

Mozilla/5.0 Firefox/3.5.6 Tapatalk 2/2.0.3
Mozilla/5.0 (iPhone; CPU iPhone OS 5_0 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A334 Safari/7534.48.3 Tapatalk/1.16.0
Mozilla/5.0 Firefox/3.5.6 Tapatalk/
Mozilla/5.0 Firefox/3.5.6
Mozilla/5.0 Firefox/3.5.6 Tapatalk/2.4.10

There is just one version of tapatalk that sets the iPhone as device in useragent. The reason is the compatibility with common webservers according to Tapatalk developers. So I’m not 100% able to get the used deviced, but I’m able to filter the Tapatalk users out of the visitors using the useragent.

(mehr …)