CLI Guide - WatchGuard Technologies
CLI Guide - WatchGuard Technologies CLI Guide - WatchGuard Technologies
CHAPTER 3: Configuration Mode Commands schedule command WG#config WG(config)#schedule [-all| \ -mon|-tue|-wed|-thu|-fri|-sat|-sun] {hr:min-hr:min \ [hr:min-hr:min ][hr:min-hr:min ][hr:minhr:min ]} Effect Use this command to set up a schedule for use in the application of policies. Schedules can be set up for the same hours for every day or for different daily schedules, depending upon the arguments. Arguments Type a short, descriptive name for this schedule. This argument specifies whether this schedule is currently active or not. - This argument defines the days of the week. The values can either be noted as “all” for all seven days, or include any combination of days of the week–mon, tue, wed, thu, fri, sat, and sun. {hour:minute-hour:minute} This argument (which can be repeated for different blocks of time) should note a range of hours, such as “9:00-12:00” (which indicates 9:00am to Noon.) Be sure to wrap the range in curly brackets, as shown in the examples below. Hours must be converted to and noted in military time– according to the 24-hour clock. TIP A midnight start time should be entered as “0:00”. 62 WatchGuard Vclass 5.1
Top-level configuration mode commands Example WG(config)#schedule workdays -mon \ {8:00-12:00 13:00-19:00} (line break) - fri \ {9:00-12:00} enable WG(config)#schedule 24_7 -all {0:00- 24:00} service command WG#config WG(config)#service [+] \ Effect Records a new service entry (individual or group) for use in policies. The service must be noted as either a “single” service, a “range” of port numbers for a single service, or, as a “group” of existing related services. Arguments Enter the name of this new service or group. -single { } Use this argument to note the protocol and port number of a single service. -range { } Use this argument to note the protocol and two or more port numbers for a single service. -group { [ \ ]} WatchGuard Command Line Interface Guide 63
- Page 25 and 26: Getting started with the WatchGuard
- Page 27 and 28: Navigating through the CLI Getting
- Page 29 and 30: Arguments None. Example WG(admin)#e
- Page 31 and 32: Getting started with the WatchGuard
- Page 33 and 34: Installing and configuring a WatchG
- Page 35 and 36: Command Description Installing and
- Page 37 and 38: Installing and configuring a WatchG
- Page 39 and 40: CHAPTER 2 Administration Mode Comma
- Page 41 and 42: Administration mode commands plete
- Page 43 and 44: Administration mode commands 4 Clic
- Page 45 and 46: Administration mode commands #ex: e
- Page 47 and 48: crl command Administration mode com
- Page 49 and 50: Administration mode commands Merge
- Page 51 and 52: Administration mode commands Proces
- Page 53 and 54: Administration mode commands Shuts
- Page 55 and 56: CHAPTER 3 Configuration Mode Comman
- Page 57 and 58: abort command Top-level configurati
- Page 59 and 60: certificate command Top-level confi
- Page 61 and 62: Top-level configuration mode comman
- Page 63 and 64: interface command Top-level configu
- Page 65 and 66: Arguments None Example WG#config WG
- Page 67 and 68: [no] traffic command (log level) WG
- Page 69 and 70: Top-level configuration mode comman
- Page 71 and 72: Top-level configuration mode comman
- Page 73 and 74: Top-level configuration mode comman
- Page 75: as command Top-level configuration
- Page 79 and 80: Top-level configuration mode comman
- Page 81 and 82: Second level configuration mode com
- Page 83 and 84: Second level configuration mode com
- Page 85 and 86: Second level configuration mode com
- Page 87 and 88: Example Second level configuration
- Page 89 and 90: Second level configuration mode com
- Page 91 and 92: Second level configuration mode com
- Page 93 and 94: Second level configuration mode com
- Page 95 and 96: Second level configuration mode com
- Page 97 and 98: Second level configuration mode com
- Page 99 and 100: Second level configuration mode com
- Page 101 and 102: Second level configuration mode com
- Page 103 and 104: Second level configuration mode com
- Page 105 and 106: Arguments Second level configurati
- Page 107 and 108: Second level configuration mode com
- Page 109 and 110: Second level configuration mode com
- Page 111 and 112: Second level configuration mode com
- Page 113 and 114: Second level configuration mode com
- Page 115 and 116: Second level configuration mode com
- Page 117 and 118: Second level configuration mode com
- Page 119 and 120: Second level configuration mode com
- Page 121 and 122: Second level configuration mode com
- Page 123 and 124: Second level configuration mode com
- Page 125 and 126: Second level configuration mode com
CHAPTER 3: Configuration Mode Commands<br />
schedule command<br />
WG#config<br />
WG(config)#schedule<br />
[-all| \<br />
-mon|-tue|-wed|-thu|-fri|-sat|-sun]<br />
{hr:min-hr:min \<br />
[hr:min-hr:min ][hr:min-hr:min ][hr:minhr:min<br />
]}<br />
Effect<br />
Use this command to set up a schedule for use in<br />
the application of policies. Schedules can be set up<br />
for the same hours for every day or for different<br />
daily schedules, depending upon the arguments.<br />
Arguments<br />
<br />
Type a short, descriptive name for this schedule.<br />
<br />
This argument specifies whether this schedule is<br />
currently active or not.<br />
-<br />
This argument defines the days of the week. The<br />
values can either be noted as “all” for all seven<br />
days, or include any combination of days of the<br />
week–mon, tue, wed, thu, fri, sat, and sun.<br />
{hour:minute-hour:minute}<br />
This argument (which can be repeated for different<br />
blocks of time) should note a range of hours, such<br />
as “9:00-12:00” (which indicates 9:00am to Noon.)<br />
Be sure to wrap the range in curly brackets, as<br />
shown in the examples below. Hours must be<br />
converted to and noted in military time–<br />
according to the 24-hour clock.<br />
TIP<br />
A midnight start time should be entered as “0:00”.<br />
62 <strong>WatchGuard</strong> Vclass 5.1