Configuration files define the NWA/WAC’s settings. Shell scripts are files of commands that you can store on the NWA/WAC and run when you need them. You can apply a configuration file or run a shell script without the NWA/WAC restarting. You can store multiple configuration files and shell script files on the NWA/WAC.You can edit configuration files or shell scripts in a text editor and upload them to the NWA/WAC. Configuration files use a .conf extension and shell scripts use a .zysh extension.
Configuration Files and Shell Scripts
When you apply a configuration file, the NWA/WAC uses the factory default settings for any features that the configuration file does not include. When you run a shell script, the NWA/WAC only applies the commands that it contains. Other settings do not change.
These files have the same syntax, which is also identical to the way you run CLI commands manually. An example is shown below.
While configuration files and shell scripts have the same syntax, the NWA/WAC applies configuration files differently than it runs shell scripts. This is explained below.
• Resets to default configuration. • Goes into CLI Configuration mode. • Runs the commands in the configuration file. |
• Goes into CLI Privilege mode. • Runs the commands in the shell script. |
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 NWA/WAC treat the line as a comment.
Your configuration files or shell scripts can use “exit” or a command line consisting of a single “!” to have the NWA/WAC exit sub command mode.
Note: “exit” or “!'” must follow sub commands if it is to make the NWA/WAC exit sub command mode.
In the following example lines 1 and 2 are comments. Line 7 exits sub command mode.
! this is from Joe # on 2010/12/05 wlan-ssid-profile default ssid Joe-AP qos wmm security default !
|
Errors in Configuration Files or Shell Scripts
When you apply a configuration file or run a shell script, the NWA/WAC processes the file line-by-line. The NWA/WAC checks the first line and applies the line if no errors are detected. Then it continues with the next line. If the NWA/WAC finds an error, it stops applying the configuration file or shell script and generates a log.
You can change the way a configuration file or shell script is applied. Include setenv stop-on-error off in the configuration file or shell script. The NWA/WAC ignores any errors in the configuration file or shell script and applies all of the valid commands. The NWA/WAC still generates a log for any errors.
Use the Configuration File screen to store, run, and name configuration files. You can also download configuration files from the NWA/WAC to your computer and upload configuration files from your computer to the NWA/WAC.
Once your NWA/WAC is configured and functioning properly, it is highly recommended that you back up your configuration file before making further configuration changes. The backup configuration file will be useful in case you need to return to your previous settings.
Configuration File Flow at Restart
• If there is not a startup-config.conf when you restart the NWA/WAC (whether through a management interface or by physically turning the power off and back on), the NWA/WAC uses the system-default.conf configuration file with the NWA/WAC’s default settings.
• If there is a startup-config.conf, the NWA/WAC checks it for errors and applies it. If there are no errors, the NWA/WAC uses it and copies it to the lastgood.conf configuration file as a back up file. If there is an error, the NWA/WAC generates a log and copies the startup-config.conf configuration file to the startup-config-bad.conf configuration file and tries the existing lastgood.conf configuration file. If there isn’t a lastgood.conf configuration file or it also has an error, the NWA/WAC applies the system-default.conf configuration file.
• You can change the way the startup-config.conf file is applied. Include the setenv-startup stop-on-error off command. The NWA/WAC ignores any errors in the startup-config.conf file and applies all of the valid commands. The NWA/WAC still generates a log for any errors.
Do not turn off the NWA/WAC while configuration file upload is in progress.
Example of Configuration File Download Using FTP
The following example gets a configuration file named startup-config.conf from the NWA/WAC and saves it on the computer.
1 Connect your computer to the NWA/WAC.
2 The FTP server IP address of the NWA/WAC in standalone AP mode is 192.168.1.2, so set your computer to use a static IP address from 192.168.1.3 ~192.168.1.254.
3 Use an FTP client on your computer to connect to the NWA/WAC. For example, in the Windows command prompt, type ftp 192.168.1.2. Keep the console session connected in order to see when the firmware recovery finishes.
4 Enter your user name when prompted.
5 Enter your password as requested.
6 Use “cd” to change to the directory that contains the files you want to download.
7 Use “dir” or “ls” if you need to display a list of the files in the directory.
8 Use "get” to download files. Transfer the configuration file on the NWA/WAC to your computer. Type get followed by the name of the configuration file. This examples uses get startup-config.conf.
9 Wait for the file transfer to complete.
10 Enter “quit” to exit the ftp prompt.
Use the Firmware Package screen to check your current firmware version and upload firmware to the NWA/WAC.
Note: The Web Configurator is the recommended method for uploading firmware. You only need to use the command line interface if you need to recover the firmware. See the CLI Reference Guide for how to determine if you need to recover the firmware and how to recover it.
Find the firmware package at www.zyxel.com in a file that (usually) uses a .bin extension.
The firmware update can take up to five minutes. Do not turn off or reset the NWA/WAC while the firmware update is in progress!
Label |
Description |
---|---|
This is the version of the boot module that is currently on the NWA/WAC. |
|
This is the firmware version and the date created. |
|
Released Date |
This is the date that the version of the firmware was created. |
File Path |
Type in the location of the file you want to upload in this field or click Browse... to find it. |
Browse... |
Click Browse... to find the .bin file you want to upload. Remember that you must decompress compressed (.zip) files before you can upload them. |
Click Upload to begin the upload process. This process may take up to two minutes. |
After you see the Firmware Upload in Process screen, wait two minutes before logging into the NWA/WAC again.
Note: The NWA/WAC automatically reboots after a successful upload.
The NWA/WAC automatically restarts causing a temporary network disconnect.
After five minutes, log in again and check your new firmware version in the Dashboard screen.
Example of Firmware Upload Using FTP
This procedure requires the NWA/WAC’s firmware. Download the firmware package from www.zyxel.com and unzip it. The firmware file uses a .bin extension, for example, "420AAHY1C0.bin". Do the following after you have obtained the firmware file.
1 Connect your computer to the NWA/WAC.
2 The FTP server IP address of the NWA/WAC in standalone AP mode is 192.168.1.2, so set your computer to use a static IP address from 192.168.1.3 ~192.168.1.254.
3 Use an FTP client on your computer to connect to the NWA/WAC. For example, in the Windows command prompt, type ftp 192.168.1.2. Keep the console session connected in order to see when the firmware recovery finishes.
4 Enter your user name when prompted.
5 Enter your password as requested.
6 Enter “hash” for FTP to print a `#' character for every 1024 bytes of data you upload so that you can watch the file transfer progress.
7 Enter “bin” to set the transfer mode to binary.
8 Transfer the firmware file from your computer to the NWA/WAC. Type put followed by the path and name of the firmware file. This examples uses put C:\ftproot\NWA/WAC_FW\420AAHY1C0.bin.
9 Wait for the file transfer to complete.
10 Enter “quit” to exit the ftp prompt.
Use shell script files to have the NWA/WAC use commands that you specify. Use a text editor to create the shell script files. They must use a “.zysh” filename extension.
Use the Shell Script screen to store, name, download, upload and run shell script files. You can store multiple shell script files on the NWA/WAC at the same time.
Note: You should include write commands in your scripts. If you do not use the write command, the changes will be lost when the NWA/WAC restarts. You could use multiple write commands in a long script.
Label |
Description |
---|---|
Rename |
Use this button to change the label of a shell script file on the NWA/WAC. You cannot rename a shell script to the name of another shell script in the NWA/WAC. Click a shell script’s row to select it and click Rename to open the Rename File screen. Specify the new name for the shell script file. Use up to 25 characters (including a-zA-Z0-9;‘~!@#$%^&()_+[]{}’,.=-). Click OK to save the duplicate or click Cancel to close the screen without saving a duplicate of the configuration file. |
Remove |
Click a shell script file’s row to select it and click Delete to delete the shell script file from the NWA/WAC. A pop-up window asks you to confirm that you want to delete the shell script file. Click OK to delete the shell script file or click Cancel to close the screen without deleting the shell script file. |
Click a shell script file’s row to select it and click Download to save the configuration to your computer. |
|
Copy |
Use this button to save a duplicate of a shell script file on the NWA/WAC. Click a shell script file’s row to select it and click Copy to open the Copy File screen. Specify a name for the duplicate file. Use up to 25 characters (including a-zA-Z0-9;‘~!@#$%^&()_+[]{}’,.=-). Click OK to save the duplicate or click Cancel to close the screen without saving a duplicate of the configuration file. |
Run |
Use this button to have the NWA/WAC use a specific shell script file. Click a shell script file’s row to select it and click Run to have the NWA/WAC use that shell script file. You may need to wait awhile for the NWA/WAC to finish applying the commands. |
# |
This column displays the number for each shell script file entry. |
File Name |
This column displays the label that identifies a shell script file. |
Size |
This column displays the size (in KB) of a shell script file. |
Last Modified |
This column displays the date and time that the individual shell script files were last changed or saved. |
Upload Shell Script |
The bottom part of the screen allows you to upload a new or previously saved shell script file from your computer to your NWA/WAC. |
File Path |
Type in the location of the file you want to upload in this field or click Browse... to find it. |
Browse... |
Click Browse... to find the .zysh file you want to upload. |
Click Upload to begin the upload process. This process may take up to several minutes. |