🎃 PAC: workaround to exempt private IP ranges in whitelist mode

[database64128]

Please follow the guide below

• You will be asked some questions, please read them carefully and answer honestly

• Put an x into all the boxes [ ] relevant to your pull request (like that [x])

• Use Preview tab to see how your pull request will actually look like

• Searched for similar pull requests

• Compiled the code with Visual Studio

• Require translation update

• Require document update (readme.md, wikipage, etc)

What is the purpose of your pull request?

• Bug fix
• Improvement
• New feature

---

Description of your pull request and other information

• Could match domains with similar patterns. But that's all we can do for now.
• No active developers use PAC mode. We are looking to deprecate PAC in favor of routing solutions.
• Closes 新版本PAC会代理局域网地址 #3002.

[darkflame0]

Missing localhost.

[chenshaoju]

@darkflame0

shadowsocks-windows/shadowsocks-csharp/Util/SystemProxy/Sysproxy.cs

Lines 22 to 44 in 589abf0

	private readonly static string[] _lanIP = {
	"<local>",
	"localhost",
	"127.*",
	"10.*",
	"172.16.*",
	"172.17.*",
	"172.18.*",
	"172.19.*",
	"172.20.*",
	"172.21.*",
	"172.22.*",
	"172.23.*",
	"172.24.*",
	"172.25.*",
	"172.26.*",
	"172.27.*",
	"172.28.*",
	"172.29.*",
	"172.30.*",
	"172.31.*",
	"192.168.*"
	};

[Loyalsoldier]

https://github.com/v2fly/geoip/blob/3f2e0c5d1febd8e0580fb986d6f76ebd3209a9ff/main.go#L28-L48

https://github.com/v2fly/domain-list-community/blob/16abfd4399b25f665f051ac337dfe9edec8e5fe4/data/private#L1-L31

BTW, should set geositePreferDirect to true by default, or use geosite with DNS resolving process to judge the IP.

[chenshaoju]

The quick test is passed, private IP (192.168.1.0/24 in my case) can working with "geositePreferDirect": false, and "geositePreferDirect": true, .

👍 Looks good to me, but someone else must approve.