[GH-ISSUE #1381] [Windows] [Feature request] Add subdomain support in split tunneling settings #561

New issue

Closed

opened 2026-10-13 20:24:09 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-13 20:24:09 +00:00

Owner

Originally created by @Doroschenkov on GitHub (Jan 28, 2025).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1381

Good day!
I propose adding the ability to specify multiple subdomains in the split tunneling whitelist using a single entry.
Let me give you an example: I need to specify all the subdomains of the googlevideo.com resource, but the names of the third-level domains and their number are unknown in advance. Alternatively, from the user's point of view, it would be convenient to specify the following construction "*.googlevideo.com" so that the application sends to the tunnel everything that goes to any domain that ends with googlevideo.com.

This can be implemented by dynamically generating whitelists for the tunnel, however, this will require rebuilding the application and separating the modules directly responsible for maintaining the tunnel and for redirecting packets so that they do not depend on each other. This will require significant changes in the architecture and will increase the hardware requirements, but it will provide the user with more flexible functionality in configuring rules for directing traffic, and will also remove restrictions on editing split tunneling parameters when the tunnel has already been created.

And on the other hand, shouldn't it be initially possible to specify subdomains for a certain resource in order to direct everything related to it to the tunnel? As an ordinary person, it seems to me that such functionality is in high demand among VPN users

Originally created by @Doroschenkov on GitHub (Jan 28, 2025). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1381 Good day! I propose adding the ability to specify multiple subdomains in the split tunneling whitelist using a single entry. Let me give you an example: I need to specify all the subdomains of the googlevideo.com resource, but the names of the third-level domains and their number are unknown in advance. Alternatively, from the user's point of view, it would be convenient to specify the following construction "*.googlevideo.com" so that the application sends to the tunnel everything that goes to any domain that ends with googlevideo.com. This can be implemented by dynamically generating whitelists for the tunnel, however, this will require rebuilding the application and separating the modules directly responsible for maintaining the tunnel and for redirecting packets so that they do not depend on each other. This will require significant changes in the architecture and will increase the hardware requirements, but it will provide the user with more flexible functionality in configuring rules for directing traffic, and will also remove restrictions on editing split tunneling parameters when the tunnel has already been created. And on the other hand, shouldn't it be initially possible to specify subdomains for a certain resource in order to direct everything related to it to the tunnel? As an ordinary person, it seems to me that such functionality is in high demand among VPN users

bsakaguchi closed this issue

2026-10-13 20:24:09 +00:00

bsakaguchi referenced this issue

2026-10-13 21:16:44 +00:00

[PR #561] [MERGED] Bugfix/build_windows.bat fix #1919