Domain-based outbound policy not working

[PeterDedecker]

I want to impose bandwidth limitation on a certain service. Therefore I created an outbound policy where all traffic to domain.com is sent to a Speedfusion tunnel with bandwidth limitation. Tested with both “priority” as “enforced” algorithm. Both have Drop the traffic When No Connections are Available and "
Terminate Sessions on Connection Recovery" enabled. The LAN computer has the BR1 Pro as DNS-server.

When booting up both the BR1 and the PC, I see traffic to domain.com is actually sent right to the Cellular WAN (first priority) instead of the limited tunnel. So even if the tunnel is up, no redirection takes place. After rebooting the computer with the BR1 still up and running (with all its speedfusion tunnel) the traffic is sent through the tunnel correctly.

What could be wrong?

[Daniel_Eble]

Maybe this?

[Known Issue] [8.5.3] Firewall or Outbound Policies with Grouped Networks and Domain Rules Not Working

Ref.: #35401 Details: After upgrading to firmware version 8.5.3, the customer reported that the Firewall and Outbound Policy using a combination of Grouped Networks together with a domain-based criterion will no longer take effect. Example #1 - Outbound Policy: (Source = Grouped Networks | Destination = Domain Name) [image] Example #2 - Firewall Policy: (Source = Grouped Networks | Destination = Domain Name) [image] Example #3 - Grouped Networks with Domain Name classification (which wi…

[PeterDedecker]

Thanks. I’m not using grouped networks (source = any) but might give it a try. Thanks!

The weird thing however is that it works fine again after rebooting the computer. Don’t know if that’s also the case with the customer mentioned by @WeiMing