Dire Wolf is a sound card based modem for packet radio. It can be downloaded for Windows and Linux here: https://github.com/wb2osz/direwolf Although there is a reference to MacOS, there are no further build instructions for Mac. Google reveals some info: one site references an outdated version, the other one proposes to install the brew build/port environment to provide the cmake tool. Installing an environment like brew for just one tool, which actually is a build tool by itself, is .. well .. odd. So I decided to build Dire Wolf on Mac without any hacks or special tools. After using the result for some time,Read More →

I finally decided to go with Mac for Amateur Radio stuff. Time Machine and Spotlight make life so much more comfortable. Not to mention good sleep/wake performance, terminal with bash command line etc. Of course, there will always be some tools that are Windows only, so I use Parallels for this. Download your Windows tool on Mac with Safari, organise stuff in iCloud and then just double click the installer program from Mac. Parallels will start Windows (from pause, no booting involved) and run the installer. When it’s time to use it, launch the tool with Spotlight from Mac. IMHO this will work best withRead More →

So your site has a login page? Ever wondered how many “people” are knocking on your door? When I looked at the login attempts on my SSH front door, just shortly after new server deployment, I decided to change doors (ports..). SSH login attempts are in the logs and are fun to look at. But how about failed WordPress logins? First of all, they are not in the logs. But this can be fixed easily like this: —> create directory mu-plugins mkdir /var/www/<your site root>/wp-content/mu-plugins —> create file wp-fail2ban.php in this directory <?php function admin_login_failed_403() {     status_header( 403 ); } add_action( ‘wp_login_failed’, ‘admin_login_failed_403’Read More →

I described the installation of multi-site WordPress here with nginx webserver and php-fpm processes both running as user www-data. According to WordPress, the webserver should have read access to all data and only the WordPress user should have write access. The concept of a WordPress user relates to hosted environments. So how to implement these requirements on your own VPS? First of all, php-fpm supports the concept of pools. Each pool can run with an unique user, separate from the webserver user. So each site should run in a separate pool. This results in the following accounts: webserver: www-data user (default for nginx on debian) site 1:Read More →