Traffic forwarding

Match traffic, send it through an exit device, and optionally use a SOCKS5 upstream on that rule.

Use cases

Forward rules match traffic by source and destination. Matching traffic is handled by the selected exit device. Each rule can also have its own upstream SOCKS5 proxy for egress from that device. Unmatched traffic follows the default path.

The feature organizes traffic paths in your own network. It is not a public proxy service.

Creating a forward rule

Under Configuration → Forwarding, add a rule and set:

• Device: the source device where the rule applies.
• Source and destination conditions: the match scope. A destination condition can directly use an external Rule Set HTTPS URL: a .srs file, or a .mmdb file ending in #<two-letter country code>.
• Exit device: required and active in the same Network.
• Priority: lower integer values match first.
• Upstream SOCKS5 (optional): belongs to this rule. Enter host:port (or [addr]:port for IPv6) and credentials as required by the form. Passwords are not displayed after saving; submit a new password to rotate one.

Saving first shows rule conflicts and site-route overlaps. Adjust conditions or priority if active rules conflict. After saving, wait for affected devices to update and test the path with a new connection.

Editing and deleting

Open a rule's detail view to change its exit device, match conditions, priority, or upstream SOCKS5. Clearing that rule's upstream address makes the exit device connect directly to the destination. A failed upstream connection does not fall back to direct egress.

A Rule Set URL is a destination condition inside the rule. There are no separate Rule Set or proxy resources, and deleting a shared resource cannot change other rules. To stop using a source URL, edit or delete the rule that references it. The current runtime has one full-intercept detection engine and offers no engine selector.

Quick troubleshooting