"With OpenClash enabled on my soft router, UU Accelerator stops working," and "Games won't connect in Fake-IP mode, but everything works fine with Clash disabled"—these two problems have plagued countless soft router users.

The core reason for the conflict between OpenClash and UU Accelerator in Fake-IP mode is straightforward: both are vying for control of network traffic. UU Accelerator needs to hijack game traffic for acceleration, while OpenClash in Fake-IP mode also hijacks DNS requests and network traffic. With both proxy tools competing for traffic simultaneously, the result is that game traffic is intercepted by OpenClash, rendering UU Accelerator ineffective—or both become unusable.

However, this conflict is not insurmountable. Based on the practical experience of multiple users, OpenClash and UU Accelerator can coexist perfectly well with proper configuration. Below are three verified solutions, listed from simplest to most complex.

Solution 1: Fake-IP-Filter Whitelist—Allowing specific domains to bypass Clash

This is the most direct method. The core logic is: In OpenClash's Fake-IP-Filter, game-related domains are whitelisted, causing DNS requests for these domains to return real IPs instead of fake IPs. Once real IPs are returned, traffic won't be hijacked by Clash, and UU Accelerator can take over normally.

In the OpenClash management interface, go to "Overwrite Settings" → "DNS Settings," find "Fake-IP-Filter," set it to blacklist mode, and then enter the domains that need to be bypassed.

For example, for *Monster Hunter: Wildlands*, you need to enter `+.wilds.monsterhunter.com` to connect normally. If errors still occur after UU Accelerator, you may also need to add domains like `+.playfabapi.com` and `+.cloudapp.azure.com`. The same applies to games like *Valorant*; you need to find the game-related domains and add them one by one.

Advantages: Simple configuration, no firewall modifications required. Disadvantages: Requires finding game-related domains one by one, which is time-consuming.

Option 2: Custom Firewall Rules – Allow Real IP Traffic to Skip Clash

If you don't want to search for domains one by one, you can use firewall rules for a permanent solution. The core logic is to allow traffic destined for non-Fake-IP network segments (198.18.0.0/16) to directly bypass the OpenClash chain.

In OpenClash's "Plugin Settings" → "Developer Options," add the following two custom firewall rules:

iptables -t nat -I openclash 1 ! -d 198.18.0.0/16 -j RETURN

iptables -t mangle -I openclash 1 ! -d 198.18.0.0/16 -j RETURN

Note: `198.18.0.0/16` needs to be replaced with your actual Fake-IP address range. After the rules take effect, real IP traffic (such as direct game connection traffic) will not be hijacked by Clash, but will be handled by UU Accelerator.

If the rules don't work, try this: First start OpenClash, then start UU Accelerator. After both are running, execute these two commands. If it still doesn't work, check if UU Accelerator's firewall mark rule has a higher priority than OpenClash's—if UU's priority is higher, game traffic will be marked and handled by UU first.

Advantages: One-time configuration, covering all games. Disadvantages: Requires some command-line skills.

Solution 3: Switch to TUN Mode + Adjust Startup Order

If the above two methods don't work, try switching to TUN mode.

In OpenClash's "Mode Settings," switch the running mode to Fake-IP (TUN-Hybrid) mode, and select "Hybrid (Meta Kernel Only)" for the network stack. Enable UDP forwarding and turn on DNS hijacking.

TUN mode handles UDP traffic better. However, note that TUN mode may have bugs in some firmware versions. If you encounter problems, try updating OpenClash to the latest version or changing the firmware version.

The startup order is also crucial. Multiple users have confirmed through testing that enabling OpenClash first, followed by UU Accelerator, will not cause conflicts. Conversely, enabling UU Accelerator first and then OpenClash significantly increases the probability of conflict.

Other Useful Tips

Enable "Bypass Mainland China IPs": Some users have reported that enabling this function allows UU Accelerator to work normally. However, note that this function may have bugs in some versions. If access to domestic websites is abnormal after enabling it, try downgrading your OpenClash version.

UU Accelerator "Width and Dimension Only": Some users mentioned in the OpenClash discussion forum that UU Accelerator has a "Width and Dimension Only" option, which can resolve conflict issues. The specific name may vary depending on the version; you can find an option similar to "Compatibility Mode" in UU settings.

Device-Level Traffic Splitting: If all the above methods are ineffective, the last resort is to completely prevent the game device from using OpenClash. In OpenClash's "Access Control," add the game host's IP or MAC address to the "LAN Devices Not Using Proxy" list. Gaming devices connect directly to the main router via UU Accelerator, while other devices use OpenClash proxy. The drawback is that gaming devices cannot simultaneously use Clash's VPN functionality.

The conflict between OpenClash and UU Accelerator in Fake-IP mode stems from their struggle for traffic control. There are essentially three solutions: bypass specific traffic from Clash (Fake-IP Filter), bypass real IP traffic from Clash (firewall rules), or use a different traffic handling method (TUN mode).

It's recommended to try the following order: first try solution one (Fake-IP Filter), then solution two (firewall rules), and finally solution three (TUN mode + adjusting the startup order).

If you still can't get it working—the last suggestion: gaming devices connect directly to the main router via UU Accelerator, while other devices use OpenClash. It's a bit more complicated, but at least it will run stably.