Howtos on Joachim Wiberg

HowTo play with SNMP

Mon, 04 Sep 2023 20:24:00 +0000

This mini HowTo describes how to use the SNMP client tools to retrieve human readable information from devices running an SNMP daemon. In the examples below mini-snmpd is used as the daemon and as client both the command line net-snmp tool and the snmpB GUI are used. Personally I use both Ubuntu and Debian, so the tools I use to download the clients will reflect that. See your respective UNIX distro’s help pages for how to install these client tools in your operating system.

Multicast HowTo

Sun, 28 May 2023 07:52:12 +0200

Introduction This HowTo attempts to give some insight into the basics of setting up multicast routing. Both static multicast routing, with SMCRoute, and dynamic multicast routing, with mrouted and pimd. For some use-cases, in particular link-local multicast, it may not be possible to use multicast routing, then I recommend trying out: Bridging networks, see bridge(8) or Linux bridge - how it works igmproxy, mcproxy, or OpenVPN in Layer-2, bridged mode Make sure to check out the FAQ for the most common problems.

HowTo: Set up Merecat with cgit

Thu, 09 Dec 2021 05:56:00 +0000

This post details how to set up cgit with Merecat httpd. It began as a GitHub issue report by Mr Alok G. Singh, who had run into problems setting it up, and ended up as a HowTo.

HowTo: Set up Merecat with Ikiwiki

Thu, 09 Dec 2021 05:51:00 +0000

This is a HowTo for setting up ikiwiki with Merecat httpd. First install ikiwiki $ sudo apt install ikiwiki libcgi-session-perl libcgi-formbuilder-perl Follow the steps to setup a new Wiki or Blog. In this example we set up a wiki in our ~/public_html: $ ikiwiki --setup /etc/ikiwiki/auto.setup ... Successfully set up wiki: url: http://localhost/~jocke/wiki srcdir: ~/wiki destdir: ~/public_html/wiki repository: ~/wiki.git To modify settings, edit ~/home.setup and then run: $ ikiwiki --setup ~/home.

HowTo: Build & Use My Projects

Tue, 05 Oct 2021 21:03:00 +0200

Ever so often someone new to Open Source show up on GitHub or in my inbox. It usually starts something like this:

“Hey, I just downloaded your software, what’s next?”
“Your software doesn’t work on my system!!!!”
“How can I do that weird-thing that fits my odd use-case?”
“I have zero documented experience but I think you should fix your build system!”

This HowTo is for you.

0. Short Version

Download a versioned archive from the project’s Releases page
Extract archive for v1.2.3 and change to its directory, cd archive-1.2.3/
./configure --help, or use something like the following …
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var && make && sudo make install

Some projects of mine are available in Debian/Ubuntu/FreeBSD, if you use that, please report bugs to them and not me. I have no control over what they do.

Cheers
/Joachim

HowTo: Add Multicast Routing to FreeBSD kernel

Sun, 01 Aug 2021 08:31:12 +0200

This is a very short blog post, mostly intended as a reminder to myself. Basically, there are two methods of adding multicast routing support to the FreeBSD kernel: Rebuild the kernel with options MROUTING Load the kernel module: kldload ip_mroute The kernel rebuild assumes the src.txz set was installed previously. cd /usr/src cd sys/amd64/conf cat GENERIC | sed 's/GENERIC$/MULTICAST/' > MULTICAST echo 'options MROUTING # Multicast routing' >> MULTICAST echo 'options PIM # Enable for pimd' >> MULTICAST cd - make kernel KERNCONF=MULTICAST reboot That’s it.

HowTo use NetBSD pre-built packages

Sat, 22 Aug 2020 21:39:00 +0100

Reminder to self: you need to set up the PKG_PATH to the correct FTP URI. Also, use the correct ARCH, otherwise the installer complains. Do not use amd64, but rather x86_64. Here it is, you’d think this be something the installer could set up a default for … PKG_PATH=http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/6.1.5/All/ or if you use the latest on an old ThinkPad T42: PKG_PATH=http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/9.0/All/ The simply pkg_add -v git Or so you might think!

HowTo: Set up Merecat with Let's Encrypt certificate

Wed, 15 Jul 2020 14:10:00 +0000

This is a HowTo for setting up Merecat httpd with Let’s Encrypt HTTPS certificates.

The upcoming v2.32 release of Merecat supports HTTPS as well as serving more than one Internet port. This is highly useful for those who want to serve both HTTPS and HTTP content.

Update: now with support for --webroot and HTTP-01 renewal!

Basic CGI in C with Merecat httpd

Mon, 05 Aug 2019 22:00:25 +0200

This post is a writeup of how to use basic CGI programs in Merecat httpd v2.32.

HowTo run pimd on FreeBSD

Sun, 27 Sep 2015 18:45:00 +0200

This is not a proper HowTo, more of a “note to self” after having created a setup to test pimd issue #57. For these notes the following virtual topology, running on Ubuntu 15.10 with Linux 4.2 and Qemu 2.3.0, is used: .--------. net1 .----. net2 .----. net3 .----------. | Sender |------| R2 |------| R3 |------| Receiver | '--------' '----' '----' '----------' The networks between the boxes are actually Linux bridge devices (br), on which you may have to disable IGMP/MLD snooping to get pimd to run smoothly.

HowTo run pimd on OpenBSD

Sun, 19 Jul 2015 00:32:00 +0200

This is an introduction to HowTo run pimd on OpenBSD. I keep it around mostly as a reminder to myself when testing new pimd releases, maybe someone else can make use of it as well. First of all, my sincere thanks to the OpenBSD team for, not just an awesome UNIX distribution, but also for their good taste in shipping a MULTICAST enabled kernel in the base distribution! On both NetBSD and FreeBSD there is a bit of work to get multicast support, which is one of the reasons for my not writing a HowTo for either of them atm.

HowTo Rebase without an origin

Wed, 27 Aug 2014 10:00:13 +0200

OK, so you’ve just been handed the task to integrate a big piece of corporate software and it’s nowhere near as done and ready as project management thinks. Of course you’ve already started chugging away at it, fixing bugs, refactoring code and wrapping it in neat containers to keep the changeset against the base SW small – you already know you’ll get another drop of the same stinking pieace of code in another six months, so you keep the changes small and track them in GIT with neatly formatted commit messages.