Traffic
The Traffic feature is available in the following versions:
- PC / Desktop
- Mudfish Cloud VPN 5.17.8 or later
- Available on Linux and Windows. It is not available on macOS due to technical issues.
- Mudfish Cloud VPN 5.17.8 or later
- Router
- Mudfish Cloud VPN 2.7.0 or later

The Traffic feature allows you to control the traffic through Mudfish's nodes.
-
Web Traffic
Web traffic (TCP port 80, 443 and UDP port 443) can be controlled.
-
Custom Traffic
Control the traffic defined by the user.
Web Traffic
The Web Traffic option allows you to control the traffic.
-
Exclude web traffic
When this option is enabled, even if web traffic is forwarded to the Mudfish program due to the effects of items or Full VPN mode, it will not use the Mudfish node. It will connect directly from your computer.
Web traffic is considered to be on TCP ports 80, 443 and UDP port 443. Web traffic on other ports is not included in the exception rules.
Information!The exception rule applies to all traffic passing through the Mudfish. Please note that it applies to all item settings and modes.
-
Web Inspect feature
When Web Inspect is enabled, you can deliver web traffic for specific domains through Mudfish nodes, while other domains are connected directly from your computer.
-
Item's Built-In Domains
When this option is enabled, only web traffic to the domains specified in the item is delivered through Mudfish nodes, and other domains are connected directly from your computer. The default is Off.
TipEnable this option to help resolve Cloud / CDN issues. Only web traffic related to the game item will pass through Mudfish nodes, reducing traffic usage.
-
Custom Domains
Specify a list of domains to deliver web traffic only to these domains through Mudfish nodes. Other domains are connected directly from your computer.
-
Enter one domain per line.
-
Wildcard domains are supported. For example, you can enter it in the format like
*.example.com.If you enter it like
*.google.com, it will match domains likewww.google.com,mail.google.com,console.cloud.google.comand so on.
-
-
Allow QUIC traffic
When Web Inspect is enabled, QUIC traffic is blocked by default to ensure proper operation of the feature. When this option is enabled, QUIC traffic is allowed. The default is Off.
warningWhen this option is enabled, HTTP/HTTPS traffic delivered via the QUIC protocol may not be applied to the 'Web Inspect feature'.
-
Custom Traffic
The exception rules apply to IPv4 TCP / UDP traffic forwarded to Mudfish, regardless of individual item settings. ICMP and IPv6 traffic are not covered by these rules.
The Custom Traffic option allows you to control the traffic.
-
Exclude custom traffic
Use this option to connect directly from your computer instead of forwarding traffic for specific IPv4 address ranges or TCP / UDP ports through Mudfish nodes.
Enter one rule per line in the format
CIDR;port-list. If you do not need to specify ports, enter onlyCIDR.- Enter addresses in IPv4 CIDR notation, such as
8.8.8.0/24. For a single IP address, add/32, as in8.8.8.8/32. Use*to match all IPv4 addresses. - Prefix each port with an uppercase
Tfor TCP orUfor UDP. Separate multiple entries with commas (,), and specify ranges as inT8080-8090. Both the starting and ending ports are included in the range. - Do not include spaces in a rule. The current settings page accepts explicitly specified port numbers from 5 to 65535.
- If you omit the port list, also omit the semicolon (
;). The rule then applies to all TCP / UDP ports (0–65535) in the specified address range.
For example:
-
*;T80,T443,U443Exclude traffic on TCP ports 80 and 443 and UDP port 443 for all IPv4 addresses. Web traffic using other ports is not covered by this rule.
-
1.1.0.0/16;T8080-8090,U8080-8090Exclude traffic on TCP / UDP ports 8080 through 8090 in the IPv4
1.1.0.0/16address range. -
8.8.8.0/24Exclude traffic on all TCP / UDP ports in the IPv4
8.8.8.0/24address range. -
8.8.8.8/32;U53Exclude traffic on UDP port 53 for the IPv4 address
8.8.8.8.
- Enter addresses in IPv4 CIDR notation, such as