Attila Györffy attilagyorffy

OPNsense + ProtonVPN + Wireguard

Published: 16 December 2022

Reference: https://docs.opnsense.org/manual/how-tos/wireguard-selective-routing.html

Goal: Set up one or more Wireguard connections from ProtonVPN on OPNsense, with policy based routing, and optional Killswitch.

I'm writing this guide first as a reference for my future self for when I inevitably forget how to do this, but also to help others out. I found there were not many guides on this specific configuration, particularly not with multiple concurrent connections, and these were some steps which were not at all obvious. I did begin with the guide in the official OPNsense documentation, but even that was missing info to make ProtonVPN work. If you are a pfSense user, it is very similar to OPNsense, and you should be able to follow along with some success, but I have not tested it myself.

%Q, %q, %W, %w, %x, %r, %s, %i

Perl-inspired notation to quote strings: by using % (percent character) and specifying a delimiting character.

Any single non-alpha-numeric character can be used as the delimiter, %[including these], %?or these?, %~or even these things~.

Strings

% or %Q

Rails 7 new features. Before and After

Add ComparisonValidator
PostgreSQL generated columns
PostgreSQL custom enum types
Add tracking of belongs_to association
association_previously_changed? method
Add invert_where method
Add associated method
Add missing method
Active Record Encryption

For Windows:

Download and install Putty
Connect your USB to UART adapter from your computer to your Nano Pi Neo Air (or any COM device)
Make sure you connect TX>RX and RX>TX (Sending/Receiving), otherwise both your devices are talking at the same time and neither one is being heard.
On Windows OS, pull up the Device Manager
- Run Windows (WinKey+R) and type in devmgmt.msc

Introduction

The MCP23017 is an I/O expander chip. It has 16 GPIO pins which you can control using an I2C interface using two pins from a Raspberry Pi, plus a power source and sink (which can also come from the Pi). It's not quite as simple as directly controlling the Pi's GPIO pins, but it's not complicated, either.

You need to install i2c-tools, which is probably in your distribution's package manager. You also need a kernel with I2C support; you might need to modprobe i2c-dev. It would presumably be possible to do without either of these things, and bitbang the I2C protocol over GPIO, but I don't understand the protocol well enough to try.

On pin numbering: if you like, you can refer to the datasheet for the MCP23017. There's a small dot in one corner of the chip, with a semi-circular cut-out at that end. The pin near

	#!/bin/bash
	tmp=$(mktemp -d)
	pushd "$tmp"

	iso=/Users/lloeki/Downloads/archlinux-2015.08.01-dual.iso
	echo "fixing disk"
	dd if=/dev/zero bs=2k count=1 of=tmp.iso
	dd if=$iso bs=2k skip=1 >> tmp.iso

	echo "mounting disk"

	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
	<!-- Generated by: TmTheme-Editor -->
	<!-- ============================================ -->
	<!-- app: http://tmtheme-editor.herokuapp.com -->
	<!-- code: https://github.com/aziz/tmTheme-Editor -->
	<plist version="1.0">
	<dict>
	<key>name</key>
	<string>Duotone Dark</string>

	/**
	* Shamelessly stolen from http://blog.jeansebtr.com/post/36590722386/async-loading-of-githubs-gists-without-jquery-31-loc
	*
	* Use like this: <gist data-username="brandonb927" data-id="4138162" data-file="gists2.js"><a href="https://gist.github.com/brandonb927/4138162#file_gists2.js">Gist</a></gist>
	* UPDATED 02/06/2013: Github implemented Namespaced Gists a few hours ago, which means gist.github.com/4149074 now redirects to gist.github.com/brandonb927/4149074 and I have updated the gist to reflect this new format
	*
	*/

	(function(){
	var gists = document.getElementsByTagName('gist');

	#!/bin/sh

	### BEGIN INIT INFO
	# Provides: mpd-autoplay
	# Required-Start: mpd
	# Required-Stop:
	# Should-Start:
	# Should-Stop:
	# Default-Start: 2 3 4 5
	# Default-Stop: 0 1 6

	#!/usr/bin/env ruby
	# encoding: UTF-8

	$VERBOSE = true # -w
	$KCODE = "U" if RUBY_VERSION < "1.9" # -KU

	require 'optparse'
	require 'socket'
	require 'fileutils'