Chapter 47 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 429 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 233 Configuration Files and Shell Scripts in the ZyWALL

Configuration Files (.conf)

Shell Scripts (.zysh)

 

 

 

• Resets to default configuration.

Goes into CLI Privilege mode.

Goes into CLI Configuration mode.

Runs the commands in the shell script.

Runs the commands in the configuration

 

 

 

file.

 

 

 

 

 

 

You have to run the example in Figure 429 on page 738 as a shell script because 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.

738

 

ZyWALL USG 50 User’s Guide