Comments In Configuration Files Or Shell Scripts - ZyXEL Communications ZyWALL USG 200 Series User Manual

Chapter 52 File Manager
These files have the same syntax, which is also identical to the way you run CLI
commands manually. An example is shown below.
Figure 583 Configuration File / Shell Script: Example
# enter configuration mode
configure terminal
# change administrator password
username admin password 4321 user-type admin
# configure ge3
interface ge3
ip address 172.23.37.240 255.255.255.0
ip gateway 172.23.37.254 metric 1
exit
# create address objects for remote management / to-ZyWALL firewall rules
# use the address group in case we want to open up remote management later
address-object TW_SUBNET 172.23.37.0/24
object-group address TW_TEAM
address-object TW_SUBNET
exit
# enable Telnet access (not enabled by default, unlike other services)
ip telnet server
# open WAN-to-ZyWALL firewall for TW_TEAM for remote management
firewall WAN ZyWALL insert 4
sourceip TW_TEAM
service TELNET
action allow
exit
write
While configuration files and shell scripts have the same syntax, the ZyWALL
applies configuration files differently than it runs shell scripts. This is explained
below.
Table 257 Configuration Files and Shell Scripts in the ZyWALL
Configuration Files (.conf)
• Resets to default configuration.
• Goes into CLI Configuration mode.
• Runs the commands in the configuration
file.
You have to run the example in
the first command is run in Privilege mode. If you remove the first command,
you have to run the example as a configuration file because the rest of the
commands are executed in Configuration mode.

Comments in Configuration Files or Shell Scripts

In a configuration file or shell script, use "#" or "!" as the first character of a
command line to have the ZyWALL treat the line as a comment.
880
Shell Scripts (.zysh)
• Goes into CLI Privilege mode.
• Runs the commands in the shell script.
Figure 583 on page 880
ZyWALL USG 100/200 Series User's Guide
as a shell script because