Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for routing rules in Hiddify configuration #877

Open
web-studio-51 opened this issue May 14, 2024 · 1 comment
Open

Add support for routing rules in Hiddify configuration #877

web-studio-51 opened this issue May 14, 2024 · 1 comment

Comments

@web-studio-51
Copy link

Feature description

I am using Hiddify and I need to route traffic through a VPN only for specific websites. However, I encountered issues when trying to use the routing field in the configuration file.

{
"outbounds": [
{
"type": "vless",
"tag": "vpn",
"server": "XXX",
"server_port": XXX,
"uuid": "XXX",
"packet_encoding": ""
},
{
"type": "direct",
"tag": "direct"
}
],
"routing": {
"domainStrategy": "AsIs",
"rules": [
{
"type": "field",
"domain": [
"chatgpt.com"
],
"outboundTag": "vpn"
}
]
}
}
decode config: routing: json: unknown field "routing"

@web-studio-51
Copy link
Author

web-studio-51 commented May 14, 2024

It seems that the current version of Hiddify does not support the routing field, which is necessary for setting up domain-based traffic routing. This feature is crucial for users who want to selectively route traffic through a VPN.

Request:

Please add support for the routing field in Hiddify configuration or provide an alternative method to achieve domain-based traffic routing.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant