C.J. May lawndoc

The Publisher:

Collective Ink Ltd, Laurel House, Station Approach, Alresford, Hampshire, SO24 9JH, United Kingdom

The Licensee:

Herman Semenov <[email protected]> (Foreign Publisher and address)

Street: Terschellingsestraat 64 >

The problem

WSL2 uses a random network from the 172.16.0.0/12 RFC1918 private IP address block. And our VPN uses that address block, too, with a route metric of 1 (= most preferred.)

This breaks networking for WSL2. Meh!

The solution

While messing around with the interface/route metric of the VPN network may work around the problem, it also reduces the priority of the VPN. We do not really want this. Additionally, changing the interface metric does not seem to be permanent, so it requires more work when it breaks again.

Overview

Internet connection and DNS routing are broken from WSL2 instances, when some VPNs are active.

The root cause seems to be that WSL2 and the VPN use the same IP address block, and the VPN routing clobbers WSL2's network routing.

This problem is tracked in multiple microsoft/WSL issues including, but not limited to:

	You can create a GPO to test changing the default behavior of the following extensions to not behave as a script
	but rather as a benign text file opened in notepad.

	js
	wsh
	vbs
	wsc
	sct
	jse
	wsf

	wordlist created from original 41G stash via:

	grep -rohP '(?<=:).*$' \| uniq > breachcompilation.txt

	Then, compressed with:

	7z a breachcompilation.txt.7z breachcompilation.txt

	Size:

	#If this isn't the user using the shell, username@host will be displayed (if enabled)
	$DEFAULT_USER='Adalbert'

	#True to print username@host event if it's the default user
	$PRINT_DEFAULT_USER=$FALSE

	#Glyphs
	$SEGMENT_DELIMETER_GLYPH=[char]0xE0B0 # î‚°
	$PREV_CMD_FAIL_GLYPH=[char]0x2718 # âœ˜
	$BGTASK_GLYPH=[char]0x2699 # âš™

	#!/usr/bin/env python

	import ConfigParser
	import argparse
	import logging
	import os

	def type_loglevel(level):
	try:
	result = getattr(logging, level.upper())