General

I was setting up my FireTV (seems to be a TV with built-in FireStick functions). I was stuck, waiting for a verification code which never arrived on my phone. I was expecting an incoming text. I was wrong to expect that. I had gotten to the stage of logging in with my Amazon credentials and was getting told (and I paraphrase here): Because of the way your account is set up, your login

Happy New Year. This morning I received an email at 4:50 AM local time telling me that my camera system had been offline for 10 minutes. Based on that, I tried to access my internal monitoring system from outside. Nothing. Later emails indicated other external systems had issues connecting to the internal network. As I type this, I just arrived at home, I’m sitting on the couch and I’ve not touched the network

Last night, when I got my FreeBSD & ZFS based Time Capsule running, I had to connect my laptop to the same network as the server in question. This is not ideal. My usual work flow: connect to the WIFI, then connect to the VPN, then I get access to those services. These are different subnets, so the Netatalk broadcast does not traverse the switch. It stays inside so my laptop does not

You like tech. You know you like it. Do you know what part of tech you are most passionate about? I credit a Google employee for the following idea. It was told to me while I was at the FreeBSD Foundation booth at GHC 2016. The following is a relatively cheap project you can do in your spare time, weekends, and evenings. For the following tasks, blog about each step, in sufficient detail

I’m writing this to document the facts. I’ll leave adjectives and opinions to you. Greg Truskey, TruCo was hired to perform renovations which started in August 2015. The estimate was 11 weeks. He was on site from about 9am to 3:30pm. Arriving earlier or late was uncommon. On days he would not arrive, we would not be notified. It would be fine weather, and he would not be present. You will recall the

I noticed this on one FreeBSD server today: $ pkg -vv | grep url url: “pkg+http://services.unixathome.org/packages/103amd64-default-master-list/”, I decided: let’s use https, not http, there. After making the change (in my case, it was in /usr/local/etc/pkg/repos/local.conf, I tried upgraded packages, and it barfed: $ sudo pkg upgrade Updating local repository catalogue… Certificate verification failed for /C=IL/O=StartCom Ltd./OU=StartCom Certification Authority/CN=StartCom Class 2 IV Server CA 34401225432:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1191: Certificate verification failed for /C=IL/O=StartCom Ltd./OU=StartCom

My neighbours had a fire in July 2015. Today, the dumpster left. They were not home today when the dumpster was hauled off. I took these photos and the video for their enjoyment. * Dumpster loading * Dumpster being driven away If you want the copies of these, I have them on my phone and I’ll send them to you.

I upgraded my pfSense box to 2.3 last night. Here is what I got: # uname -a FreeBSD bast.int.unixathome.org 10.3-RELEASE FreeBSD 10.3-RELEASE #4 05adf0a(RELENG_2_3_0): Mon Apr 11 19:09:19 CDT 2016 root@factory23-amd64-builder:/builder/factory-230/tmp/obj/builder/factory-230/tmp/FreeBSD-src/sys/pfSense amd64 These are the package repos they are using (as taken from pkg -vv): Repositories: pfSense-core: { url : “pkg+http://firmware.netgate.com/pkg/pfSense_factory-v2_3_0_amd64-core”, enabled : yes, priority : 0, mirror_type : “SRV”, signature_type : “FINGERPRINTS”, fingerprints : “/usr/local/share/pfSense/keys/pkg” } pfSense: { url : “pkg+http://firmware.netgate.com/pkg/pfSense_factory-v2_3_0_amd64-pfSense_factory-v2_3_0”, enabled