Hi @JakubN, what is the traffic type of your data? As long as it is a bidirectional stream (e.g. TCP, or some UDP streams that have control packets), this is already supported without the need of Outbound Policy on FusionHub.
FusionHub is designed to route traffics according to remote PepVPN peer’s choice, any packets in “outgoing” direction will be routed to where the “incoming” packets come from.
Say if the PC is initiating the connection, as UBR (with outbound policy) routed the packets via sub-tunnel 2 to the FusionHub, when Camera replies back, the reply packet will be forwarded to sub-tunnel 2 by FusionHub without the need of Outbound Policy, because the last incoming packet comes from sub-tunnel 2.
So in another case, if the first packet comes from another direction, from Camera to PC, the first packet sending to PC will go to sub-tunnel 1 (the default tunnel), but when the PC send out reply packets in the same session, UBR will route the reply packet to sub-tunnel 2 based on Outbound Policy, and FusionHub will update the record, any further packets coming from the Camera to PC later on, will be forwarded to sub-tunnel 2. As a result, only those packets before the first reply from PC will be sent via sub-tunnel 1, all packets after the reply will be using sub-tunnel 2 as defined in UBR’s Outbound Policy.