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:
| #!/bin/sh | |
| if pwd | grep /mnt/c > /dev/null; then | |
| exec git.exe "$@" | |
| else | |
| exec /usr/bin/git "$@" | |
| fi |
| package main | |
| import ( | |
| "database/sql" | |
| "encoding/json" | |
| "fmt" | |
| "log" | |
| "time" | |
| "github.com/go-sql-driver/mysql" |
| #198.47.104.134 m10.music.126.net | |
| 198.47.104.134 m3.music.126.net | |
| 123.58.180.105 m6.music.126.net | |
| 174.35.52.182 m9.music.126.net | |
| 174.35.25.7 m1.music.126.net | |
| 220.243.234.5 m4.music.126.net | |
| 174.35.24.139 m7.music.126.net | |
| 198.47.104.134 m2.music.126.net | |
| 123.58.180.106 m5.music.126.net | |
| 220.243.234.8 m8.music.126.net |
| const crypto = require('crypto') | |
| // larger numbers mean better security, less | |
| const config = { | |
| // size of the generated hash | |
| hashBytes: 32, | |
| // larger salt means hashed passwords are more resistant to rainbow table, but | |
| // you get diminishing returns pretty fast | |
| saltBytes: 16, | |
| // A selected HMAC digest algorithm specified by digest is applied to derive |
