Can STUN/TURN traffic for AVD vnet be routed directly to internet and not AzureFirewall/NVA?
I got a simple AVD pool with 4 hosts located in regionA. All hosts are in single vnetA which is globally peered with vnetB in regionB where AzureFirewall is. Route table is assigned to vnetA to route AVD traffic to internet and 0.0.0.0/0 to private IP of AF in vnetB.
With the ShortPath being made available for Public networks I left it turned on and added following ranges to route directly to internet from vnetA:
20.202.0.0/1613.107.17.41/3213.107.64.0/1852.112.0.0/1452.120.0.0/14
RTT is anywhere from 80 to 180ms for all clients that are local to the vnetA region where hosts are, which seems high.
Turning off ShortPath resulted in unexpected “GraphicsCapsNotReceived” errors which is a separate issue.
I got a simple AVD pool with 4 hosts located in regionA. All hosts are in single vnetA which is globally peered with vnetB in regionB where AzureFirewall is. Route table is assigned to vnetA to route AVD traffic to internet and 0.0.0.0/0 to private IP of AF in vnetB. With the ShortPath being made available for Public networks I left it turned on and added following ranges to route directly to internet from vnetA:20.202.0.0/1613.107.17.41/3213.107.64.0/1852.112.0.0/1452.120.0.0/14RTT is anywhere from 80 to 180ms for all clients that are local to the vnetA region where hosts are, which seems high. Turning off ShortPath resulted in unexpected “GraphicsCapsNotReceived” errors which is a separate issue. Read More