[GH-ISSUE #1607] Regex on split tunelling #667

Open
opened 2026-10-13 20:26:11 +00:00 by bsakaguchi · 5 comments
Owner

Originally created by @myagizmaktav on GitHub (May 22, 2025).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1607


Describe the bug
Split tunneling functionality appears to only accept explicit IP addresses or hostnames, and does not support the use of wildcard characters (e.g., *) for broader domain matching within application exclusion rules. This prevents users from easily specifying entire services or subdomains for split tunneling.

To Reproduce
Steps to reproduce the behavior:

  1. Go to the split tunneling configuration section of the application.
  2. Attempt to add a rule to exclude a domain using a wildcard, for example, *.discord.gg or *.discord.com.
  3. Observe that the input field either rejects the wildcard syntax or the rule does not function as expected, meaning traffic to subdomains of discord.gg or discord.com still routes through the VPN.

Expected behavior
The split tunneling feature should allow the use of wildcard characters (e.g., *) in domain specifications, effectively acting as a form of regex, to enable easier and more comprehensive exclusion of applications or services (e.g., *.discord.gg, *.discord.com). When such a rule is applied, all traffic matching the wildcard pattern should be routed outside the VPN.

Log files
[Please attach relevant log files here if available, demonstrating the attempt to add a wildcard rule and any resulting errors or unexpected routing behavior.]

Screenshots
[If applicable, add screenshots showing the input field rejecting the wildcard or the rule being entered but not functioning correctly.]

Desktop (please complete the following information):

  • OS: [e.g. Windows 10]
  • Version [e.g. 2.1.2]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Version [e.g. 2.1.2]

Server (please complete the following information):

  • OS: [e.g. Ubuntu 22.04]

Additional context
The current limitation to only explicit IP addresses or hostnames makes managing split tunneling rules cumbersome, especially for applications or services that utilize multiple subdomains. Allowing wildcard matching would significantly improve usability and flexibility.

Originally created by @myagizmaktav on GitHub (May 22, 2025). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1607 --- **Describe the bug** Split tunneling functionality appears to only accept explicit IP addresses or hostnames, and does not support the use of wildcard characters (e.g., `*`) for broader domain matching within application exclusion rules. This prevents users from easily specifying entire services or subdomains for split tunneling. **To Reproduce** Steps to reproduce the behavior: 1. Go to the split tunneling configuration section of the application. 2. Attempt to add a rule to exclude a domain using a wildcard, for example, `*.discord.gg` or `*.discord.com`. 3. Observe that the input field either rejects the wildcard syntax or the rule does not function as expected, meaning traffic to subdomains of discord.gg or discord.com still routes through the VPN. **Expected behavior** The split tunneling feature should allow the use of wildcard characters (e.g., `*`) in domain specifications, effectively acting as a form of regex, to enable easier and more comprehensive exclusion of applications or services (e.g., `*.discord.gg`, `*.discord.com`). When such a rule is applied, all traffic matching the wildcard pattern should be routed outside the VPN. **Log files** [Please attach relevant log files here if available, demonstrating the attempt to add a wildcard rule and any resulting errors or unexpected routing behavior.] **Screenshots** [If applicable, add screenshots showing the input field rejecting the wildcard or the rule being entered but not functioning correctly.] **Desktop (please complete the following information):** - OS: [e.g. Windows 10] - Version [e.g. 2.1.2] **Smartphone (please complete the following information):** - Device: [e.g. iPhone6] - OS: [e.g. iOS8.1] - Version [e.g. 2.1.2] **Server (please complete the following information):** - OS: [e.g. Ubuntu 22.04] **Additional context** The current limitation to only explicit IP addresses or hostnames makes managing split tunneling rules cumbersome, especially for applications or services that utilize multiple subdomains. Allowing wildcard matching would significantly improve usability and flexibility.
Author
Owner

@rasolAAaa commented on GitHub (May 22, 2025):

درود بر شما و تمامی دست اندرکاران برنامه بسیار زیبا قشنگ خوشگل از راهنمایی
که فرمودید من استفاده مکنم

در تاریخ پنجشنبه 22 مهٔ 2025،‏ 5:57 Mehmet Yağız Maktav <
@.***> نوشت:

myagizmaktav created an issue (amnezia-vpn/amnezia-client#1607)
https://github.com/amnezia-vpn/amnezia-client/issues/1607

Describe the bug
Split tunneling functionality appears to only accept explicit IP addresses
or hostnames, and does not support the use of wildcard characters (e.g., *)
for broader domain matching within application exclusion rules. This
prevents users from easily specifying entire services or subdomains for
split tunneling.

To Reproduce
Steps to reproduce the behavior:

  1. Go to the split tunneling configuration section of the application.
  2. Attempt to add a rule to exclude a domain using a wildcard, for
    example, *.discord.gg or *.discord.com.
  3. Observe that the input field either rejects the wildcard syntax or
    the rule does not function as expected, meaning traffic to subdomains of
    discord.gg or discord.com still routes through the VPN.

Expected behavior
The split tunneling feature should allow the use of wildcard characters
(e.g., *) in domain specifications, effectively acting as a form of
regex, to enable easier and more comprehensive exclusion of applications or
services (e.g., *.discord.gg, *.discord.com). When such a rule is
applied, all traffic matching the wildcard pattern should be routed outside
the VPN.

Log files
[Please attach relevant log files here if available, demonstrating the
attempt to add a wildcard rule and any resulting errors or unexpected
routing behavior.]

Screenshots
[If applicable, add screenshots showing the input field rejecting the
wildcard or the rule being entered but not functioning correctly.]

Desktop (please complete the following information):

  • OS: [e.g. Windows 10]
  • Version [e.g. 2.1.2]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Version [e.g. 2.1.2]

Server (please complete the following information):

  • OS: [e.g. Ubuntu 22.04]

Additional context
The current limitation to only explicit IP addresses or hostnames makes
managing split tunneling rules cumbersome, especially for applications or
services that utilize multiple subdomains. Allowing wildcard matching would
significantly improve usability and flexibility.

—
Reply to this email directly, view it on GitHub
https://github.com/amnezia-vpn/amnezia-client/issues/1607, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BIQMEYTCU3V5VPQI5I3PBA327URYFAVCNFSM6AAAAAB5UWNZUOVHI2DSMVQWIX3LMV43ASLTON2WKOZTGA4DCNZXGM4TQOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

<!-- gh-comment-id:2899649017 --> @rasolAAaa commented on GitHub (May 22, 2025): درود بر شما و تمامی دست اندرکاران برنامه بسیار زیبا قشنگ خوشگل از راهنمایی که فرمودید من استفاده مکنم در تاریخ پنجشنبه 22 مهٔ 2025،‏ 5:57 Mehmet Yağız Maktav < ***@***.***> نوشت: > *myagizmaktav* created an issue (amnezia-vpn/amnezia-client#1607) > <https://github.com/amnezia-vpn/amnezia-client/issues/1607> > ------------------------------ > > *Describe the bug* > Split tunneling functionality appears to only accept explicit IP addresses > or hostnames, and does not support the use of wildcard characters (e.g., *) > for broader domain matching within application exclusion rules. This > prevents users from easily specifying entire services or subdomains for > split tunneling. > > *To Reproduce* > Steps to reproduce the behavior: > > 1. Go to the split tunneling configuration section of the application. > 2. Attempt to add a rule to exclude a domain using a wildcard, for > example, *.discord.gg or *.discord.com. > 3. Observe that the input field either rejects the wildcard syntax or > the rule does not function as expected, meaning traffic to subdomains of > discord.gg or discord.com still routes through the VPN. > > *Expected behavior* > The split tunneling feature should allow the use of wildcard characters > (e.g., *) in domain specifications, effectively acting as a form of > regex, to enable easier and more comprehensive exclusion of applications or > services (e.g., *.discord.gg, *.discord.com). When such a rule is > applied, all traffic matching the wildcard pattern should be routed outside > the VPN. > > *Log files* > [Please attach relevant log files here if available, demonstrating the > attempt to add a wildcard rule and any resulting errors or unexpected > routing behavior.] > > *Screenshots* > [If applicable, add screenshots showing the input field rejecting the > wildcard or the rule being entered but not functioning correctly.] > > *Desktop (please complete the following information):* > > - OS: [e.g. Windows 10] > - Version [e.g. 2.1.2] > > *Smartphone (please complete the following information):* > > - Device: [e.g. iPhone6] > - OS: [e.g. iOS8.1] > - Version [e.g. 2.1.2] > > *Server (please complete the following information):* > > - OS: [e.g. Ubuntu 22.04] > > *Additional context* > The current limitation to only explicit IP addresses or hostnames makes > managing split tunneling rules cumbersome, especially for applications or > services that utilize multiple subdomains. Allowing wildcard matching would > significantly improve usability and flexibility. > > — > Reply to this email directly, view it on GitHub > <https://github.com/amnezia-vpn/amnezia-client/issues/1607>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/BIQMEYTCU3V5VPQI5I3PBA327URYFAVCNFSM6AAAAAB5UWNZUOVHI2DSMVQWIX3LMV43ASLTON2WKOZTGA4DCNZXGM4TQOI> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >
Author
Owner

@myagizmaktav commented on GitHub (May 22, 2025):

English pls.

<!-- gh-comment-id:2900919053 --> @myagizmaktav commented on GitHub (May 22, 2025): English pls.
Author
Owner

@pr3ci0u5 commented on GitHub (Sep 18, 2025):

Please we need this so bad!!! This should be a basic functionality. Voting for this ticket +++

<!-- gh-comment-id:3309603977 --> @pr3ci0u5 commented on GitHub (Sep 18, 2025): Please we need this so bad!!! This should be a basic functionality. Voting for this ticket +++
Author
Owner

@Apostlerus commented on GitHub (Jun 30, 2026):

If I'd known this feature didn't exist, I would never have bought your app. -_- A one-year-old ticket... impressive.

<!-- gh-comment-id:4847593047 --> @Apostlerus commented on GitHub (Jun 30, 2026): If I'd known this feature didn't exist, I would never have bought your app. -_- A one-year-old ticket... impressive.
Author
Owner

@myagizmaktav commented on GitHub (Jul 2, 2026):

Guys this project open source write with ai then test it then make a pr.

<!-- gh-comment-id:4867063964 --> @myagizmaktav commented on GitHub (Jul 2, 2026): Guys this project open source write with ai then test it then make a pr.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
amnezia-vpn/amnezia-client#667
No description provided.