stickertape
New Around Here
I note that the following enhancement is coming in 388.2.
I was hoping someone could help translate the above note for me based on my scenario below.
I have a site to site Wireguard tunnel set up. LAN client traffic that is destined for the LAN subnet at the "other" site is sent via the established WG tunnel interface. This requires a VPN Director rule on the WG client side (we can call it Site B) to route traffic destined for the LAN subnet at Site A via the WG tunnel.
In the above example, does this mean that all of my devices from both sites won't be able to take advantage of flow cache? ie. the clients will be either enabled or disabled? Or alternatively, does this mean that only packets traversing the WG interface will bypass flow cache and most traffic will not bypass flow cache?
This is most excellent news!- CHANGED: Implemented Flow Cache bypass for WireGuard
(backport from upstream). WireGuard can
now be used with Flow Cache enabled,
however note that clients sent through
a WG tunnel in VPN Director will still not
be able to use Flow Cache, however other
non-redirected clients will.
I was hoping someone could help translate the above note for me based on my scenario below.
I have a site to site Wireguard tunnel set up. LAN client traffic that is destined for the LAN subnet at the "other" site is sent via the established WG tunnel interface. This requires a VPN Director rule on the WG client side (we can call it Site B) to route traffic destined for the LAN subnet at Site A via the WG tunnel.
In the above example, does this mean that all of my devices from both sites won't be able to take advantage of flow cache? ie. the clients will be either enabled or disabled? Or alternatively, does this mean that only packets traversing the WG interface will bypass flow cache and most traffic will not bypass flow cache?