User Tools

Site Tools


sonicwall:google_meet_video_call_traffic_route

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
sonicwall:google_meet_video_call_traffic_route [2021/08/19 18:05] aperezsonicwall:google_meet_video_call_traffic_route [2021/08/19 18:05] (current) aperez
Line 4: Line 4:
 Option A: Option A:
  
-**With PBR to meet addresses: IPv4: 74.125.250.0/24 +**With PBR to meet addresses: IPv4: 74.125.250.0/24** 
-IPv6: 2001: 4860: 4864: 5 :: 0/64**+ 
 +**IPv6: 2001: 4860: 4864: 5 :: 0/64**
  
 A simple static routing entry specifies how to handle traffic that matches specific criteria, such as destination address, destination mask, gateway to forward traffic, the interface that gateway is located, and the route metric. This method of static routing satisfies most static requirements, but is limited to forwarding based only on destination addressing. SonicWall firewall (UTM) appliances running SonicOS Standard and Firmware 6.x support static routing. A simple static routing entry specifies how to handle traffic that matches specific criteria, such as destination address, destination mask, gateway to forward traffic, the interface that gateway is located, and the route metric. This method of static routing satisfies most static requirements, but is limited to forwarding based only on destination addressing. SonicWall firewall (UTM) appliances running SonicOS Standard and Firmware 6.x support static routing.
sonicwall/google_meet_video_call_traffic_route.1629414300.txt.gz · Last modified: 2021/08/19 18:05 by aperez

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki