Routing Rules Configuration

This guide will teach you how to configure advanced routing rules in Clash Party to optimize traffic routing and create custom rule sets for different scenarios.

📋 What are Routing Rules?

Routing rules determine how different types of traffic are handled by Clash Party. They allow you to:

• Route specific domains through different proxies
• Bypass local services and websites
• Block advertisements and malicious content
• Optimize performance for different applications

🎯 Rule Types

Domain-based Rules

1
2
3
4

rules:
  - DOMAIN-SUFFIX,google.com,PROXY
  - DOMAIN,www.example.com,DIRECT
  - DOMAIN-KEYWORD,youtube,PROXY

IP-based Rules

1
2
3
4

rules:
  - IP-CIDR,192.168.0.0/16,DIRECT
  - IP-CIDR,10.0.0.0/8,DIRECT
  - GEOIP,CN,DIRECT

Process-based Rules

1
2
3

rules:
  - PROCESS-NAME,chrome.exe,PROXY
  - PROCESS-NAME,steam.exe,DIRECT

⚙️ Common Rule Configurations

Basic Bypass Rules

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12

rules:
  # Local network
  - IP-CIDR,127.0.0.0/8,DIRECT
  - IP-CIDR,172.16.0.0/12,DIRECT
  - IP-CIDR,192.168.0.0/16,DIRECT
  - IP-CIDR,10.0.0.0/8,DIRECT
  
  # China mainland
  - GEOIP,CN,DIRECT
  
  # Default proxy
  - MATCH,PROXY

Gaming Optimization

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11

rules:
  # Steam
  - DOMAIN-SUFFIX,steampowered.com,DIRECT
  - DOMAIN-SUFFIX,steamcontent.com,DIRECT
  
  # Game platforms
  - DOMAIN-SUFFIX,battle.net,DIRECT
  - DOMAIN-SUFFIX,epicgames.com,DIRECT
  
  # Low latency for games
  - PROCESS-NAME,game.exe,LOW-LATENCY-PROXY

Ad Blocking Rules

1
2
3
4
5

rules:
  # Ad domains
  - DOMAIN-SUFFIX,doubleclick.net,REJECT
  - DOMAIN-SUFFIX,googleadservices.com,REJECT
  - DOMAIN-KEYWORD,advertisement,REJECT

🔧 Configuring Rules in Clash Party

Method 1: Profile Editor

1. Go to “Profiles” tab
2. Select your profile
3. Click “Edit” button
4. Navigate to “Rules” section
5. Add or modify rules
6. Save changes

Method 2: External Rule Sets

1. Create a separate rules file
2. Reference it in your main config:

1
2
3
4
5
6
7
8
9

rule-providers:
  custom-rules:
    type: http
    behavior: classical
    url: "https://example.com/rules.yaml"
    interval: 86400

rules:
  - RULE-SET,custom-rules,PROXY

📊 Rule Priority

Rules are processed from top to bottom. The first matching rule determines the action:

1. Domain rules (highest priority)
2. IP rules
3. Process rules
4. GEOIP rules
5. MATCH rule (catch-all, lowest priority)

🎯 Advanced Configurations

Load Balancing

 1
 2
 3
 4
 5
 6
 7
 8
 9
10

proxy-groups:
  - name: "LoadBalance"
    type: load-balance
    proxies:
      - "Server1"
      - "Server2"
    strategy: round-robin

rules:
  - DOMAIN-SUFFIX,example.com,LoadBalance

Fallback Groups

1
2
3
4
5
6
7
8

proxy-groups:
  - name: "Fallback"
    type: fallback
    proxies:
      - "Primary"
      - "Secondary"
    url: "http://www.gstatic.com/generate_204"
    interval: 300

URL Testing

1
2
3
4
5
6
7
8

proxy-groups:
  - name: "AutoSelect"
    type: url-test
    proxies:
      - "Server1"
      - "Server2"
    url: "http://www.gstatic.com/generate_204"
    interval: 300

🔍 Testing and Debugging

Check Rule Matching

1. Open “Logs” tab in Clash Party
2. Enable detailed logging
3. Visit websites to see which rules match
4. Adjust rules based on results

Performance Monitoring

1. Monitor connection speeds
2. Check latency for different rules
3. Optimize based on usage patterns

📚 Best Practices

Rule Organization

1. Group similar rules: Keep related rules together
2. Use comments: Document complex rules
3. Regular updates: Keep rule sets current
4. Test thoroughly: Verify rules work as expected

Performance Tips

1. Minimize rules: Use only necessary rules
2. Optimize order: Put frequently matched rules first
3. Use efficient patterns: Avoid overly complex regex
4. Cache DNS: Enable DNS caching for better performance

🛠️ Troubleshooting

Common Issues

1. Rules not working: Check rule syntax and order
2. Slow performance: Reduce rule complexity
3. DNS issues: Configure proper DNS settings
4. Conflicts: Resolve overlapping rules

Debugging Steps

1. Enable debug logging
2. Test individual rules
3. Check rule precedence
4. Verify proxy group configuration

📚 Next Steps

After mastering routing rules:

• Explore DNS configuration options
• Set up custom proxy groups
• Learn about traffic analysis
• Configure automatic rule updates

For support, check our FAQ or contact us.