wen-long

I'm using [PORT]net/zerotier[/PORT] for quite some time as a way of getting to my systems from other networks very happily. It works in airports, cafes, and all the usual hostile places we travel to.

It provides a L2 encrypted mesh (a bit like VXLAN I suppose) via a tap interface.

What I'd like to do is to use the ZT network as a VPN - routing all traffic from my FreeBSD laptop and phone through the zerotier layer out to my appointed ZT "VPN Gateway". Basically, translating the linux doc here: https://support.zerotier.com/knowledgebase.php?entry=show&search-for=full&article=ZWFhNWMyMTZjODY1ODcwNmFhZmJjYmRhN2I5MjRhOGQ_ -- into FreeBSD config. BTW https://www.zerotier.com/manual.shtml has a lot of background detail if you're interested.I can get the iphone working, but not the laptop.

What works after configuring zerotier to provide the "default route" is different on each device:

the iphone works
an apple imac works

From theme: Programming

Microservices for Java Developers: A Hands-On Introduction to Frameworks and Containers

http://www.oreilly.com/programming/free/files/microservices-for-java-developers.pdf
http://www.oreilly.com/programming/free/files/microservices-for-java-developers.epub
http://www.oreilly.com/programming/free/files/microservices-for-java-developers.mobi

Modern Java EE Design Patterns

http://www.oreilly.com/programming/free/files/modern-java-ee-design-patterns.pdf
http://www.oreilly.com/programming/free/files/modern-java-ee-design-patterns.epub
http://www.oreilly.com/programming/free/files/modern-java-ee-design-patterns.mobi

Object-Oriented vs. Functional Programming

Exporting your 2FA tokens from Authy to transfer them into another 2FA application

IMPORTANT - Update regarding deprecation of Authy desktop apps

Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.

And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.

If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

	set firewall options mss-clamp interface-type all
	set firewall options mss-clamp mss 1380
	set firewall options mss-clamp6 interface-type all
	set firewall options mss-clamp6 mss 1360

	### KERNEL TUNING ###

	# Increase size of file handles and inode cache
	fs.file-max = 2097152

	# Do less swapping
	vm.swappiness = 10
	vm.dirty_ratio = 60
	vm.dirty_background_ratio = 2

	udp://public.popcorn-tracker.org:6969/announce
	http://182.176.139.129:6969/announce
	http://5.79.83.193:2710/announce
	http://91.218.230.81:6969/announce
	udp://tracker.ilibr.org:80/announce
	http://atrack.pow7.com/announce
	http://bt.henbt.com:2710/announce
	http://mgtracker.org:2710/announce
	http://mgtracker.org:6969/announce
	http://open.touki.ru/announce.php

	// code courtesy of Toby team

	chrome.storage.local.get("state", o => (
	((f, t) => {
	let e = document.createElement("a");
	e.setAttribute("href", `data:text/plain;charset=utf-8,${encodeURIComponent(t)}`);
	e.setAttribute("download", f);
	e.click();
	})(`TobyBackup${Date.now()}.json`, o.state)
	));

	isolation.tools.getPtrLocation.disable = "TRUE"
	isolation.tools.setPtrLocation.disable = "TRUE"
	isolation.tools.setVersion.disable = "TRUE"
	isolation.tools.getVersion.disable = "TRUE"
	monitor_control.disable_directexec = "TRUE"
	monitor_control.disable_chksimd = "TRUE"
	monitor_control.disable_ntreloc = "TRUE"
	monitor_control.disable_selfmod = "TRUE"
	monitor_control.disable_reloc = "TRUE"
	monitor_control.disable_btinout = "TRUE"

	127.0.0.1 api.ad.xiaomi.com
	127.0.0.1 sdkconfig.ad.xiaomi.com
	127.0.0.1 ad.mi.com
	127.0.0.1 ad.xiaomi.com
	127.0.0.1 ad1.xiaomi.com

	127.0.0.1 adv.sec.miui.com
	127.0.0.1 test.ad.xiaomi.com
	127.0.0.1 new.api.ad.xiaomi.com