#linux

So, I'm bringing a little Chromebox back into use on our home network to do some basic network services: dhcp, dns, and probably actually using it as a router (long story; tl;dr TekSavvy says they'll give you a /56 but then the VDSL modem they sell you can't do DHCPv6-PD properly). Anyway... I slapped Ubuntu 16.04 Xenial server on it and started plugging away at a couple of things. I opted to use ISC's newer Kea DHCP server rather than isc-dhcp-server. Little did I know that Ubuntu and systemd had other ideas…

As part of some mail filter testing, I needed to install ESET Mail Security onto a Debian 4.0 Etch VPS running on Virtuozzo. As a side-note, I found that the install package for ESET’s Gateway Filter, Mail Security, and File Server Security for Linux is all the exact same package; the functionality is basically just controlled/activated by means of licensing the appropriate component. Anyway, the download comes as an installation script called esets.i386.deb.bin. Running that script outputs a license agreement that you have to accept, produces a .deb package called esets.i386.deb, and outputs instructions on how to install the .deb package by using dpkg and import the license file. The .deb package installed just fine on another Debian test box, but when I attempted to run dpkg –i esets.i386.deb on the Virtuozzo VPS, tar squawked at me that it could not open /dev/stdin and the installation bailed: hostname:/usr/local/src/eset# dpkg -i esets-3.0.11.i386.deb Selecting previously deselected package esets. (Reading database ... 24639 files and directories currently installed.) Unpacking esets (from esets-3.0.11.i386.deb) ... Setting up esets (3.0.11) ... Unpacking esets modules ... tar: /dev/stdin: Cannot open: No such file or directory tar: Error is not recoverable: exiting now dpkg: error processing esets (--install): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: esets…

I had not previously played aroung much with MySQL replication, but got the chance to do so recently. I'm doing some testing with a new mail filter setup composed of amavisd-new, SpamAssassin, and some other SA modules running through Postfix on Debian Etch. The setup uses Maia Mailguard as a web front-end and management system, including per-user settings and quarantines. We're using MySQL for the database backend for Maia for storing quarantines, per-user settings and the like, but wanted to have a dual-MX setup with a secondary MX sitting in a remote site…