Table Of Contents
Command Reference
Before using this chapter, read:
•
Chapter 1, "" for important information about command line guidelines including ports and protocols.
•
Chapter 2, "" for information about configuring PIX Firewall for initial access, server access, authentication, and troubleshooting.
The following notes can help you as you configure the PIX Firewall:
•
View your configuration at any time with the write terminal command.
•
Save your configuration frequently with the write memory command.
•
Always check the syntax before entering a command. Enter a command and press the Enter key to view a quick summary, or precede a command with help, as in, help aaa.
•
View syslog messages as you work on the PIX Firewall. Start accumulating messages with the logging buffered 7 command, view messages with the show logging command, and clear the message buffer with the clear logging command. Syslog messages are described in the System Log Messages for the PIX Firewall Version 4.3. You can view this document online at:
http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_v43/syslog/
•
Abbreviate commands, such as, co t to start configuration mode, wr t to list the configuration, and wr m to write to Flash memory. Start logging with lo b 7 and show messages with sh lo.
•
After changing or removing the alias, conduit, global, nat, outbound, and static commands, use the clear xlate command to make the IP addresses available for access. If access still does not work, save the configuration to Flash memory with the write memory command and reboot. For this reason, it is best to make configuration changes during off-hours on your network.
•
View possible port and protocol numbers at the following IANA web sites:
http://www.isi.edu/in-notes/iana/assignments/port-numbers
http://www.isi.edu/in-notes/iana/assignments/protocol-numbers
•
Create your configuration on a text editor and then cut and paste it into the configuration. PIX Firewall lets you paste in a line at a time or the whole configuration. Always check your configuration after pasting large blocks of text to be sure everything copied.
aaa
Enable, disable, or view TACACS+ or RADIUS user authentication, authorization, and accounting for the server previously designated with the radius-server or tacacs-server commands.
(Configuration mode.)
aaa accounting acctg_service | except inbound|outbound| if_name local_ip local_mask
foreign_ip foreign_mask tacacs+ | radiusno aaa accounting authen_service | except inbound | outbound | if_name
aaa authentication authen_service | except inbound | outbound | if_name local_ip local_mask
foreign_ip foreign_mask tacacs+ | radiusno aaa authentication [authen_service | except inbound|outbound | if_name local_ip local_mask foreign_ip foreign_mask tacacs+ | radius]
aaa authentication [enable | any | telnet] console tacacs+ | radius
no aaa authentication [any | telnet] console tacacs+ | radius
aaa authorization author_service | except inbound| outbound | if_name
local_ip local_mask foreign_ip foreign_maskno aaa authorization [author_service | except inbound | outbound | if_name
local_ip local_mask foreign_ip foreign_mask]show aaa
Syntax Description
accounting
Enable or disable accounting services with authentication server. Use of this command requires that you previously used either the radius-server or tacacs-server command to designate an authentication server.
acctg_service
The accounting service. Possible values are any, ftp, http, telnet, or protocol/port. For protocol/port, protocol is 6 for TCP, 17 for UDP, and so on, and port is the TCP or UDP destination port. A port value of 0 (zero) means all ports. For protocols other than TCP and UDP, the port is not applicable and should not be used.
authentication
Enable or disable user authentication, prompt user for username and password, and verify information with authentication server.
When used with the console option, enables or disables authentication service for access to the PIX Firewall console over Telnet or from the Console connector on the PIX Firewall unit.
Use of the aaa authentication command requires that you previously used either the radius-server or tacacs-server command to designate an authentication server.
authen_service
The application with which a user is accessing a network. Use any, ftp, http, or telnet. The any value enables accounting or authentication for all TCP services. To have users prompted for authentication credentials, they must use FTP, HTTP, or Telnet. (HTTP is the Web and only applies to web browsers that can prompt for a username and password.)
If the authentication or authorization server is authenticating services other than FTP, HTTP, or Telnet, using any will not permit those services to authenticate in the firewall. The firewall only knows how to communicate with FTP, HTTP, and Telnet for authentication and authorization.
Only set this parameter to a service other than any if the authentication or authorization server is set the same way. Unless you want to temporarily restrict access to a specific service, setting a service in this command can increase system administration work and may cause all connections to fail if the authentication or authorization server is authenticating one service and you set this command to another.
authorization
Enable or disable TACACS+ user authorization for services (PIX Firewall does not support RADIUS authorization). The authentication server determines what services the user is authorized to access.
author_service
The services which require authorization. Use any, ftp, http, telnet, or protocol/port. Services not specified are authorized implicitly. Services specified in the aaa authentication command do not affect the services which require authorization.
For protocol/port:
•
protocol—the protocol (6 for TCP, 17 for UDP, 1 for ICMP, and so on).
•
port—the TCP or UDP destination port, or port range. The port can also be the ICMP type; that is, 8 for ICMP echo or ping. A port value of 0 (zero) means all ports. Port ranges only applies to the TCP and UDP protocols, not to ICMP. For protocols other than TCP, UDP, and ICMP the port is not applicable and should not be used. An example port specification is:
aaa authorization udp/53-1024 inside 0 0 0 0This example enables authorization for DNS lookups to the inside interface for all clients, and authorizes access to any other services that have ports in the range of 53 to 1024.
except
Create an exception to a previously specified set of services.
inbound
Authenticate or authorize inbound connections. Inbound means the connection originates on the outside interface and is being directed to the inside or perimeter.
outbound
Authenticate or authorize outbound connections. Outbound means the connection originates on the inside and is being directed to the outside or perimeter.
if_name
Interface name from which users require authentication. Use if_name in combination with the local_ip address and the foreign_ip address to determine where access is sought and from whom. The local_ip address is always on the highest security level interface and foreign_ip is always on the lowest. Refer to the Examples section for how the if_name affects the use of this command.
local_ip
The IP address of the highest security level interface from which or to which access is sought. You can set this address to 0 to let the authentication server decide which hosts are authenticated.
local_mask
Network mask of local_ip. Always specify a specific mask value. Use 0 if the IP address is 0.
foreign_ip
The IP address of the lowest security level interface from which or to which access is sought.
foreign_mask
Network mask of foreign_ip. Always specify a specific mask value. Use 0 if the IP address is 0.
console
Specify that access to the PIX Firewall console require authentication.
If used with the enable keyword, access to the serial console depends on acceptance of login credentials from an authentication server. In addition, any changes made to the configuration from the serial console (not from Telnet console sessions) are sent to syslog at level 4.
If used with the any keyword, access to the serial console or Telnet to the PIX Firewall's console must be authenticated with the authentication server. If used with the telnet keyword, then only Telnet access to the PIX Firewall console requires authentication from the authentication server.
Telnet access to the PIX Firewall console is only available from the inside interface and requires previous use of the tcpchecksum command.
Authentication of the serial console creates a potential dead-lock situation if the authentication server requests are not answered and you need access to the console to attempt diagnosis. If the console login request times out, you can gain access to the PIX Firewall from the serial console by entering the pix username and the enable password.
The maximum password length for accessing the console is 16 characters.
tacacs+
Authenticate using Terminal Access Controller Access Control System Plus (TACACS+).
radius
Authenticate using Remote Authentication Dial-In User Service (RADIUS).
Usage Guidelines
The aaa command enables or disables:
•
User authentication services. A user starting a connection via FTP, Telnet, or over the World Wide Web is prompted for their username and password. An authentication server, designated previously with the tacacs-server or radius-server command, verifies whether the username and password are correct. If the username and password are correct, PIX Firewall lets further traffic between the authentication server and the connection interact independently through the PIX Firewall's "Cut-Through Proxy" feature.
•
Authentication access to the PIX Firewall's console via Telnet or the serial console. (Telnet access requires previous use of the tcpchecksum command.)
•
User authorization services for TACACS+ connections that let the authentication server determine which services the user can access.
•
Accounting services so that administrators can track which hosts accessed the PIX Firewall.
Note
PIX Firewall does not support RADIUS authorization.
Note
If the AAA console login request times out, you can gain access to the PIX Firewall from the serial console by entering the pix username and the enable password.
Usage Notes
1
You can change the authentication prompt with the auth-prompt command.
2
The aaa command is not intended to mandate your security policy. The authentication and authorization servers determine whether a user can or cannot access the system, what services can be accessed, and what IP addresses the user can access.The PIX Firewall interacts with FTP, HTTP (Web access), and Telnet to display the credentials prompts for logging in to the network or logging in to exit the network. You can specify that only a single service be authenticated, but this must agree with the authentication server to ensure that both the firewall and server agree.
3
You can now specify an interface name with aaa authentication. In previous versions, if you specified aaa authentication any outbound 0 0 server, PIX Firewall only authenticated outbound connections and not those to the perimeter interface. PIX Firewall now authenticates any outbound connection to the outside as well as to hosts on the perimeter interface. To preserve the behavior of previous versions, use these commands to enable authentication and to disable authentication from the inside to the perimeter interface:
aaa authentication any outbound 0 0 0 0 serveraaa authentication except outbound inside_net inside_mask perim_net perim_mask server4
If you want to allow connections to come from any host, code the IP address and mask as 0.0.0.0 0.0.0.0, or 0 0.When the web server and the authentication server are on different hosts, use the virtual command to get the correct authentication behavior.
5
When using HTTP authentication to a site running Microsoft IIS that has "Basic text authentication" or "NT Challenge" enabled, users may be denied access from the Microsoft IIS server. This occurs because the browser appends the string: "Authorization: Basic=Uuhjksdkfhk==" to the HTTP GET commands. This string contains the PIX Firewall authentication credentials.
Windows NT Microsoft IIS servers respond to the credentials and assume that a Windows NT user is trying to access privileged pages on the server. Unless the PIX Firewall username password combination is exactly the same as a valid Windows NT username and password combination on the Microsoft IIS server, the HTTP GET command is denied.
To solve this problem, PIX Firewall provides the virtual http command which redirects the browser's initial connection to another IP address, authenticates the user, then redirects the browser back to the URL which the user originally requested.
Once authenticated, a user never has to reauthenticate no matter how low the PIX Firewall uauth timeout is set. This is because the browser caches the "Authorization: Basic=Uuhjksdkfhk==" string in every subsequent connection to that particular site. This can only be cleared when the user exits all instances of Netscape Navigator or Internet Explorer and restarts. Flushing the cache is of no use.
As long as the user repeatedly browses the Internet, the browser resends the "Authorization: Basic=Uuhjksdkfhk==" string to transparently reauthenticate the user.
6
Use of the aaa authorization command requires previous use of the aaa authentication command; however, use of the aaa authentication command does not require use of an aaa authorization command.
7
For outbound connections, first use the nat command to determine which IP addresses can access the firewall. For inbound connections, first use the static and conduit commands to determine which inside IP addresses can be accessed through the firewall from the outside network.
8
When a host is configured for authentication, all users on the host have to use a web browser or Telnet first before performing any other networking activity, such as accessing mail or a news reader. The reason for this is that users must first establish their authentication credentials and programs such as mail agents and newsreaders do not have authentication challenge prompts.
9
The PIX Firewall only accepts 7-bit characters during authentication. After authentication, the client and server can negotiate for 8-bits if required. During authentication, the PIX Firewall only negotiates Go-Ahead, Echo, and NVT (network virtual terminal).
10
Up to 16 TACACS+ or RADIUS servers are permitted. When a user logs in, the servers are accessed one at a time starting with the first server you specify in the configuration, until a server responds.
11
For each IP address, one aaa authentication command is permitted for inbound connections and one for outbound connections. Also, for an IP address, one aaa authorization command is permitted. If you want to authorize more than one service with aaa authorization, use the any parameter for the service type.
12
The PIX Firewall permits only one authentication type per network. For example, if one network connects through the PIX Firewall using TACACS+ for authentication, another network connecting through the PIX Firewall can authenticate with RADIUS, but one network cannot authenticate with both TACACS+ and RADIUS.
13
The PIX Firewall permits a user up to four chances to log in with Telnet and then if the username or password still fails, the PIX Firewall drops the connection. If a user enters an incorrect password in FTP, the connection is dropped immediately. If a user enters an incorrect password in HTTP, the user is reprompted.
14
For the TACACS+ server, if you do not specify a key to the tacacs-server command, no encryption occurs.
15
Network browsers such as Netscape Navigator do not present a challenge value during authentication; therefore, only password authentication can be used from a network browser.
16
Some FTP graphical user interfaces (GUIs) do not display challenge values.
17
If the username or password on the authentication database differs from the username or password on the remote host to which you are using FTP to access, enter the username and password in these formats:
authentication_user_name@remote_system_user_nameauthentication_password@remote_system_passwordIf you daisy-chain PIX Firewall units, Telnet authentication works in the same way as a single unit, but FTP and HTTP authentication have additional complexity for users because they have to enter each password and username with an additional at (@) character and password or username for each daisy-chained system. Users can exceed the 63-character password limit depending on how many units are daisy-chained and password length.
18
PIX Firewall supports authentication usernames up to 127 characters and passwords of up to 63 characters. A password or username may not contain an at (@) character as part of the password or username string, except as shown in Note 18.
19
If the first attempt at authorization fails and a second attempt causes a timeout, use the
service resetinbound command to reset the client that failed the authorization so that it will not retransmit any connections. An example authorization timeout message in Telnet is:Unable to connect to remote host: Connection timed outSee also: radius-server, tacacs-server, virtual, tcpchecksum.
Examples
1
The following examples demonstrate ways to use the if_name parameter. The PIX Firewall has an inside network of 192.168.1.0, an outside network of 204.31.17.0, and a perimeter network of 192.150.50.0.
This example enables authentication for connections originated from the inside network to the outside network:
aaa authentication any outbound 192.168.1.0 255.255.255.0 204.31.17.0 255.255.255.0 tacacs+This example enables authentication for connections originated from the inside network to the perimeter network:
aaa authentication any outbound 192.168.1.0 255.255.255.0 192.150.50.0 255.255.255.0 tacacs+This example enables authentication for connections originated from the outside network to the inside network:
aaa authentication any inbound 192.168.1.0 255.255.255.0 204.31.17.0 255.255.255.0 tacacs+This example enables authentication for connections originated from the outside network to the perimeter network:
aaa authentication any inbound 192.150.50.0 255.255.255.0 204.31.17.0 255.255.255.0 tacacs+This example enables authentication for connections originated from the perimeter network to the outside network:
aaa authentication any perimeter 192.150.50.0 255.255.255.0 204.31.17.0 255.255.255.0 tacacs+2
This example specifies that IP addresses 10.0.0.1 through 10.0.0.254 can originate outbound connections and then enables user authentication so that those addresses must enter user credentials to exit the firewall. In this example, the first aaa authentication command permits authentication on FTP, HTTP, or Telnet depending on what the authentication server handles. The second aaa authentication command lets host 10.0.0.42 start outbound connections without being authenticated.
nat (inside) 1 10.0.0.0 255.255.255.0aaa authentication any outbound 0 0 tacacs+aaa authentication except outb 10.0.0.42 255.255.255.255 tacacs+3
This example permits inbound access to any IP address in the range of 204.31.17.1 through 204.31.17.254. All services are permitted by the conduit command and the aaa authentication command permits authentication on FTP, HTTP, or Telnet depending on what the authentication server handles.
static (inside, outside) 204.31.17.0 10.16.1.0 netmask 255.255.255.0 10 60conduit permit tcp 204.31.17.0 255.255.255.0 10.16.1.0 255.255.255.0aaa authentication any inbound 0 0 tacacs+4
This example enables authorization for DNS lookups from the outside interface:
aaa authorization udp/53 inbound 0.0.0.0 0.0.0.05
This example enables authorization of ICMP echo-reply packets arriving at the inside interface from inside hosts:
aaa authorization 1/0 outbound 0.0.0.0 0.0.0.0This means that users will not be able to ping external hosts if they have not been authenticated using Telnet, HTTP, or FTP.
6
This example enables authorization for ICMP echoes (pings) only that arrive at the inside interface from an inside host:
aaa authorization 1/8 outbound 0.0.0.0 0.0.0.0alias
Administer overlapping addresses with dual NAT. (Configuration mode.)
alias [(if_name)] dnat_ip foreign_ip [netmask]
no alias [[(if_name)] dnat_ip foreign_ip [netmask]]
show alias
Syntax Description
Usage Guidelines
The alias command translates one address into another. Use this command to prevent conflicts when you have IP addresses on a network that are the same as those on the Internet or another intranet. You can also use this command to do address translation on a destination address. For example, if a host sends a packet to 204.31.17.1, you can use alias to redirect traffic to another address, such as, 192.150.50.42.
After changing or removing an alias statement, use the clear xlate command. If the previous condition persists, save your configuration with the write memory command and then reboot the PIX Firewall.
There must be an A (address) record in the DNS zone file for the "dnat" address in the alias command.
The no alias command disables a previously set alias statement. The show alias command displays alias statements in the configuration.
The alias command automatically interacts with DNS servers on your network to ensure that domain name access to the aliased IP address is handled transparently.
You can specify a net alias by using network addresses for the foreign_ip and dnat_ip IP addresses. For example, alias 10.1.1.0 204.31.17.0 255.255.255.0 creates aliases for each IP address between 204.31.17.1 and 204.31.17.254.
Examples
1
In this example, an inside network uses IP address 192.159.1.33, which on the Internet belongs to domain.com. When inside clients try to access domain.com, the packets do not go to the firewall because the client thinks 192.159.1.33 is on the local inside network. To correct this, a net alias is created as follows with the alias command:
alias (inside) 192.168.1.0 192.159.1.0show aliasalias 192.168.1.0 192.159.1.0 255.255.255.0When client 192.159.1.123 connects to domain.com, the DNS response from an external DNS server to the internal client's query would be altered by the PIX Firewall to: 192.168.1.33. If the PIX Firewall uses 204.31.17.1 through 204.31.17.254 as the global pool IP addresses, the packet goes to the PIX Firewall with SRC=192.159.1.123 and DST=192.168.1.33. The PIX Firewall translates it to SRC=204.31.17.254 and DST=192.159.1.33 on the outside.
2
In this example, a web server is on the inside at 10.1.1.11 and a static for it at 204.31.17.11. The source host is on the outside with address 192.150.50.7. A DNS server on the outside has a record for www.caguana.com as follows:
The period at the end of the www.caguana.com. domain name must be included.
The alias command is:
alias 10.1.1.11 204.31.17.11 255.255.255.255PIX Firewall doctors the nameserver replies to 10.1.1.11 for inside clients to directly connect to the web server.
The conduit command statement you would expect to use is:
conduit permit tcp host 204.31.17.11 eq telnet host 192.150.50.7But with the alias command, use this command:
conduit permit tcp host 204.31.17.11 eq telnet host 192.159.1.7
You can test the DNS entry for the host with the following nslookup command:
nslookup -type=any www.caguana.comarp
Change or view the PIX Firewall's ARP cache, and set the timeout value. (Configuration mode.)
arp if_name ip_address mac_address [alias]
clear arp
no arp if_name ip_address
show arp [if_name] [ip_address mac_address alias]
arp timeout seconds
no arp timeout
show arp timeout
Syntax Description
Usage Guidelines
The arp command adds an entry to the PIX Firewall ARP cache. ARP is a low-level TCP/IP protocol that resolves a node's physical address from its IP address through an ARP request asking the node with a particular IP address to send back its physical address. The presence of entries in the ARP cache indicates that the PIX Firewall has network connectivity. The clear arp command clears the ARP table but not the alias (permanent) entries. Use the no arp command to remove these entries. The show arp command lists the entries in the ARP table.
Use the arp command to add an entry for new hosts you add on your network or when you swap an existing host for another. Alternatively, you can wait for the duration specified with the arp timeout command to expire and the ARP table rebuilds itself automatically with the new host information.
The arp timeout command sets the duration that an ARP entry can stay in the PIX Firewall ARP table before expiring. The timer is known as the ARP persistence timer. The default value is
14,400 seconds (4 hours).The no arp timeout command sets the timer to its default value. The show arp timeout command displays its current value.
Examples
arp inside 192.168.0.42 00e0.1e4e.2a7carp outside 192.168.0.43 00e0.1e4e.3d8b aliasshow arpoutside 192.168.0.43 00e0.1e4e.3d8b aliasinside 192.168.0.42 00e0.1e4e.2a7cclear arp inside 192.168.0.42arp timeout 42show arp timeoutarp timeout 42 secondsno arp timeoutshow arp timeoutarp timeout 14400 secondsauth-prompt
Change the AAA challenge text. (Configuration mode.)
auth-prompt string
clear auth-prompt
no auth-prompt string
show auth-prompt
Syntax Description
Usage Guidelines
The auth-prompt command lets you change the AAA challenge text for HTTP, FTP, and Telnet access. This text displays above the username and password prompts that users view when logging in. If you do not use this command, FTP users view FTP authentication, HTTP users view HTTP Authentication, and challenge text does not appear for Telnet access.
Example
auth-prompt XYZ Company Firewall AccessAfter this string is added to the configuration, users view:
XYZ Company Firewall AccessUser Name:Password:clock
Set the PIX Firewall clock for use with the PIX Firewall Syslog Server. (Configuration mode.)
clock
clock set hh:mm:ss month day year
clock set hh:mm:ss day month year
show clock
Syntax Description
Usage Guidelines
The clock command lets you specify the current time, month, day, and year for use time stamped syslog messages, which you can enable with the logging timestamp command. You can view the current time with the clock or the show clock command.
You can interchange the settings for the day and the month; for example, clock set 21:0:0 1 apr 2000.
A time prior to January 1, 1998 or after December 31, 2097 will not be accepted (the maximum date that the clock command can work to).
While the PIX Firewall clock is year 2000 compliant, it does not adjust itself for daylight savings time changes; however, it does know about leap years.
The PIX Firewall clock setting is retained in memory when the power is off by a battery on the PIX Firewall's motherboard. Should this battery fail, contact Cisco's customer support for a replacement PIX Firewall unit.
Example
To enable PFSS time-stamp logging for the first time, use these commands:
clock set 21:0:0 apr 1 2000show clock21:00:05 Apr 01 2000logging host 204.31.17.3logging timestamplogging trap 5In this example, the clock command sets the clock to 9 pm on April 1, 2000. The logging host command specifies that a syslog server is at IP address 204.31.17.3. The PIX Firewall automatically determines that the server is a PFSS and sends syslog messages to it via TCP and UDP. The logging timestamp command enables sending time stamped syslog messages. The logging trap command specifies that messages at syslog level 0 through 5 be sent to the syslog server. The value 5 is used to capture severe and normal messages, but also those of the aaa authentication enable command.
conduit
Add, delete, or show conduits through the firewall for incoming connections. (Configuration mode.)
conduit permit | deny protocol global_ip global_mask [operator port [port]] foreign_ip foreign_mask [operator port [port]]
no conduit permit | deny protocol global_ip global_mask [operator port [port]] foreign_ip foreign_mask [operator port [port]]
conduit permit | deny icmp global_ip global_mask foreign_ip foreign_mask [icmp_type]
show conduit
permit
Permit access if the conditions are matched.
deny
Deny access if the conditions are matched.
protocol
Specify the transport protocol for the connection. Possible literal values are icmp, tcp, udp, or an integer in the range 0 through 255 representing an IP protocol number. Use ip to specify all transport protocols. You can view valid protocol numbers online at:
http://www.isi.edu/in-notes/iana/assignments/protocol-numbers
If you specify the icmp protocol, you can permit or deny ICMP access to one or more global IP addresses. Specify the ICMP type in the icmp_type variable, or omit to specify all ICMP types. Refer to the Usage Guidelines for a complete list of the ICMP types.
global_ip
A global IP address previously defined by a global or static command. You can use any if the global_ip and global_mask are 0.0.0.0 0.0.0.0. The any option applies the permit or deny to the global addresses.
If global_ip is a host, you can omit global_mask by specifying the host command before global_ip. For example:
conduit permit tcp host 204.31.17.1 eq ftp anyThis example lets any foreign host access global address 204.31.17.1 for FTP.
global_mask
Network mask of global_ip. The global_mask is a 32-bit, four-part dotted decimal; such as, 255.255.255.255. Use zeros in a part to indicate bit positions to be ignored. Use subnetting if required. If you use 0 for global_ip, use 0 for the global_mask; otherwise, enter the global_mask appropriate to global_ip.
foreign_ip
An external IP address (host or network) that can access the global_ip. You can specify 0.0.0.0 or 0 for any host. If both the foreign_ip and foreign_mask are 0.0.0.0 0.0.0.0, you can use the shorthand any option.
If foreign_ip is a host, you can omit foreign_mask by specifying the host command before foreign_ip. For example:
conduit permit tcp any eq ftp host 204.31.17.42This example lets foreign host 204.31.17.42 access any global address for FTP.
foreign_mask
Network mask of foreign_ip. The foreign_mask is a 32-bit, four-part dotted decimal; such as, 255.255.255.255. Use zeros in a part to indicate bit positions to be ignored. Use subnetting if required. If you use 0 for foreign_ip, use 0 for the foreign_mask; otherwise, enter the foreign_mask appropriate to foreign_ip. You can also specify a mask for subnetting, for example, 255.255.255.192.
operator
A comparison operand that lets you specify a port or a port range.
Use without an operator and port to indicate all ports; for example:
conduit permit tcp any anyUse eq and a port to permit or deny access to just that port. For example use eq ftp to permit or deny access only to FTP:
conduit deny tcp host 192.168.1.1 eq ftp 204.31.17.1Use lt and a port to permit or deny access to all ports less than the port you specify. For example, use lt 2025 to permit or deny access to the well known ports (1 to 1024):
conduit permit tcp host 192.168.1.1 lt 1025 anyUse gt and a port to permit or deny access to all ports greater than the port you specify.
For example, use gt 42 to permit or deny ports 43 to 65535:conduit deny udp host 192.168.1.1 gt 42 host 204.31.17.42Use neq and a port to permit or deny access to every port except the ports that you specify.
For example, use neq 10 to permit or deny ports 1-9 and 11 to 65535:conduit deny tcp host 192.168.1.1 neq 10 host 204.31.17.42 neq 42Use range and a port range to permit or deny access to only those ports named in the range.
For example, use range 10 1024 to permit or deny access only to ports 10 through 1024. All other ports are unaffected.conduit deny tcp any range ftp telnet anyNote By default, all ports are denied until explicitly permitted.
port
Service(s) you permit to be used while accessing global_ip or foreign_ip. Specify services by the port that handles it, such as smtp for port 25, www for port 80, and so on. You can specify ports by either a literal name or a number in the range of 0 to 65535. You can specify all ports by not specifying a port value; for example:
conduit deny tcp any anyThis command is the default condition for the conduit command in that all ports are denied until explicitly permitted.
You can view valid port numbers online at:
http://www.isi.edu/in-notes/iana/assignments/port-numbers
Refer to the "Ports" section in Chapter 1, "" for a list of valid port literal names in port ranges; for example, ftp h323. You can also specify numbers.
icmp_type
The type of ICMP message. lists the ICMP type literals that you can use in this command. Omit this option to mean all ICMP types. An example of this command that permits all ICMP types is: conduit permit icmp any any. This command lets ICMP pass inbound and outbound.
Syntax Description
Usage Guidelines
A conduit statement creates an exception to the PIX Firewall Adaptive Security mechanism by permitting connections from one firewall network interface to access hosts on another.
The conduit command can permit or deny access to either the global or static commands; however, neither is required for the conduit command. You can associate a conduit command with a global or static command through the global address, either specifically to a single global address, a range of global addresses, or to all global addresses.
When used with a static, a conduit permits users on a lower security interface to access a higher security interface. When not used with a static, a conduit permits both inbound and outbound access.
If you associate a conduit with a static, only the interfaces specified on the static have access to the conduit. For example, if a static lets users on the dmz interface access the inside interface, only users on the dmz interface can access the static. Users on the outside do not have access.
Note
The conduit commands are processed in the order entered into the configuration.
Conduit permit and deny options are processed in the order listed in the PIX Firewall configuration. In the following example host 192.159.1.250 is not denied access through the PIX Firewall because the permit option precedes the deny option:
conduit permit tcp host 204.31.17.4 255.255.255.255 eq 80 anyconduit deny tcp host 204.31.17.4 255.255.255.0 192.159.1.250 255.255.255.255 eq 80 any
Note
If you want internal users to be able to ping external hosts, use the conduit permit icmp any any command.
After changing or removing a conduit command, use the clear xlate command. If the previous condition persists, save your configuration with the write memory command, and then reboot the PIX Firewall.
You can remove a conduit with the no conduit command. Use the show conduit command to view the conduit statements in the configuration.
If you prefer more selective ICMP access, you can specify a single ICMP message type as the last option in this command. lists possible ICMP types values.
Usage Notes
1
By default, all ports are denied until explicitly permitted.
2
Conduit commands are processed in the order entered in the configuration. If you remove a command, it affects the order of all subsequent conduit statements.
3
To remove all conduit commands, cut and paste your configuration onto your console computer, edit the configuration on the computer, use the write erase command to clear the current configuration, and then paste the configuration back into the PIX Firewall.
4
You can have as many conduits as needed as long as the total size of your configuration does not exceed the maximum size of the configuration. Directions for calculating the maximum configuration size are provided in the Release Notes for the PIX Firewall Version 4.3. You can view this document online at:
http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_v43/pixrn43.htm
5
If you use PAT (Port Address Translation), you cannot use conduit using the PAT address to either permit or deny access to ports.
6
Two conduit statements are required for establishing access to the following services: discard, dns, echo, ident, pptp, rpc, sunrpc, syslog, tacacs-ds, talk, and time. Each service, except for pptp, requires one conduit for TCP and one for UDP. For DNS, if you are only receiving zone updates, you only need a single conduit statement for TCP.
The two conduit statements for the PPTP transport protocol, which is a subset of the GRE protocol, are as shown in this example:
static (dmz2,outside) 204.31.17.5 192.168.1.5 netmask 255.255.255.255conduit permit tcp host 204.31.17.5 eq 1723 anyconduit permit gre host 204.31.17.5 anyIn this example, PPTP is being used to handle access to host 192.168.1.5 on the dmz2 interface from users on the outside. Outside users access the dmz2 host using global address 204.31.17.5. The first conduit statement opens access for the PPTP protocol and gives access to any outside users. The second conduit permits access to GRE. If PPTP was not involved and GRE was, you could omit the first conduit statement.
7
The RPC conduit support fixes up UDP portmapper and rpcbind exchanges. TCP exchanges are not supported. This lets simple RPC-based programs work; however, remote procedure calls, arguments, or responses that contain addresses or ports will not be fixed up.
For MSRPC, two conduit statements are required, one for port 135 and another for access to the high ports (1024-65535). For Sun RPC, a single conduit is required for UDP port 111.
Once you create a conduit for RPC, you can use the following command to test its activity from a UNIX host:
rpcinfo -u unix_host_ip_address 150001Replace unix_host_ip_address with the IP address of the UNIX host.
8
You can overlay host statics on top of a net static range to further refine what an individual host can access:
static (inside, outside) 204.31.17.0 10.1.1.0conduit permit tcp 204.31.17.0 255.255.255.0 eq ftp anystatic (inside, outside) 203.31.17.3 10.1.1.3conduit permit udp host 204.31.17.3 eq h323 host 1.2.3.3In this case, the host at 1.2.3.3 has InternetPhone access in addition to its blanket FTP access.
Examples
1
The following commands permit access between an outside UNIX gateway host at 204.31.17.42, to an inside SMTP server with Mail Guard at 192.168.1.49. Mail Guard is enabled in the default configuration for PIX Firewall with the fixup protocol smtp 25 command. The global address on the PIX Firewall is 204.31.17.1:
static (inside,outside) 204.31.17.1 192.168.1.49 netmask 255.255.255.255 0 0conduit permit tcp host 204.31.17.1 eq smtp host 204.31.17.42To disable Mail Guard, enter this command:
no fixup protocol smtp 252
You can set up an inside host to receive H.323 InternetPhone calls and allow the outside network to connect inbound via the IDENT protocol (TCP port 113). In this example, the inside network is at 192.168.1.0, the global address is 204.31.17.0, and the outside network is 192.150.50.0:
static (inside,outside) 204.31.17.0 192.168.1.0 netmask 255.255.255.0 0 0conduit permit tcp 204.31.17.0 255.255.255.0 eq h323 anyconduit permit tcp 204.31.17.0 255.255.255.0 eq 113 192.150.50.0 255.255.255.03
You can create a web server on the perimeter interface that can be accessed by any outside host as follows:
static (perimeter,outside) 204.31.17.4 192.168.1.4 netmask 255.255.255.0 0conduit permit tcp host 204.31.17.4 eq 80 anyIn this example, the static command maps the perimeter host, 10.1.1.4. to the global address, 204.31.17.4. The conduit statement specifies that the global host can be accessed on port 80 (web server) by any outside host.
configure
Clear or merge current configuration with that on floppy or Flash, start configuration mode, or view current configuration. (Privileged mode.)
clear configure primary|secondary|all
configure net [[server_ip]:[filename]]
configure floppy
configure memory
configure terminal
show configure
Syntax Description
Usage Guidelines
The clear configure command resets a configuration to its default values. Use this command to create a template configuration or when you want to clear all values. The clear configure primary command resets the default values for the interface, ip, mtu, nameif, and route commands. This command also deletes interface names in the configuration. The clear configure secondary removes alias, conduit, global, and static lines from the configuration.
Note
Save your configuration before using the clear configure command. The clear configure secondary command does not prompt you before deleting lines from your configuration.
The configure net command merges the current running configuration with a TFTP configuration stored at the IP address you specify and from the file you name. If you specify both the IP address and path name in the tftp-server command, you can specify :filename as simply a colon ( : ); for example:
configure net :Use the write net command to store the configuration in the file.
Note
Many TFTP servers require the configuration file to be world-readable to be accessible.
The configure floppy command merges the current running configuration with the configuration stored on diskette. This command assumes that the diskette was previously created by the write floppy command.
The configure memory command merges the configuration in Flash memory into the current configuration in RAM.
The configure terminal command starts configuration mode. Exit configuration mode with the quit command. After exiting configuration mode, use write memory to store your changes in Flash memory or write floppy to store the configuration on diskette. Use the write terminal command to display the current configuration.
The show configure command lists the contents of the configuration in Flash memory.
Each statement from diskette (with configure floppy), Flash memory (with configure memory), or TFTP transfer (with configure net) is read into the current configuration and evaluated in the same way as commands entered from a keyboard with these rules:
•
If the command on diskette or Flash memory is identical to an existing command in the current configuration, it is ignored.
•
If the command on diskette or Flash memory is an additional instance of an existing command, such as if you already have one telnet command for IP address 1.2.3.4 and the diskette configuration has a telnet command for 6.7.8.9, then both commands appear in the current configuration.
•
If the command redefines an existing command, the command on diskette or Flash memory overwrites the command in the current configuration in RAM. For example, if you have hostname ram in the current configuration and hostname floppy on diskette, the command in the configuration becomes hostname floppy and the command line prompt changes to match the new host name when that command is read from diskette.
Example
configure net 10.1.1.1:/tftp/config/pixconfigconfigure floppyconfigure memorypixfirewall> enablepassword: *****pixfirewall# configure terminalpixfirewall(config)# show config: Saved... config commands ...: Endwrite memorydebug
Debug packets or ICMP tracings through the PIX Firewall. (Configuration mode.)
debug icmp trace
no debug icmp trace
debug packet if_name [src source_ip [netmask mask]] [dst dest_ip [netmask mask]]
[[proto icmp] | [proto tcp [sport src_port] [dport dest_port]] |
[proto udp [sport src_port] [dport dest_port]] [rx | tx | both]no debug packet if_name [src source_ip [netmask mask]] [dst dest_ip [netmask mask]]
[[proto icmp] | [proto tcp [sport src_port] [dport dest_port]] |
[proto udp [sport src_port] [dport dest_port]] [rx | tx | both]debug sqlnet
no debug sqlnet
show debug
Syntax Description
if_name
Interface name from which the packets are arriving; for example, to monitor packets coming into the PIX Firewall from the outside, set if_name to outside.
src source_ip
Source IP address.
netmask mask
Network mask.
dst dest_ip
Destination IP address.
proto icmp
Display ICMP packets only.
proto tcp
Display TCP packets only.
sport src_port
Source port. Refer to the "Ports" section in Chapter 1, "" for a list of valid port literal names.
dport dest_port
Destination port.
proto udp
Display UDP packets only.
rx
Display only packets received at the PIX Firewall.
tx
Display only packets that were transmitted from the PIX Firewall.
both
Display both received and transmitted packets.
Usage Guidelines
The debug command lets you view debug information. The show debug command displays the current state of tracing. You can debug the contents of network layer protocol packets with debug packet. The debug sqlnet command reports on traffic between Oracle SQL*Net clients and servers through the PIX Firewall. The debug icmp trace command shows ICMP packet information, the source IP address, and the destination address of packets arriving, departing, and traversing the PIX Firewall including pings to the PIX Firewall's own interfaces.
Use of the debug commands can slow down busy networks.
Trace Channel Feature
The debug icmp trace and debug sqlnet commands now send their output to the Trace Channel. The location of the Trace Channel depends on whether you have a simultaneous Telnet console session running at the same time as the console session, or if you are using only the PIX Firewall serial console:
•
If you are only using the PIX Firewall serial console, all debug commands display on the serial console.
•
If you have both a serial console session and a Telnet console session accessing the console, then no matter where you enter the debug icmp trace or the debug sqlnet commands, the output displays on the Telnet console session.
•
If you have two or more Telnet console sessions, the first session is the Trace Channel. If that session closes, the serial console session become the Trace Channel. The next Telnet console session that accesses the console will then become the Trace Channel.
•
The debug packet command only displays on the serial console. However, you can enable or disable this command from either the serial console or a Telnet console sessions.
The debug commands are shared between all Telnet and serial console sessions.
Note
The downside of the Trace Channel feature is that if one administrator is using the serial console and another administrator starts a Telnet console session, the serial console debug icmp trace and debug sqlnet output will suddenly stop without warning. In addition, the administrator on the Telnet console session will suddenly be viewing debug output, which may be unexpected. If you are using the serial console and debug output is not appearing, use the who command to see if a Telnet console session is running.
Additional debug Command Information
Note
Use of the debug packet command on a PIX Firewall experiencing a heavy load may result in the output displaying so fast that it may be impossible to stop the output by entering the no debug packet command from the console. You can enter the no debug packet command from a Telnet session.
Note
To let users ping through the PIX Firewall, add the conduit permit icmp any any command to the configuration. This lets pings go outbound and inbound.
To stop a debug packet trace, enter:
no debug packet if_nameReplace if_name with the name of the interface; for example, inside, outside, or a perimeter interface name.
To stop a debug icmp trace, enter:
no debug icmp traceExamples
The following example turns on this command:
debug icmp traceWhen you ping a host through the PIX Firewall from any interface, trace output displays on the console. The following example shows a successful ping from an external host (204.31.17.42) to the PIX Firewall's outside interface (204.31.71.1):
Inbound ICMP echo reply (len 32 id 1 seq 256) 204.31.17.1 > 204.31.17.42Outbound ICMP echo request (len 32 id 1 seq 512) 204.31.17.42 > 204.31.17.1Inbound ICMP echo reply (len 32 id 1 seq 512) 204.31.17.1 > 204.31.17.42Outbound ICMP echo request (len 32 id 1 seq 768) 204.31.17.42 > 204.31.17.1Inbound ICMP echo reply (len 32 id 1 seq 768) 204.31.17.1 > 204.31.17.42Outbound ICMP echo request (len 32 id 1 seq 1024) 204.31.17.42 > 204.31.17.1Inbound ICMP echo reply (len 32 id 1 seq 1024) 204.31.17.1 > 204.31.17.42NO DEBUG ICMP TRACEICMP trace offThis example shows that the ICMP packet length is 32 bytes, that the ICMP packet identifier is 1, and the ICMP sequence number. The ICMP sequence number starts at 0 and is incremented each time a request is sent.
You can debug the contents of packets with debug packet:
debug packet inside--------- PACKET ----------- IP --4.3.2.1 ==> 255.3.2.1ver = 0x4 hlen = 0x5 tos = 0x0 tlen = 0x60id = 0x3902 flags = 0x0 frag off=0x0ttl = 0x20 proto=0x11 chksum = 0x5885-- UDP --source port = 0x89 dest port = 0x89len = 0x4c checksum = 0xa6a0-- DATA --00000014: 00 01 00 00 |....00000024: 00 00 00 01 20 45 49 45 50 45 47 45 47 45 46 46 | .... EIEPEGEGEFF00000034: 43 43 4e 46 41 45 44 43 41 43 41 43 41 43 41 43 | CCNFAEDCACACACAC00000044: 41 43 41 41 41 00 00 20 00 01 c0 0c 00 20 00 01 | ACAAA.. ..... ..00000054: 00 04 93 e0 00 06 60 00 01 02 03 04 00 | ......`......--------- END OF PACKET ---------This display lists the information as it appears in a packet.
An example of show debug follows:
show debugdebug icmp trace offdebug packet offdebug sqlnet offdisable
Exit privileged mode and return to unprivileged mode. (Privileged mode.)
disable
Usage Guidelines
The disable command exits privileged mode and returns you to unprivileged mode. Use the enable command to return to privileged mode.
Example
pixfirewall# disablepixfirewall>enable
Start privileged mode. (Unprivileged mode.)
enable
Usage Guidelines
The enable command starts privileged mode. The PIX Firewall prompts you for your privileged mode password. By default, a password is not required—press the Enter key at the Password prompt to start privileged mode. Use disable to exit privileged mode. Use enable password to change the password.
Example
pixfirewall> enablePassword:pixfirewall# configure terminalpixfirewall(config)#enable password
Set the privileged mode password. (Privileged mode.)
enable password password [encrypted]
show enable password
Syntax Description
password
A case-sensitive password of up to 16 alphanumeric characters.
encrypted
Specifies that the password you entered is already encrypted. The password must be 16 characters in length.
Usage Guidelines
The enable password command changes the privileged mode password, for which you are prompted after you enter the enable command. When the PIX Firewall starts and you enter privileged mode, the password prompt appears. There is not a default password (press the Enter key at the Password prompt). The show enable password command lists the encrypted form of the password.
You can return the enable password to its original value (press the Enter key at prompt) by entering:
pixfirewall# enable passwordpixfirewall#
Note
If you change the password, write it down and store it in a manner consistent with your site's security policy. Once you change this password, you cannot view it again. Also, ensure that all who access the PIX Firewall console are given this password.
Use the passwd command to set the password for PIX Firewall Manager and Telnet access to the PIX Firewall console. The default passwd value is cisco.
See also: passwd.
Examples
pixfirewall> enablePassword:pixfirewall# enable password w0ttal1fepixfirewall# configure terminalwrite terminalBuilding configuration......enable password 2oifudsaoid.9ff encrypted...The following shows the use of the encrypted option:
enable password 1234567890123456 encryptedshow enable passwordenable password 1234567890123456 encryptedenable password 1234567890123456show enable passwordenable password feCkwUGktTCAgIbD encryptedestablished
Allow or disallow return connections based on an established connection. (Configuration mode.)
established protocol dst_port_1 [permitto protocol [dst_port_2[-dst_port_2]]] [permitfrom protocol [src_port[-src_port]]]
no established protocol dst_port_1 [permitto protocol [dst_port_2[-dst_port_2]]] [permitfrom protocol [src_port[-src_port]]]
show established
Syntax Description
protocol
IP protocol type of udp or tcp.
dst_port_1
The destination port to which you want to establish a connection. Refer to the "Ports" section in Chapter 1, "" for a list of valid port literal names.
dst_port_2
The destination port that you want the PIX Firewall to permit the connection to return on.
src_port
The source port on the server from which the return connection will originate.
permitto
Permit inbound connections to the specified port or protocol. This option only opens the destination port.
permitfrom
Permit inbound connections from the specified port or protocol. Used with the permitto option, the permitfrom option provides a more specific source port. If the permitfrom option is used by itself, it requests access from a specific port to any port.
Usage Guidelines
The established command allows outbound connections return access to the PIX Firewall on different ports from which the original connection originated from. This command works with two connections, an original connection outbound from a network protected by the PIX Firewall and a return connection from a server on an external host. The PIX Firewall finds dst_port_1 in its translation table and associates the established command information with the outbound translation. The outbound translation indicates the source and destination IP addresses.
The first protocol and port you specify is for the destination of the original connection. The permitto and permitfrom options refine the information you specify for the return connection.
Note
Cisco recommends that you always specify the established command with the permitto and permitfrom options. Without these options, the use of the established command opens a security hole that can be exploited for attack of your internal systems. Refer to the "Security Problem" section that follows for more information.
The permitto option lets you specify a new protocol or port for the return connection at the PIX Firewall. The permitfrom option lets you specify a new protocol or port at the remote server. The no established command disables the established feature. The show established command shows the established commands in the configuration.
Note
For the established command to work, the client must listen on the port specified with the permitto option.
You can use the established command with a PAT or a non-PAT global statement, as well as with the nat 0 statement (where there are no global statements).
The established command works as shown in the following format:
established A B permitto C D permitfrom E FThis command works as though it were written "For protocol A and port B, permit a connection back to the PIX Firewall through protocol C and port D, and, optionally, permit a return connection from the server over protocol E and port F."
For example:
established tcp 6060 permitto tcp 6061 permitfrom tcp 6059In this case, a source connection starts using TCP port 6060. The PIX Firewall then lets the return connection come back in over TCP port 6061 from a server that is providing the same service at TCP port 6059.
For multimedia applications such as RealAudio, VDO, Xing, VocalTec, H.323, and CuSeeMe, PIX Firewall handles return packet access through the firewalls transparently. For other applications, such as Internet gaming, if the return packets do not return correctly and the application does not work, the established command provides an alternative functionality.
Security Problem
While this command is running, all UDP or TCP traffic is permitted between the client and server for the current TCP connection. This command only allows the host to which the inside client is connected to deliver UDP data or make high TCP port connections back to the client.
The established command can potentially open a large security hole in the PIX Firewall if not used with discretion. Whenever you use this command, if possible, also use the permitto and permitfrom options to indicate ports to which and from which access is permitted. Without these options, users outside the PIX Firewall can access any ports on servers behind the firewall that are accessible with the conduit and static commands.
The following example illustrates this problem:
static (inside,outside) 204.31.17.42 192.168.1.42 netmask 255.255.255.255conduit permit tcp host 204.31.17.42 eq http anyestablished tcp 0In this example, inside host 192.168.1.42 can be accessed from the outside interface for Web access as permitted by the conduit statement. Because this is a web server (using the HTTP port), access permission is granted to any outside host. However, the established command modifies the effect of the conduit statement and lets any user access any port on the 192.168.1.42 server.
Examples
The following example occurs when a local host 10.1.1.1 starts a TCP connection on port 9999 to a foreign host 204.31.17.1. The example allows packets from the foreign host 204.31.17.1 on port 4242 back to local host 10.1.1.1 on port 5454:
established tcp 9999 permitto tcp 5454 permitfrom tcp 4242The next example allows packets from foreign host 204.31.17.1 on any port back to local host 10.1.1.1 on port 5454:
established tcp 9999 permitto tcp 5454exit
Exit an access mode. (All modes.)
exit
Usage Guidelines
Use the exit command to exit from an access mode. This command is the same as quit.
Example
pixfirewall(config)# exitpixfirewall# exitpixfirewall>failover
Change or view access to the optional failover feature. (Configuration mode.)
failover [active]
failover ip address if_name ip_address
failover reset
failover timeout hh:mm:ss
no failover active
show failover
Syntax Description
Usage Guidelines
Use the failover command without an argument after you connect the optional failover cable between your primary firewall and a secondary firewall. The default configuration has failover enabled. Enter no failover in the configuration file for the PIX Firewall if you will not be using the failover feature. Use the show failover command to verify the status of the connection and to determine which unit is active.
Note
Remove the failover cable before upgrading to a new version of PIX Firewall. Once the new software is installed, reconnect the cable and reboot the two systems. The Primary unit will then automatically update the Secondary unit.
The Standby unit must not be configured individually. Only use the default configuration initially. When the two units are connected and the Primary unit reboots, the Secondary unit will be automatically updated. You can force an update by using the write standby command. If you make changes to the Standby unit, it displays a warning but does not update the Active unit.
To take a unit out of the "failed" state, cycle the power or use the failover reset command. When a failed Primary unit is fixed and brought back on line it will not automatically resume as the Active unit. This ensures that active control will not resume on a unit that could immediately enter a failed state again. However, if a failure is due to a lost signal on a network interface card, failover will "auto-recover" when the network is available again.
Use the failover active command to initiate a failover switch from the Standby unit, or the no failover active command from the Active unit to initiate a failover switch. You can use this feature to return a failed unit to service, or to force an Active unit offline for maintenance. Because the Standby unit does not keep state information on each connection, all active connections will be dropped and must be re-established by the clients.
If a failover IP address has not been entered, show failover will display 0.0.0.0 for the IP address, and monitoring of the interfaces will remain in "waiting" state. A failover IP address must be set for failover to work.
Refer to the section "Configuring Firewall Units for Failover" in Chapter 3 "" for additional configuration information.
Usage Notes
1
Failover provides a mechanism for PIX Firewall to be redundant by allowing two identical units to serve the same functionality.
2
One PIX Firewall unit is considered the "primary" unit while the other is considered the "secondary" unit (determined by the failover cable). The Primary unit is also the Active unit by default, and it performs normal network functions while the backup unit (standby) only monitors, ready to take control should the Active unit fail.
3
PIX Firewall configurations using failover require a separate IP address for each network interface on the Standby unit. The system IP address is the address of the Active unit. When the show IP address command is executed on the Active unit, the current IP address is the same as the system IP address. When the show IP address command is executed on the Standby unit, the system IP address is the failover IP address configured for the Standby unit.
4
The two units must be running the same version of software. Configuration replication will occur under the following conditions:
(a)
When the Standby unit completes its initial bootup, the Active unit will replicate its entire configuration to the Standby unit.
(b)
As commands are entered on the Active unit they are sent across to the Standby unit. (The commands are sent via the failover cable.)
(c)
Entering the write standby command on the Active unit forces the entire configuration to the Standby unit.
5
When a failure or switch occurs syslog messages are generated indicating the cause of the failure.
6
Because configuration replication is automatic from the Active unit to the Standby unit, configuration changes should only be entered from the Active unit.
7
Failover works in a switched environment.
If the unit is attached to a switch running spanning tree, this will take twice the forward delay time configured in the switch (typically 15 seconds) plus 30 seconds. This is because at bootup (and immediately following a failover event) the network switch will detect a temporary bridge loop.
When this bridge loop is detected, the switch will stop forwarding packets for the duration of the forwarding delay time. It will then enter "listen" mode for an additional forward delay time during which time the switch is listening for bridge loops but still not forwarding traffic (and thus not forwarding failover hello packets). After twice the forward delay time (30 seconds) traffic should resume. The PIX Firewall will remain in "waiting" mode until it hears two hello packets (1 every 15 seconds for a total of 30 seconds). During this time the PIX Firewall passes traffic, and will not fail the unit if it does not hear the hello packets. All other failover monitoring is still occurring (power, interface, and failover cable hello).
8
Failover also works with the FDDI interface. Note that Port-B is on the top of the FDDI card, and Port-A is on the bottom.
9
Failover works by passing control to the secondary unit should the Primary unit fail. For Ethernet, failover detection should occur within 30 to 45 seconds.
10
Assign different IP addresses to each PIX Firewall (with the ip address command).
11
The failover feature causes the PIX Firewall to ARP for itself every 15 seconds. If this adversely affects your ARP table, you can disable it with the no failover command.
12
Failover will not start monitoring the network interfaces until it has heard the second hello packet from the other unit on that interface. This should happen within 30 to 60 seconds.
13
If failover is disabled, the following displays:
show failoverFailover OffCable Status: My side not connectedReconnect timeout: 0:00:00Examples
The following output shows that failover is enabled, and that the Primary unit state is active:
show failoverFailover OnCable status: NormalThis host: Primary - ActiveActive time: 42855 (sec)Interface dmz (10.2.3.1): Normal (Waiting)Interface outside (204.31.17.1): Normal (Waiting)Interface inside (192.168.1.1): Normal (Waiting)Other host: Secondary - StandbyActive time: 0 (sec)Interface dmz (10.2.3.2): Normal (Waiting)Interface outside (204.31.17.2): Normal (Waiting)Interface inside (192.168.1.2): Normal (WaitingWaiting indicates that monitoring the other unit's network interfaces has not yet started. When a PIX Firewall fails, the Normal message changes to Failed.
You can view the IP addresses of the Standby unit with the show ip address command:
show ip addressSystem IP Addresses:ip address outside 204.31.17.2 255.255.255.0ip address inside 192.168.2.1 255.255.255.0ip address perimeter 204.31.18.3 255.255.255.0Current IP Addresses:ip address outside 204.31.17.2 255.255.255.0ip address inside 192.168.2.1 255.255.255.0ip address perimeter 204.31.18.3 255.255.255.0The Current IP Addresses are the same as the System IP Addresses on the failover Active unit. When the Primary unit fails, the Current IP Addresses become those of the Standby unit.
filter
Enable or disable outbound URL filtering for use with WebSENSE servers. (Configuration mode.)
filter url http|except local_ip local_mask foreign_ip foreign_mask [allow]
no filter url http|except [local_ip local_mask foreign_ip foreign_mask]
show filter
Syntax Description
Usage Guidelines
This command lets you prevent users from accessing World Wide Web URLs that you designate using the WebSENSE filtering application.
The allow option to the filter command determines how the PIX Firewall behaves in the event that the WebSENSE server goes offline. If you use the allow option with the filter command and the WebSENSE server goes offline, port 80 traffic passes through the PIX Firewall without filtering. Used without the allow option and with the server offline, PIX Firewall stops outbound port 80 (Web) traffic until the server is back online, or if another URL server is available, passes control to the next URL server.
Note
With the allow option set, PIX Firewall does not pass control to an alternate server if the WebSENSE server goes offline.
To filter URLs:
Step 1
Designate a WebSENSE server with the url-server command.
Step 2
Enable filtering with the filter command.
Step 3
If needed, improve throughput with the url-cache command. However, this command does not update WebSENSE logs, which may affect WebSENSE accounting reports. Accumulate WebSENSE run logs before using the url-cache command.
Step 4
Use the show url-cache stats and the show perfmon commands to view run information.
Information on WebSENSE is available at: http://www.websense.com/products/websense/
Example
The following example filters all outbound HTTP connections except those from the 10.0.2.54 host:
url-server (perimeter) host 10.0.1.1filter url http 0 0 0 0filter url except 10.0.2.54 255.255.255.255 0 0fixup protocol
Change, enable, disable, or list a PIX Firewall application protocol feature. (Configuration mode.)
fixup protocol ftp [port]
fixup protocol http [port[-port]
fixup protocol h323 [port[-port]]
fixup protocol rsh [514]
fixup protocol smtp [port[-port]]
fixup protocol sqlnet [port[-port]]
no fixup protocol protocol [port[-port]]
show fixup [protocol protocol]
Syntax Description
protocol
Specify the protocol to fix up: ftp, http, h323, rsh, smtp, sqlnet.
port
Specify the port number or range for the application protocol. The default ports are: 80 for http, 1720 for h323, 25 for smtp, and 1521 for sqlnet. The default port value for rsh cannot be changed, but additional port statements can be added. Refer to the "Ports" section in Chapter 1, "" for a list of valid port literal names.
Usage Guidelines
The fixup protocol commands let you view, change, enable, or disable the use of a through the PIX Firewall. The ports you specify are those that the PIX Firewall listens at for each respective service. You can change the port value for each service except rsh.
The fixup protocol smtp command enables the Mail Guard feature, which only lets mail servers receive the RFC 821, section 4.5.1 commands of HELO, MAIL, RCPT, DATA, RSET, NOOP, and QUIT. All other commands are rejected with the "500 command unrecognized" reply code.
The fixup protocol commands are always present in the configuration and are enabled by default. You can add multiple port settings for each protocol with separate commands; for example:
fixup protocol ftp 21fixup protocol ftp 4254fixup protocol ftp 9090These commands cause PIX Firewall to listen to the standard FTP port of 21 but also to listen for FTP traffic at ports 4254 and 9090.
The show fixup command lists all values or the show fixup protocol protocol command lists an individual protocol.
You can disable a protocol definition with the no fixup command.
Examples
The following example enables access to an inside server running Mail Guard:
static (inside, outside) 204.31.17.1 192.168.42.1 netmask 255.255.255.0conduit permit tcp host 204.31.17.1 eq smtp anyfixup protocol smtp 25This example shows the default fixup protocol values:
show fixupfixup protocol ftp 21fixup protocol http 80fixup protocol smtp 25fixup protocol h323 1720fixup protocol rsh 514fixup protocol sqlnet 1521The following example shows the commands to disable Mail Guard:
static (dmz1,outside) 204.31.17.1 10.1.1.1 netmask 255.255.255.255conduit permit tcp host 204.31.17.1 eq smtp anyno fixup protocol smtp 25In this example, the static command sets up a global address to permit outside hosts access to the 10.1.1.1 mail server host on the dmz1 interface. (The MX record for DNS needs to point to the 204.31.17.1 address so that mail is sent to this address.) The conduit command lets any outside users access the global address through the SMTP port (25). The no fixup protocol command disables the Mail Guard feature.
floodguard
Enable or disable Flood Defender to protect against flood attacks. (Configuration mode.)
floodguard enable | disable
show floodguard
Syntax Description
Usage Guidelines
The floodguard command lets you reclaim PIX Firewall resources if the user authentication (uauth) subsystem runs out of resources. If an inbound or outbound uauth connection is being attacked or overused, the PIX Firewall will actively reclaim TCP user resources.
When the resources deplete, the PIX Firewall lists messages about it being out of resources or out of tcpusers.
If the PIX Firewall uauth subsystem is depleted, TCP user resources in different states are reclaimed depending on urgency in the following order:
1
Timewait
2
FinWait
3
Embryonic
4
Idle
The floodguard command is enabled by default.
Example
floodguard enableshow floodguardfloodguard enableglobal
Create or delete entries from a pool of global addresses. (Configuration mode.)
global [(if_name)] nat_id global_ip[-global_ip] [netmask global_mask]
no global [(if_name)] nat_id [global_ip[-global_ip] [netmask global_mask]]
show global
Syntax Description
Usage Guidelines
The global command defines a pool of global addresses. The global addresses in the pool provide an IP address for each outbound connection, and for those inbound connections resulting from outbound connections. Ensure that associated nat and global statements have the same nat_id.
After changing or removing a global statement, use the clear xlate command. If the previous condition persists, save your configuration with the write memory command and then reboot the PIX Firewall.
Use the no global command to remove access to a nat ID, or to a PAT address or address range within a nat ID. Use the show global command to view the global statements in the configuration.
Usage Notes
1
You can enable the PAT (Port Address Translation) feature by entering a single IP address with the global command. PAT lets multiple outbound sessions appear to originate from a single IP address. With PAT enabled, the firewall chooses a unique port number from the PAT IP address for each outbound connection. This feature is valuable when an Internet service provider cannot allocate enough unique IP addresses for your outbound connections. The IP addresses you specify for Port Address Translation cannot be in another global address pool.
2
PAT does not work with H.323 applications and caching nameservers.
3
PAT works with DNS, FTP and passive FTP, HTTP, mail, RPC, rshell, Telnet, URL filtering, and outbound traceroute.
4
Do not use Port Address Translation when multimedia applications need to be run through the firewall. Multimedia applications can conflict with port mappings provided by PAT.
5
Port Address Translation (PAT) feature works with IP data packets that arrive in reverse order.
6
IP addresses in the pool of global addresses specified with the global command require reverse DNS entries to ensure that all external network addresses are accessible through the PIX Firewall. To create reverse DNS mappings, use a DNS PTR record in the address-to-name mapping file for each global address. For more information on DNS, refer to DNS and BIND, by Paul Albitz and Cricket Liu, O'Reilly & Associates, Inc., ISBN 1-56592-010-4. Without the PTR entries, sites can experience slow or intermittent Internet connectivity and FTP requests that consistently fail. For example, if a global IP address is 204.31.17.1 and the domain for the PIX Firewall is pix.caguana.com, the PTR record would be:
1.17.31.204.in-addr.arpa. IN PTR pix.caguana.com.7
The PIX Firewall allocates global IP addresses from the pool by starting at the end of the range you specify and working backward. In the following example, PIX Firewall starts with address 204.31.17.50, 204.31.17.49, and so on down to 204.31.17.40:
global (outside) 1 204.31.17.40-204.31.17.50Always add a PAT to the start of the range (the lowest IP address); for example:
global (outside) 1 204.31.17.39Then should addresses 204.31.17.40 through 204.31.17.50 be used up, PIX Firewall will assign the next connection to a port in 204.31.17.39.
Note
When a PAT is augmenting a pool of global addresses, first the addresses from the pool are used. The next connection is taken from the PAT address. If a global pool address frees, the next connection is taken from the global pool. The global pool addresses always come first, then the PAT addresses.
Examples
The following example declares two global pool ranges and a Port Address Translation address. Then the nat command permits all inside users to start connections to the outside network.
global (outside) 1 204.31.17.1-204.31.17.10 netmask 255.255.255.0global (outside) 1 204.31.17.42 netmask 255.255.255.0Global 204.31.17.42 will be Port Address Translatednat (inside) 1 0 0clear xlateThe next example creates a global pool from two contiguous Class C addresses and gives the perimeter hosts access to this pool of addresses:
global (outside) 1000 192.150.50.1-192.150.50.254global (outside) 1000 192.150.51.1-192.150.51.254nat (perimeter) 1000 0 0help
Display help information. (Unprivileged mode.)
help
?
Usage Guidelines
The help or ? command displays help information about all commands. You can view help for an individual command by entering the command name followed by a question mark or just the command name and pressing the Enter key.
If the pager command is enabled and when 24 lines display, the listing pauses, and the following prompt appears:
<--- More --->The More prompt uses syntax similar to the UNIX more command:
•
To view another screenful, press the Space bar.
•
To view the next line, press the Enter key.
•
To return to the command line, press the q key.
Example
age ?age <minutes>Help information is available on the core commands (not the show, no, or clear commands) by entering ? at the command prompt:
?aaa Enable, disable, or view TACACS+ or RADIUSuser authentication, authorization and accounting...hostname
Change the host name in the PIX Firewall command line prompt. (Configuration mode.)
hostname newname
Syntax Description
newname
New host name for the PIX Firewall prompt. This name can be up to 16 alphanumeric characters and mixed case.
Usage Guidelines
The hostname command changes the host name label on prompts. The default host name is pixfirewall.
Example
pixfirewall(config# hostname spinnerspinner(config)# hostname pixfirewallpixfirewall(config#interface
Identify network interface speed and duplex. (Configuration mode.)
interface hardware_id hardware_speed
show interface
Syntax Description
Usage Guidelines
The interface command identifies the speed and duplex settings of the network interface boards.
Use show interface to view information about the interface.The configuration of the interface affects buffer allocation (the PIX Firewall will allocate more buffers for higher line speeds). Buffer allocation can be checked with the show blocks command.
Note
The show interface command reports "line protocol down" for BNC cable connections and for 3Com cards.
Note
Even though the default is to set automatic speed sensing for the interfaces with the interface hardware_id auto command, it is safest to specify the speed of the network interfaces; for example, 10baset or 100basetx. This lets PIX Firewall operate in network environments that may include switches or other devices that do not handle auto sensing correctly.
Usage Notes
1
When you use the interface token-ring command, also use the mtu command to set the block size depending on the interface speed.
2
After changing an interface command, save your configuration with the write memory command and then reboot the PIX Firewall.
show interface Notes
The show interface command lets you view network interface information for both Ethernet and Token Ring depending on which is installed in your PIX Firewall. This is one of the first commands you should use when establishing network connectivity after installing a PIX Firewall.
The information in the show interface display is as follows:
•
"ethernet" (or token-ring) indicates that you have used the interface command to configure the interface. The statement indicates either outside or inside and whether the interface is available ("up") or not available ("down").
•
"line protocol up" means a working cable is plugged into the network interface. If the message is "line protocol down," either the cable is incorrect or not plugged into the interface connector.
•
Network interface type.
•
Interrupt vector. It is acceptable for Token Ring and Ethernet cards to have the same interrupts because PIX Firewall uses interrupts to get Token Ring information, but polls Ethernet cards.
•
MAC address. Intel cards start with "i" and 3Com cards with "3c."
•
MTU (maximum transmission unit): the size in bytes that data can best be sent over the network.
•
"nn packets input" indicates that packets are being received in the firewall.
•
"nn packets output" indicates that packets are being sent from the firewall.
•
Line duplex status: half duplex indicates that the network interface switches back and forth between sending and receiving information; full duplex indicates that the network interface can send or receive information simultaneously.
•
Line speed: 10baseT is listed as 10000 Kbit; 100baseTX is listed as 100000 Kbit.
•
Interface problems:
•
no buffer, the PIX Firewall is out of memory or slowed down due to heavy traffic and cannot keep up with the received data.
•
runts are packets with less information than expected.
•
giants are packets with more information than expected.
•
CRC (cyclic redundancy check) are packets that contain corrupted data (checksum error).
•
frame errors are framing errors.
•
ignored and aborted errors are provided for future use, but are not currently checked; the PIX Firewall does not ignore or abort frames.
•
underruns occur when the PIX Firewall is overwhelmed and cannot get data fast enough to the network interface card.
•
overruns occur when the network interface card is overwhelmed and cannot buffer received information before more needs to be sent.
Example
The following example assigns names to each interface, enables auto detection for the interface parameters, and then shows interface activity:
nameif ethernet0 outside security0nameif token-ring0 inside security100nameif ethernet1 DMZ security50interface ethernet0 autointerface token-ring0 16mbpsinterface ethernet1 autoshow interfaceinterface ethernet0 "outside" is up, line protocol is upHardware is i82557 ethernet, irq 10, address is 0060.7380.2f16IP address 192.150.50.1, subnet mask 255.255.0.0MTU 1500 bytes, BW 100000 Kbit half duplex0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort1 packets output, 0 bytes, 0 underrunsinterface token-ring0 "inside" is up, line protocol is upHardware is o3137 token-ring, irq 9, address is 0000.8326.72c6IP address 10.0.0.1, subnet mask 255.0.0.0MTU 8192 bytes, BW 16000 Kbit, Ring-speed: 16Mbps116 packets input, 27099 bytes, 0 no bufferReceived 116 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 116 frame, 0 overrun, 0 ignored, 0 abort3 packets output, 150 bytes, 0 underrunsinterface ethernet1 "DMZ" is up, line protocol is upHardware is i82557 ethernet, irq 9, address is 00a0.c95d.0282IP address 127.0.0.1, subnet mask 255.255.255.0MTU 1500 bytes, BW 10000 Kbit half duplex0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underrunsip address
Identify the IP address for the PIX Firewall. (Configuration mode.)
ip address if_name ip_address [netmask]
show ip
Syntax Description
if_name
The internal or external interface name designated by the nameif command.
ip_address
PIX Firewall's network interface IP address.
netmask
Network mask of ip_address.
Usage Guidelines
The ip address command assigns an IP address to the PIX Firewall. Use the show ip command to view which addresses are assigned to the network interfaces. If you make a mistake while entering this command, re-enter the command with the correct information.
After changing an ip address command, save your configuration with the write memory command and then reboot the PIX Firewall.
Note
Do not set the netmask to all 255s, such as 255.255.255.255. This stops access on the interface. Instead, use a network address of 255.255.255.0 for Class C addresses, 255.255.0.0 for Class B addresses, or 255.0.0.0 for Class A addresses.
The default address for an interface is 127.0.0.1.
PIX Firewall configurations using failover require a separate IP address for each network interface on the Standby unit. The system IP address is the address of the Active unit. When the show IP address command is executed on the Active unit, the current IP address is the same as the system IP address. When the show IP address command is executed on the Standby unit, the system IP address is the failover IP address configured for the Standby unit.
Example
nameif ethernet0 outside security0nameif ethernet1 inside security100nameif ethernet2 perimeter security50ip address inside 192.168.2.1 255.255.255.0ip address outside 204.31.17.2 255.255.255.0ip address perimeter 204.31.18.3 255.255.255.0show ip addressSystem IP Addresses:ip address outside 204.31.17.2 255.255.255.0ip address inside 192.168.2.1 255.255.255.0ip address perimeter 204.31.18.3 255.255.255.0Current IP Addresses:ip address outside 204.31.17.2 255.255.255.0ip address inside 192.168.2.1 255.255.255.0ip address perimeter 204.31.18.3 255.255.255.0The Current IP Addresses are the same as the System IP Addresses on the failover Active unit. When the Primary unit fails, the Current IP Addresses become those of the Standby unit.
kill
Terminate a Telnet session. (Privileged mode.)
kill telnet_id
Syntax Description
Usage Guidelines
The kill command terminates a Telnet session. Use the who command to view the Telnet session ID value. When you kill a Telnet session, the PIX Firewall lets any active commands terminate and then drops the connection without warning the user. The kill command does not affect PIX Firewall Manager sessions.
See also: show who, telnet.
Example
show who2: From 10.10.54.0kill 2link / linkpath / age
Specify a Private Link connection to a remote PIX Firewall. (Configuration mode.)
link [(if_name)] foreign_external_ip key-id key|md5
no link [(if_name)] foreign_external_ip key-id key|md5
show link
linkpath foreign_internal_ip netmask foreign_external_ip mtu
no linkpath foreign_internal_ip netmask foreign_external_ip mtu
show linkpath
age minutes
show age
Syntax Description
Usage Guidelines
The link command creates an encrypted path between version 4.3(x) Private Link-equipped PIX Firewall units. The PIX Firewall Private Link consists of an encryption circuit board and software that permits the PIX Firewall units to provide encrypted communications across an unsecure network such as the Internet.
You can specify up to seven encryption keys for data access between your unit and the remote unit. The key-ID and key values must be the same on each side of the Private Link. Once you specify the same keys on both sides of the connection, the systems alert each other when a new key takes effect.
PIX Firewall selects the next Private Link encryption key by the "round-robin" method. The age command determines the length of time a key is current.
The no link command deletes a key from the link command. Use the show link command to list the remote IP address, keys, and the number of packets processed through Private Link.
The linkpath command identifies the internal and external network interfaces on the foreign PIX Firewall running Private Link. Use show linkpath to view the IP addresses you specify. Use no linkpath to stop access to a Private Link remote firewall. You can use multiple linkpath statements to define which networks on the remote PIX Firewall can access the Private Link connection.
The show age command lists the current aging duration.
Usage Notes
1
Both PIX Firewall units using Private Link must run the same software version.
2
After using the link command to add or delete link entries, use the write memory command to store the configuration, and then reboot the PIX Firewall.
3
The number of Private Link keys must be the same on both sides of the link.
4
If you use the link command to change the interface on which a Private Link tunnel terminates, you must reboot the PIX Firewall on which you made the change. For example, if the Private Link tunnel terminates on the perimeter interface of the foreign PIX Firewall and you change it to terminate on the inside interface of the foreign PIX Firewall, you must reboot the local PIX Firewall on which you changed the configuration.
5
You can use the linkpath 0.0.0.0 0.0.0.0 foreign_external_ip command to route all outbound traffic on a foreign PIX Firewall to a central PIX Firewall. However, this use has two caveats: there can be only one central PIX Firewall and the other PIX Firewall units must be satellites to it. This implies that the satellites only relay connections to the central and do not communicate among themselves. The second caveat is that the linkpath 0 0 command overrides the default route on the outside interface of the satellite PIX Firewall causing all outbound traffic to flow over Private Link to the central PIX Firewall unit. One use of this feature is when access to the Internet is controlled through one PIX Firewall and the other PIX Firewall units feed their Internet traffic to this one site. This could occur when a central processing facility wants to manage all the Internet IP addresses, let the internal networks use any IP numbering scheme, and have local PIX Firewall units protecting individual departments or sites.
6
Use of linkpath from a perimeter interface requires a route command for that interface. Refer to the "Examples" section for more information.
7
You cannot ping the PIX Firewall interfaces from either the local or foreign PIX Firewall units. Use hosts on the network to ensure that PIX Firewall interfaces are reachable.
8
Test access to the foreign Private Link PIX Firewall with the ping inside command.
9
An encryption circuit board must be present to use link or linkpath commands.
10
Private Link is enabled automatically after you power-up after inserting the encryption circuit board.
11
If you install the Private Link board after you purchase your PIX Firewall, Refer to the Regulatory Compliance and Safety Information for the PIX Firewall for important safety information before opening the PIX Firewall chassis. Then refer to the Quick Installation Guide for the PIX Firewall for information about opening the PIX Firewall chassis and inserting new boards. Both documents are provided in the PIX Firewall accessory kit, on the CCO Documentation CD-ROM, and at the www.cisco.com web site.
12
Enter the link command for each key you want to specify; for example, if you want seven keys, enter the link command in the configuration seven times.
13
The PIX Firewall allows up to 256 Private Links.
14
At least two PIX Firewall units are required along with the hardware/software option to use this feature.
15
Refer to "Private Link" in Chapter 3 "" for more information.
16
If a single key is set, the age command keeps that one key active continuously.
17
Use the same link statements on either side of the Private Link to ensure that the keys are the same and in the same order on both sides of the link.
18
Private Link packet information tells the remote side what key number to use to decrypt the data. The aging duration can be different, as well as the system clocks themselves on either side of the link, but as long as you use the same link statements on both sides, all information decrypts correctly.
Examples
The following example specifies the remote IP address of the Private Link and specifies four keys for access to the remote system, and specifies the IP address of the inside network interface on the remote host.
link (perimeter) 204.31.17.2 1 fadebacfadebaclink (perimeter) 204.31.17.2 2 bacfadefadebaclink (perimeter) 204.31.17.2 3 baabaaafadebaclink (perimeter) 204.31.17.2 4 beebeeefadebaclinkpath 10.1.1.0 255.255.255.0 204.31.17.2route perimeter 10.1.1.0 255.255.255.0 192.150.50.1 1The link and linkpath commands in this example allow a Private Link to be established to or from the perimeter network at 204.31.17.2 and the remote network at 10.1.1.0. The route command is required to force the Private Link communications to the perimeter interface. The 192.150.50.1 IP address is that of the PIX Firewall's perimeter interface.
Another example follows:
link 204.31.17.42 1 12345678901234show linkTermIface Foreign IP KeyID Keyinside 204.31.17.42 1 0x12345678901234An age example follows:
age 10show agePrivate Link Key Aging: 10 minuteslogging
Enable or disable syslog and SNMP logging. (Configuration mode.)
logging on
no logging on
logging buffered level
clear logging
no logging buffered
logging console level
no logging console
logging facility facility
no logging facility facility
logging host [in_if_name] ip_address [protocol /port]
no logging host [in_if_name] ip_address
logging message syslog_id
no logging message syslog_id
clear logging disabled
show logging disabled
logging monitor level
no logging monitor level
logging timestamp
no logging timestamp
logging trap level
no logging trap level
show logging
Syntax Definition
Usage Guidelines
The logging command lets you enable or disable sending informational messages to the console, to a syslog server, or to an SNMP server.
You can also use this guide to get the message numbers that can be individually suppressed with the logging message command.
Important Notes
1
Do not use the logging console command when the PIX Firewall is in production mode because it degrades system performance. By default, this command is disabled. Instead, use the logging buffered command to start logging, the show logging command to view the messages, and the clear logging command to clear the buffer to make viewing the most current messages easier.
2
PIX Firewall provides more information in messages sent to a syslog server than at the console, but the console provides enough information to permit effective troubleshooting.
3
The logging timestamp command requires that the clock command be set.
4
The no logging message command cannot block the "%PIX-6-199002: PIX startup completed. Beginning operation." syslog message.
5
The aaa authentication enable console command causes syslog messages to be sent (at syslog level 4) each time the configuration is changed from the serial console.
See also: clock, telnet, terminal
Viewing Syslog Messages from the Console
To view syslog messages from the PIX Firewall console:
Step 1
Store syslog messages for display at the PIX Firewall console with the following command:
logging buffered 7The value 7 causes all syslog message levels to be stored in the buffer. If preferred, set the value to a lower number to view fewer messages.
Refer to Appendix A of the System Log Messages for the PIX Firewall Version 4.3 guide for a list of messages that appear at each severity level. You can view this document on line at:
http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_v43/syslog/
Step 2
View the messages with:
show loggingStep 3
Use the clear logging command to clear the buffer so that viewing new messages is easier.
Step 4
To disable storing messages, use the no logging buffered command.
New messages appear at the end of the logging listing.
Viewing Syslog Messages from a Telnet Console Session
To view syslog messages from a Telnet console session:
Step 1
If you have not done so already, configure the PIX Firewall to let a host on the inside interface access the PIX Firewall with the telnet command. For example, if a host has the IP address 192.168.1.2, the command would be:
telnet 192.168.1.2 255.255.255.255You should also set the duration that a Telnet session can be idle before PIX Firewall disconnects the session to a value greater than the default of 5 minutes. A good value is at least 15 minutes, which you can set as follows:
telnet timeout 15Step 2
Start Telnet and specify the inside interface of the PIX Firewall. For example, if the inside interface of the PIX Firewall is 192.168.1.1, the command to start Telnet would be:
telnet 192.168.1.1Step 3
When Telnet connects, the PIX Firewall prompts you with the PIX passwd: prompt. Enter the Telnet password, which is cisco by default.
Step 4
Use the enable command followed by the configure terminal command to get to configuration mode.
Step 5
Start message logging with the logging monitor command.
Step 6
Display messages directly to the Telnet session by entering the terminal monitor command. You can disable directly displaying messages by entering the terminal no monitor command.
Step 7
Trigger some events by pinging a host or starting a web browser. The syslog messages then appear in the Telnet session window.
Step 8
When done, disable this feature with these commands:
terminal no monitorno logging monitorSending Syslog Messages to a Syslog Server
PIX Firewall can send syslog messages to any syslog server. In the event that all syslog servers are offline, PIX Firewall stores up to 100 messages in its memory. Subsequent messages that arrive overwrite the buffer starting from the first line.
To send messages to a syslog server:
Step 1
Designate a host to receive the messages with the logging host command as shown in the following example:
logging host interface address [protocol/port]Replace interface with the interface on which the server exists and address with the IP address of the host. An example logging host command is as follows:
logging host outside 204.31.17.5If the syslog server is receiving messages on a non-standard port, you can replace protocol with udp and port with the new port value. The default protocol is UDP with a default port of 514. You can also specify TCP with a default of 1468. To date, there is only one TCP syslog server, the Cisco PIX Firewall Syslog Server (PFSS). Refer to "PIX Firewall Syslog Server (PFSS)" for more information.Only one logging host UDP or TCP statement is permitted for a specific syslog server. A subsequent statement overrides the previous one. Use the write terminal command to view the logging host command statement in the configuration—the UDP option is shown as "17" and the TCP option as "6."
Step 2
Set the logging level with the logging trap command; for example:
logging trap debuggingCisco recommends that you use the debugging level during initial setup and during testing. Thereafter, set the level from debugging to errors for production use.
Step 3
If needed, set the logging facility command to a value other than its default of 20. Most UNIX systems expect the messages to arrive at facility 20, which receives the messages in the local4 receiving mechanism.
Step 4
Start sending messages with the logging on command. To disable sending messages, use the no logging on command.
Step 5
If you want to send time stamped messages to a syslog server, use the clock set command to set the PIX Firewall system clock and the logging timestamp command to enable time stamping. For example:
clock set 14:25:00 apr 1 1999logging timestampIn this example, the clock is set to the current time of 2:25 pm on April 1, 1999, and time stamping is enabled. To disable time-stamp logging, use the no logging timestamp command.
Sending SNMP Traps to an SNMP Server
To send traps to an SNMP server:
Step 1
Identify the IP address of the SNMP server with the snmp-server host command.
Step 2
Set the snmp-server options for location, contact, and the community password as required.
Step 3
Set the logging level with the logging trap command; for example:
logging trap debuggingCisco recommends that you use the debugging level during initial set up and during testing. Thereafter, set the level from debugging to errors for production use.
Step 4
Start sending syslog messages to the server with the logging on command. To disable sending messages, use the no logging on command.
Only syslog messages in the syslog MIB are controlled by this command. Refer to "Compiling Cisco Syslog Enterprise MIB Files" in Chapter 3, "" for more information.
Suppressing Syslog Messages
To suppress syslog messages:
Step 1
Determine which syslog message needs to be suppressed by either observing a message whose frequency is overwhelming a message facility or by viewing the System Log Messages for the PIX Firewall Version 4.3. You can view this document on line at:
http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_v43/syslog/
Step 2
Use the no logging message command to suppress the message; for example:
no logging message 103012Step 3
To view all messages that are disabled, use the show logging disabled command. You can also view an individually disabled message with the show logging message syslog_id command.
Step 4
To send all messages, use the clear logging disabled command. Or you can return individual messages back to use with the logging message command.
For example, to suppress the following message:
%PIX-6-305002: Translation built for gaddr IP_addr to IP_addrUse the following command to stop this message from being sent to the syslog server:
no logging message 305002You can view all disabled messages or just one with the following commands:
show logging disabledno logging message 305002show logging message 305002syslog 305002 disabledIf you want to let the message resume being sent, use the following command:
logging message 305002Additional logging Command Information
The PIX Firewall generates syslog messages for system events, such as security alerts and resource depletion. Using a UNIX syslog facility, you can specify which types of syslog messages create email alerts, are stored in log files, or display on the console of a designated inside network host. Use the logging monitor command to determine what messages display in a Telnet session to the PIX Firewall console.
To disable messages for a specific session, use the terminal no monitor command.
Because the PIX Firewall shares the eight facilities with other UNIX network devices, the logging facility command lets you choose the facility that the PIX Firewall marks on each message it sends to the syslog host. Messages are sent to the syslog host over UDP.
Use the show logging command to view the current syslog hosts and previously sent messages.
PIX Firewall Syslog Server (PFSS)
The PIX Firewall Syslog Server (PFSS) provides a syslog server that runs from a Windows NT system and receives TCP and UDP syslog messages from up to 10 PIX Firewalls. This server is provided at no charge from Cisco Connection Online (CCO).
Use of the PFSS gives you the additional benefit of reliability through receiving TCP event messages and being able to monitor whether the server is up or down from the PIX Firewall. Installation instructions for the PFSS are provided in the Quick Installation Guide for the PIX Firewall Version 4.3. You can view this document online at:
http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_v43/pix43qig.htm
Note
The Windows NT filesystem where you install PFSS must be an NTFS partition and not FAT. The Windows NT system must run version 4.0 with Service Pack 3 installed.
You can configure the PIX Firewall to send syslog messages via UDP or TCP. If syslog messages are sent using TCP, and if the Windows NT partition in which the log files are stored runs out of disk space, the PIX Firewall stops all traffic until the disk space is freed or until the PIX Firewall is directed to send messages to another syslog server. If you configure the PIX Firewall to send syslog messages using UDP, the PIX Firewall operates normally regardless of the ability of the PFSS to receive messages.
Windows NT installation and configuration instructions for the PIX Firewall Syslog Server (PFSS) are described in the Quick Installation Guide for the PIX Firewall Version 4.3.
Note
PFSS and the PIX Firewall Manager cannot be used together even if installed on separate Windows NT systems.
PFSS creates seven rotating syslog files monday.log, tuesday.log, wednesday.log, thursday.log, friday.log, saturday.log, and sunday.log. If a week has passed since the last log file was created, it will rename the old log file to day.mmddyy where day is the current day, mm is the month, dd is the day, and yy is the year.
PFSS also creates the pfss.log file where the values for the disk full percentage, and the UDP and TCP port values are stored.
If the Windows NT filesystem is full, the PIX Firewall Syslog Server disables all TCP connections from the PIX Firewall by closing its TCP listen socket.
The PIX Firewall tries to re-connect to the PIX Firewall Syslog Server five times, and during the retry, it stops all new connections through the PIX Firewall. If the TCP connection cannot be re-established, the status of the host log is set to disable after the fifth attempt.
Changing Windows NT PFSS Parameters
Note
You can only view previously set PFSS timer values with the Windows NT regedit command by searching for disk_empty_watch. Do not change PFSS values from the Registry. You can view values other than the PFSS timers by viewing the pfss.log file with a program such as Notepad. This file is stored in the same directory that you specified for the log files when you installed PFSS.
Step 1
On the Windows NT system, select the PIX Firewall Syslog Server entry from the Start>Settings>Control Panel>Services menu. You can add commands to the Startup Parameters edit box. After you enter a command, click Start. If you press the Enter key, the menu closes without information being accepted.
Step 2
Change the values by entering one of these commands:
•
-d %_disk_full—The maximum percentage of how full the disk is that you allow the Windows NT to reach before causing the PIX Firewall to stop transmissions. This is an integer value in the range of 1 to 100. The default is 90.
•
-t tcp_port—the port used by the Windows NT system to listen for TCP syslog messages, the default is 1468. If you specify another port, it must be in the range of 1024 to 65535.
•
-u udp_port—the port used by the Windows NT system to listen for UDP syslog messages, the default is 514. If you specify another port, it must be in the range of 1024 to 65535.
•
-e disk_empty_watch_timer—the duration in seconds that PFSS waits between checks to see if the disk partition is still empty. The default is 5 seconds, the range is any number greater than zero.
•
-f disk_full_watch_timer—the duration in seconds that PFSS waits between checks to see if the disk partition is still full. The default is 3 seconds, the range is any number greater than zero.
Recovering After the Windows NT Disk is Full
To recover from a disk full situation:
Step 1
On the Windows NT system, move the old logs to a new filesystem (or back up and remove them). Make sure this creates enough free disk space for more log messages.
Step 2
On the PIX Firewall enter configuration mode and check that the PFSS host is correctly disabled from the PIX Firewall by entering the show logging command and look for "host interface ip_address 6/1468 disable." The "disable" keyword means that no new connections are allowed through the PIX Firewall.
Step 3
Disable logging to the PFSS host by entering the no logging host interface ip_address command for the disabled host.
Step 4
Re-enable logging by entering the logging host interface ip_address tcp/1468 command for the disabled host.
Step 5
Check that the PFSS host is now enabled by reentering the show logging command. The disable keyword should now be gone.
Step 6
Use the show conn command to determine if new connections have started. If none have, start a Telnet or FTP session through the PIX Firewall to start new connections.
Step 7
If new connections do not restart, reboot the PIX Firewall.
Example
The following example shows how to start console logging and view the results:
logging buffered debuggingshow loggingSyslog logging: enabledTimestamp logging: disabledConsole logging: disabledMonitor logging: disabledBuffer logging: level debugging, 37 messages loggedTrap logging: disabled305001: Portmapped translation built for gaddr 204.31.17.5/0 laddr 192.168.1.2/256...The line of output starting with 305001 shows a translation to a PAT global through global address 204.31.17.5 from a host at 192.168.1.2. The "305001" identifies a syslog message for creating a translation through a PAT global. Refer to System Log Messages for the PIX Firewall Version 4.3 for more information on syslog messages. You can view this document on line at:
http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_v43/syslog/
mtu
Specify the MTU (maximum transmission unit) for an interface. (Configuration mode.)
mtu if_name bytes
no mtu [if_name bytes]
show mtu
Syntax Description
Usage Guidelines
The mtu command sets the size of data sent on a connection. Data larger than the MTU value is fragmented before being sent. The minimum value for bytes is 64 and the maximum is 65,535 bytes.
PIX Firewall supports the IP Path MTU Discovery mechanism, as defined in RFC 1191. IP Path MTU Discovery allows a host to dynamically discover and cope with differences in the maximum allowable maximum transmission unit (MTU) size of the various links along the path. Sometimes a router is unable to forward a datagram because it requires fragmentation (the packet is larger than the MTU you set for the interface), but the "don't fragment" (DF) bit is set. The network software sends a message to the sending host, alerting it to the problem. The host will have to fragment packets for the destination so that they fit the smallest packet size of all the links along the path.
For Ethernet interfaces, the default MTU is 1,500 bytes in a block, which is also the maximum. This value is sufficient for most applications, but you can pick a lower number if network conditions warrant it.
For Token Ring, the default is 8,192 bytes.
The no mtu command resets the MTU block size to 1,500 for Ethernet interfaces and 8,192 for Token Ring. The show mtu command displays the current block size. The show interface command also shows the MTU value.
Example
interface token-ring0 16mbpsinterface ethernet0 automtu inside 8192show mtumtu outside 1500mtu inside 8192name / names
Associate a name with an IP address. (Configuration mode.)
name ip_address name
no name [ip_address name]
names
no names
clear names
show names
Syntax Description
Usage Guidelines
Use the name command to identify a host by a text name. The names you define become like a host table local to the PIX Firewall. Because there is no connection to DNS or /etc/hosts on UNIX servers, use of this command is a mixed blessing—it makes configurations much more readable but introduces another level of abstraction to administer; not only do you have to add and delete IP addresses to your configuration as you do now, but with this command, you need to ensure that the host names either match existing names or you have a map to list the differences.
The names command enables use of the name command to map text strings to IP addresses. The clear names and no names commands are the same and disable use of the name text strings. The show names command lists the name statements in the configuration.
Notes
1
You must first use the names command before using the name command. Use the name command immediately after the names command and before you use the write memory command.
2
To disable displaying name values, use no names.
3
Only one name can be associated with an IP address.
4
Both name and names statements are saved in the configuration.
Example
In the example that follows, the names command enables use of the name command. The name command substitutes pix_inside for references to 192.168.42.3, and pix_outside for 204.31.17.33. The ip address commands use these names while assigning IP addresses to the network interfaces. The no names command disables the name values from displaying. Subsequent use of the names command restores their display.
namesname 192.168.42.3 pix_insidename 204.31.17.33 pix_outsideip address inside pix_insideip address outside pix_outsideshow ip addressinside ip address pix_inside mask 255.255.255.255outside ip address pix_outside mask 255.255.255.255no namesshow ip addressinside ip address 192.168.42.3 mask 255.255.255.255outside ip address 204.31.17.33 mask 255.255.255.255namesshow ip addressinside ip address pix_inside mask 255.255.255.255outside ip address pix_outside mask 255.255.255.255nameif
Name interfaces and assign security level. (Configuration mode.)
nameif hardware_id if_name security_level
show nameif
Syntax Description
Usage Guidelines
The nameif command lets you assign a name to an interface. You can use this command to assign interface names if you have more than two network interface circuit boards in your PIX Firewall.
The first two interfaces have the default names inside and outside. The inside interface has default security level 100, the outside interface has default security level 0.
Usage Notes
1
After changing a nameif command, save your configuration with the write memory command and then reboot the PIX Firewall.
2
The inside interface cannot be renamed or given a different security level.
3
An interface is always "outside" with respect to another interface that has a higher security level.
4
Refer to the current PIX Firewall release notes for information about the number of supported interfaces.
See also: interface.
Example
nameif ethernet2 perimeter1 sec50nameif ethernet3 perimeter2 sec20nat
Associate a network with a pool of global IP addresses. (Configuration mode.)
nat [(if_name)] nat_id local_ip [netmask [max_conns [em_limit]]] [norandomseq]
no nat [[(if_name)] nat_id local_ip [netmask [max_conns [em_limit]]]] [norandomseq]
show nat
Syntax Description
Usage Guidelines
The nat command lets you enable or disable address translation for one or more internal addresses. Address translation means that when a host starts an outbound connection, the IP addresses in the internal network are translated into global addresses. Network Address Translation (NAT) lets your network have any IP addressing scheme and the firewall protects these addresses from visibility on the external network.
After changing or removing a nat statement, use the clear xlate command. If the previous condition persists, save your configuration with the write memory command and then reboot the PIX Firewall.
The connection limit lets you set the maximum number of outbound connections that can be started with the IP address criteria you specify. The embryonic connection limit lets you prevent a type of attack where processes are started without being completed. An embryonic connection is a connection that someone attempted but has not completed and has not yet seen data. Every connection is embryonic until it sets up.
You can use the no nat command to remove a nat statement and you can use the show nat command to view nat statements in the current configuration.
helps you decide when to use the nat or static commands for access between the various interfaces in the PIX Firewall. For this table, assume that the security levels are 40 for dmz1 and 60 for dmz2.
The rule of thumb is that for access from a higher security level interface to a lower security level interface, use the nat command. From lower security level interface to a higher security level interface, use the static command.
Usage Notes
1
You can disable address translation with the nat 0 command. Use this when you have IP addresses that are the same as those used on more than one interface. Adaptive Security remains in effect with the nat 0 command. The extent to which the inside hosts are accessible from the outside depends on the conduit statements that permit inbound access.
Addresses on each interface must be on a different subnet. Refer to Appendix D, "" for more information on subnetting.
The nat 0 1.2.3.0 command means let those IP addresses in the 1.2.3.0 net appear on the outside without translation. All other hosts are translated depending on how their nat statements appear in the configuration.
2
The nat 1 0 0 command means that all outbound connections can pass through the PIX Firewall with address translation. If you use the nat (inside) 1 0 0 command, users can start connections on any interface with a lower security level, on the both perimeter interfaces and the outside interface. With NAT in effect, you must also use the global statement to provide a pool of addresses through which translated connections pass. In effect, you use the nat statement to specify from which interface connections can originate and you use the global statement to determine at which interface connections can occur. The NAT ID must be the same on the nat and global statements.
3
The nat 1 1.2.3.0 command means that only outbound connections originating from the inside host 1.2.3.0 can pass through the firewall to go to their destinations with address translation.
See also: global, outbound, apply.
Examples
The following example specifies with nat statements that all the hosts on the 10.0.0.0 and 3.3.3.0 inside networks can start outbound connections. The global statements create a pool of global addresses.
nat (inside) 1 10.0.0.0 255.0.0.0global (outside) 1 204.31.17.25-204.31.17.27global (outside) 1 204.31.17.28nat (inside) 3 3.3.3.0 255.255.255.0global (outside) 3 204.31.18.1-204.31.18.254When using the nat 0 command, if you want the addresses to be visible from the outside network, use the static and conduit command:
nat (inside) 0 204.31.17.0 255.255.255.0static (inside, outside) 207.31.17.1 207.31.17.1conduit permit tcp host 207.31.17.1 eq ftp host 10.0.0.1static (inside, outside) 207.31.17.2 207.31.17.2conduit permit tcp host 207.31.17.2 eq ftp host 10.0.0.1...outbound / apply
Create an access list for controlling Internet use. (Configuration mode.)
outbound list_ID permit|deny ip_address [netmask [java|port[-port]]] [protocol]
outbound list_ID except ip_address [netmask [java|port[-port]]] [protocol]
clear outbound
no outbound [list_ID permit|deny ip_address [netmask [java|port[-port]]] [protocol]]
no outbound [list_ID except ip_address [netmask [java|port[-port]]] [protocol]]
show outbound
apply [(if_name)] list_ID outgoing_src|outgoing_dest
clear apply
no apply [[(if_name)] list_ID outgoing_src|outgoing_dest]
show apply [(if_name)] [list_ID outgoing_src|outgoing_dest]
Syntax Description
list_ID
A tag number for the access list. The access list number you use must be the same for the apply and outbound commands. This value must be a positive number. This number can be the same as what you use with nat and global. This number is just an arbitrary number that groups outbound statements to an apply statement.
permit
Allow the access list to access the specified IP address and port.
deny
Deny the access list access to the specified IP address and port.
except
Create an exception to a previous outbound command. An except statement applies to permit or deny statements only with the same access list ID.
When used with apply outgoing_src, the IP address of an except statement applies to the destination address.
When used with apply outgoing_dest, the IP address of an except statement applies to the source address.
Refer to "Outbound List Rules" for more information.
ip_address
The IP address for this access list entry. Do not specify a range of addresses. The 0.0.0.0 ip_address can be abbreviated as 0.
netmask
The network mask for comparing with the IP address; 255.255.255.0 causes the access list to apply to an entire Class C address. 0.0.0.0 indicates all access. The 0.0.0.0 netmask can be abbreviated as 0.
port
A port or range of ports that the access list is permitted or denied access to. Refer to the "Ports" section in Chapter 1, "" for a list of valid port literal names.
java
The java keyword indicates port 80 and when used with the deny option, means that the firewall blocks Java applets from being downloaded from ip_address (depending on use of the apply command). Java applets are permitted by default and do not have to be explicitly permitted.
protocol
Limit outbound access to udp, tcp, or icmp protocols. If a protocol is not specified, the default is tcp.
if_name
The network interface originating the connection.
outgoing_src
Deny or permit an internal IP address the ability to start outbound connections using the service(s) specified in the outbound command.
outgoing_dest
Deny or permit access to an external IP address using the service(s) specified in the outbound command.
Usage Guidelines
The outbound command creates an access list that lets you specify the following:
•
Whether inside users can create outbound connections
•
Whether inside users can access specific outside servers
•
What services inside users can use for outbound connections and for accessing outside servers
•
Whether outbound connections can execute Java applets on the inside network
Outbound lists are filters on outgoing packets from the PIX Firewall. The filter can be based on the source IP address, the destination IP address, and the destination port/protocol as specified by the rules. The use of an outbound command requires use of the apply command. The apply command lets you specify whether the access control list applies to inside users' ability to start outbound connections with apply command's outgoing_src option, or whether the access list applies to inside users' ability to access servers on the outside network with the apply command's outgoing_dest option.
After adding, removing, or changing outbound statements, save your configuration with the write memory command and then reboot the PIX Firewall.
Use the no outbound command to remove a single outbound statement from the configuration. Use the clear outbound command to remove all outbound statements from the configuration. The show outbound command displays the outbound statements in the configuration.
Use the no apply command to remove a single apply statement from the configuration. Use the clear apply statement to remove all the apply statements from the configuration. The show apply command displays the apply statements in the configuration.
Outbound List Rules
Rules, written as outbound list_ID ... statements are global to the PIX Firewall, they are activated by apply list_ID outgoing_src|outgoing_dest statements. When applied to outgoing_src, the source IP address, the destination port, and protocol are filtered. When applied to outgoing_dest, the destination IP address, port, and protocol are filtered.
The outgoing_src and outgoing_dest outbound lists are filtered independently. If any one of the filters contain deny, the outbound packet is denied. When multiple rules are used to filter the same packet, the best matched rule takes effect. The best match is based on the IP address mask and the port range check. More strict IP address masks and smaller port ranges are considered a better match. If there is a tie, a permit overrides a deny.
Rules are grouped by a list_ID. Within each list_ID, except rules (that is, outbound n except ...) can be set. The except option reverses the best matched rule of deny or permit. In addition, PIX Firewall filters the specified IP address and mask in the rule for the destination IP address of the outbound packet if the list is applied to the outbound_src. Alternatively, PIX Firewall filters the source IP address if the list is applied to the outgoing_dest. Furthermore, the except rules only apply to rules with the same list_ID. A single except rule within a list_ID without another permit or deny rule has no effect. If multiple except rules are set, the best match is checked for which except to apply.
The outbound command rules are now sorted by the best match checking. Use the show outbound command to see how the best match is judged by the PIX Firewall.
Usage Notes
1
If outbound commands are not specified, the default behavior is to permit all outbound traffic and services from inside hosts.
2
After adding, changing, or removing an outbound and apply statement group, use the clear xlate command to make the IP addresses available in the translation table.
3
The outbound commands are processed linearly within a list_ID. In addition, list_IDs are processed sequentially in descending order. For example, the first statement you specify in an outbound list is processed first, then the next outbound statement in that list, and so on. Similarly, list_ID 10 is processed before list_ID 20, and so on.
4
When using outbound commands, it is often helpful to deny or permit access to the many before you deny or permit access to the specific. Start with an interface-wide specification such as the following that denies all hosts from starting connections:
outbound 1 deny 0 0 0apply (inside) 1 outgoing_srcThen add statements that permit or deny hosts access to specific ports, for example:
outbound 1 deny 0 0 0outbound 1 permit 10.1.1.1 255.255.255.255 23 tcp
outbound 1 permit 10.1.1.1 255.255.255.255 80 tcp
apply (inside) 1 outgoing_src
If you used the except option, you could state this same example as follows:
outbound 1 deny 0 0 0outbound 1 except 204.31.17.11 255.255.255.255 23 tcp
outbound 1 except 204.31.17.11 255.255.255.255 80 tcp
apply (inside) 1 outgoing_srcIn the above except statement, IP address 204. 31.17.11 is the destination IP address, not the source address. This means that everyone is denied outbound access, except those users going to 204.31.17.11 via Telnet or HTTP (80).
5
The Java applet blocking feature removes applets that come into the HTTP port. The
PIX Firewall removes applets containing a Java signature anywhere in the packet, but does not remove applets encapsulated in some archive files. Legitimate, non-Java files with Java signatures are also blocked.6
If you permit access to port 80 (http), this also permits Java applets to be downloaded.
You must have a specific deny statement to block Java applets.7
The maximum number of outbound list entries in a configuration is 2000.
8
Outbound lists have no effect on conduits which operate on inbound connections.
Examples
The first outbound group sets inside hosts so that they can only see and Telnet to perimeter hosts, and do DNS lookups. In this example, the perimeter network address is 204.0.0.0 and the network mask is 255.255.255.0:
outbound 9 deny 0.0.0.0 0.0.0.0 0 0outbound 9 except 204.0.0.0 255.255.255.0 23 tcpoutbound 9 except 0.0.0.0 0.0.0.0 53 udpThe next outbound group in this same example lets hosts 10.1.1.11 and 10.1.1.12 go anywhere:
outbound 11 deny 0.0.0.0 0.0.0.0 0 0outbound 11 permit 10.1.1.11 255.255.255.255 0 0outbound 11 permit 10.1.1.12 255.255.255.255 0 0outbound 11 permit 0.0.0.0 0.0.0.0 21 tcpoutbound 11 permit 10.3.3.3 255.255.255.255 143 tcpThis last outbound group in this same example lets hosts on the perimeter only access TCP ports 389 and 30303 and UDP port 53 (DNS). Finally, the apply statements set the outbound groups so that the permit and deny rules affect access to all external addresses.
outbound 13 deny 0.0.0.0 0.0.0.0 0 0outbound 13 permit 0.0.0.0 0.0.0.0 389 tcpoutbound 13 permit 0.0.0.0 0.0.0.0 30303 tcpoutbound 13 permit 0.0.0.0 0.0.0.0 53 udpapply (inside) 9 outgoing_srcapply (inside) 11 outgoing_srcapply (perim) 13 outgoing_srcControlling Outbound Connections
The following example prevents all inside hosts from starting outbound connections:
outbound 1 deny 0 0 0apply (inside) 1 outgoing_srcThe 0 0 0 at the end of the command means all IP addresses (0 is the same as 0.0.0.0), with a 0.0.0.0 subnet mask and for all services (port value is zero).
Conversely, the following example permits all inside hosts to start connections to the outside (this is the default if an access list is not created):
outbound 1 permit 0 0 0apply (inside) 1 outgoing_srcControlling Inside Hosts' Access to Outbound Services
The following example prevents inside host 192.168.1.49 from accessing the World Wide Web
(port 80):outbound 11 deny 192.168.1.49 255.255.255.255 80 tcpapply (inside) 11 outgoing_srcControlling Inside Hosts' Access to Outside Servers
If your employees are spending too much time examining GIF images on a particular site with two web servers, you can use the following example to restrict this access:
outbound 12 deny 192.168.146.201 255.255.255.255 80 tcpoutbound 12 deny 192.168.146.202 255.255.255.255 80 tcpapply (inside) 12 outgoing_destPreventing Use of Java Applets
The following example prevents all inside users from executing Java applets on the inside network:
outbound 1 deny 0 0 javaapply (inside) 1 outgoing_srcUsing except Statements
An except statement only provides exception to items with the same list_ID. Consider the following example:
outbound 9 deny 0.0.0.0 0.0.0.0 0 0outbound 9 except 20.0.0.0 255.0.0.0 23 tcpoutbound 9 except 0.0.0.0 0.0.0.0 53 udpoutbound 11 deny 0.0.0.0 0.0.0.0 0 0outbound 11 permit 10.1.1.11 255.255.255.255 0 0outbound 11 permit 10.1.1.12 255.255.255.255 0 0outbound 11 permit 0.0.0.0 0.0.0.0 21 tcpoutbound 11 permit 10.3.3.3 255.255.255.255 143 tcpoutbound 13 deny 0.0.0.0 0.0.0.0 0 0outbound 13 permit 0.0.0.0 0.0.0.0 389 tcpoutbound 13 permit 0.0.0.0 0.0.0.0 30303 tcpoutbound 13 permit 0.0.0.0 0.0.0.0 53 udpIn the preceding examples, the following two statement work against other statements in list 9 but not in lists 11 and 13.
outbound 9 except 20.0.0.0 255.0.0.0 23 tcpoutbound 9 except 0.0.0.0 0.0.0.0 53 udpIn the following example, the set of deny, permit, and except option statements denies everybody from connecting to external hosts except for DNS queries and Telnet connections to hosts on 20.0.0.0. The host with IP address 10.1.1.11 is permitted outbound access, and has access to everywhere except to 20.0.0.0 via Telnet and anywhere to use DNS:
outbound 1 deny 0.0.0.0 0.0.0.0 0 tcpoutbound 1 permit 10.1.1.11 255.255.255.255 0 tcpoutbound 1 except 20.0.0.0 255.0.0.0 23 tcpoutbound 1 except 0.0.0.0 0.0.0.0 53 udpapply (inside) outgoing_srcpager
Enable or disable screen paging. (Privileged mode.)
pager [lines lines]
no pager
show pager
Syntax Definition
lines
The number of lines before the More prompt appears. The minimum is 1.
Use 0 to disable paging.
Usage Guidelines
The pager lines command lets you specify the number of lines in a page before the More prompt appears. The pager command enables display paging, and no pager disables paging and lets output display completely without interruption. If you set pager lines to some value and want to revert back to the default, enter the pager command without options.
Use pager 0 to disable paging.
The show pager command displays pager status.
When paging is enabled, the following prompt appears:
<--- More --->The More prompt uses syntax similar to the UNIX more command:
•
To view another screenful, press the Space bar.
•
To view the next line, press the Enter key.
To return to the command line, press the q key.
Example
pixfirewall# pager lines 2pixfirewall# ping inside 10.0.0.4210.0.0.42 NO response received -- 1010ms10.0.0.42 NO response received -- 1000ms<--- More --->passwd
Set password for Telnet and PIX Firewall Manager access to the firewall console. (Privileged mode.)
passwd password [encrypted]
show passwd
Syntax Description
Usage Guidelines
The passwd command sets a password for Telnet and PIX Firewall Manager access to the firewall console. An empty password is also changed into an encrypted string. However, any use of a write command displays or writes the passwords in encrypted form. Once passwords are encrypted, they are not reversible back to plain text.
Note
Write down the new password and store it in a manner consistent with your site's security policy. Once you change this password, you cannot view it again.
See also: enable password.
Example
passwd watag00s1amshow passwdpasswd jMorNbK0514fadBh encryptedperfmon
View performance information. (Privileged mode.)
perfmon interval seconds
perfmon quiet | verbose
show perfmon
Syntax Description
Usage Guidelines
The perfmon command lets you monitor the PIX Firewall's performance. Use the show perfmon command to view the information immediately. Use the perfmon verbose command to display the information every two minutes continuously. Use the perfmon interval seconds command with the perfmon verbose command to display the information continuously every number of seconds you specify.
Note
The show perfmon command does not display in a Telnet console session.
Use the perfmon quiet command to disable the display.
An example of the performance information is:
This information lists the number of translations, connections, WebSENSE requests, address translations (called "fixups"), and AAA transactions that occur each second.
Example
The following commands display the performance monitor statistics every 30 seconds on the PIX Firewall console:
perfmon interval 30perfmon verboseping
Determine if other IP addresses are visible from the PIX Firewall. (Privileged mode.)
ping if_name ip_address
Syntax Description
Usage Guidelines
The ping command determines if the PIX Firewall has connectivity or if a host is available on the network. The command output shows if the response was received; that is, that the host exists on the network. If the host is not responding, ping displays "NO response received." Use show interface to ensure that the PIX Firewall is connected to the network and is passing traffic.
If you want internal hosts to be able to ping external hosts, you must create an ICMP conduit for echo reply; for example, to give ping access to all hosts, use the conduit permit icmp any any command.
If you are pinging through PIX Firewall between hosts or routers, but the pings are not successful, use the debug icmp trace command to monitor the success of the ping. If pings are both inbound and outbound, they are successful.
Example
The ping command makes three attempts to reach an IP address:
ping inside 192.168.42.54192.168.42.54 response received -- 0Ms192.168.42.54 response received -- 0Ms192.168.42.54 response received -- 0Msquit
Exit configuration or privileged mode. (All modes.)
quit
Usage Guidelines
Use the quit command to exit configuration or privileged mode.
Example
pixfirewall(config)# quitpixfirewall# quitpixfirewall>radius-server
Specify a RADIUS server for use with the aaa command. (Configuration mode.)
radius-server [(if_name)] host ip_address key [timeout seconds]
clear radius-server
no radius-server [(if_name)] host [[ip_address] [key]]
show radius-server
Syntax Description
Usage Guidelines
Specify a RADIUS server. Use show radius-server to view the information.
Note
You can have a total of 16 URL servers, RADIUS servers, and TACACS+ servers. For example, if you have 11 URL servers and 5 TACACS+ servers, if you want to add a RADIUS server, you must disable one of either the URL or TACACS+ servers from the PIX Firewall configuration to free up a server entry for the RADIUS server.
Servers are used in the order entered in the configuration. If the server is off-line or fails, the next server is checked. This continues until a working server is found. Use no radius-server to disable access to a host.
Use the radius-server command before you use the aaa command. The aaa command enables authentication, and accounting services for access to the RADIUS server you designate.
Note
PIX Firewall does not support RADIUS authorization services.
The clear radius-server command removes all radius-server entries from the configuration.
Before using the clear radius-server command, remove the aaa commands that enable RADIUS authentication or accounting.
Example
radius-server (perimeter) host 192.168.42.42 whatakey!@#$%^&*show radius-serverradius-server (perimeter) host 192.168.42.42 whatakey!@#$%^&*aaa authentication any outside 192.168.42.42 255.255.255.255 0 0 radiusreload
Reboot and reload the configuration. (Privileged mode.)
reload
Usage Guidelines
The reload command reboots the PIX Firewall and reloads the configuration from a bootable floppy
disk or, if a diskette is not present, from Flash memory.
Note
You are prompted for confirmation before starting with "Proceed with reload?".
Any response other than n causes the reboot to occur.
Note
Configuration changes not written to Flash memory are lost after reload. Before rebooting, store the current configuration in Flash memory with the write memory command.
Example
reloadProceed with reload? [confirm] yRebooting...PIX Bios V2.7...rip
Change RIP settings. (Configuration mode.)
rip if_name default|passive
no rip [if_name default|passive]
show rip if_name
Syntax Description
Usage Guidelines
The rip passive command enables IP routing table updates from received RIP (Routing Information Protocol) broadcasts. Use show rip to display the current RIP settings. Use no rip to disable the PIX Firewall IP routing table updates. The default is to enable IP routing table updates.
Example
show riprip outside passiveno rip outside defaultrip inside passiveno rip inside defaultrip inside defaultshow riprip outside passiveno rip outside defaultrip inside passiverip inside defaultroute
Enter a static or default route for the specified interface. (Configuration mode.)
route if_name ip_address netmask gateway_ip [metric]
clear route [if_name ip_address [netmask gateway_ip]]
no route [if_name ip_address [netmask gateway_ip]]
show route
Syntax Description
Usage Guidelines
Use the route command to enter a default or static route for an interface. To enter a default route, set ip_address and netmask to 0.0.0.0, or the shortened form of 0. All routes entered using the route command are stored in the configuration when it is saved.
Create static routes to access networks connected outside a router on any interface. The effect of a static route is like stating "to send a packet to the specified network, give it to this router." For example, PIX Firewall sends all packets destined to the 192.168.42.0 network through the 192.168.1.5 router with this static route statement:
route dmz 192.168.42.0 255.255.255.0 192.168.1.5 1
Note
If the linkpath 0 0 command is used, the outside interface's default route statement is overridden and all outbound traffic is routed through Private Link to a central PIX Firewall unit.
Examples
Specify one default route statement for the outside interface, which in this example, has an IP address of 192.150.50.1:
route outside 0 0 192.150.50.1 1For static routes, if two networks, 10.1.2.0 and 10.1.3.0 connect via a hub to the dmz1 interface router at 10.1.1.4, add these static route statements to provide access to the networks:
route dmz1 10.1.2.0 255.0.0.0 10.1.1.4 1route dmz1 10.1.3.0 255.0.0.0 10.1.1.4 1service
Reset inbound connections. (Configuration mode.)
service resetinbound
show service
Syntax Description
Usage Guidelines
The service command works with all inbound TCP connections to statics whose conduits or uauth (user authorization) do not allow inbound. One use is for resetting IDENT connections. If an inbound TCP connection is attempted and denied, you can use the service resetinbound command to return an RST (reset flag in the TCP header) to the source. Without the option, the PIX Firewall drops the packet without returning an RST.
For use with IDENT, the PIX Firewall sends a TCP RST to the host connecting inbound and stops the incoming IDENT process so that email outbound can be transmitted without having to wait for IDENT to time out. In this case, the PIX Firewall sends a syslog message stating that the incoming connection was a denied connection. Without service resetinbound, the PIX Firewall drops packets that are denied and generates a syslog message stating that the SYN was a denied connection. However, outside hosts keep retransmitting the SYN until the IDENT times out.
When an IDENT connection is timing out, you will notice that connections slow down. Perform a trace to determine that IDENT is causing the delay and then invoke the service command.
The service resetinbound command provides a safer way to handle an IDENT connection through the PIX Firewall. Ranked in order of security from most secure to less secure are these methods for handling IDENT connections:
1
Use the service resetinbound command.
2
Use the established command with the permitto tcp 113 options.
3
Create a static and conduit to open TCP port 113.
When using the aaa command, if the first attempt at authorization fails and a second attempt causes a timeout, use the service resetinbound command to reset the client that failed the authorization so that it will not retransmit any connections. An example authorization timeout message in Telnet is:
Unable to connect to remote host: Connection timed outExample
service resetinboundshow serviceservice resetinboundsession
Access an embedded AccessPro router console. (Privileged mode.)
session enable
no session
show session
Note
Only use this command if you have an AccessPro router installed in your PIX Firewall.
Syntax Description
Usage Guidelines
The session command lets you specify Cisco IOS commands on an AccessPro router console when the router is installed in your PIX Firewall. Use COM port 4 on the AccessPro router to communicate with the PIX Firewall.
Exit the router console session by entering tilde-dot (~.). Press the tilde key and when you hear a bell sound from your terminal, press the dot key.
While a router console session is occurring, the PIX Firewall disables failover because they both require the same interrupts.
Example
This example enables an AccessPro session, starts the session, and then disables it.
session enableSession has been enabled.sessionWarning: FAILOVER has been disabled!!!Attempting session with embedded router, use ~. to quit!acpro> ~.no sessionSession has been disabledsessionSession is not enabledshow
View command information. (Differs by mode.)
show ?
Usage Guidelines
This command without arguments or the show ? command lets you view the names of the show commands and their descriptions. Explanations for each show command are provided on the respective command page for the command itself where appropriate; for example, show arp is described on the arp command page.
Note
The show commands that do not have a command equivalent shown in this section are described on their respective command pages; for example, the show interface command is described on the interface command page.
If the pager command is enabled and when 24 lines display, the listing pauses, and the following prompt appears:
<--- More --->The More prompt uses syntax similar to the UNIX more command:
•
To view another screenful, press the Space bar.
•
To view the next line, press the Enter key.
•
To return to the command line, press the q key.
Example
show ?? help ...show blocks
Show system buffer utilization. (Privileged mode.)
show blocks
Usage Guidelines
This command lists preallocated system buffer utilization. In the show blocks listing, the SIZE column displays the block type. The MAX column is the maximum number of allocated blocks. The LOW column is the fewest blocks available since last reboot. The CNT column is the current number of available blocks. The FAILED column is not currently used. A zero in the LOW column indicates a previous event where memory exhausted. A zero in the CNT column means memory is exhausted now. Exhausted memory is not a problem as long as traffic is moving through the PIX Firewall. You can use the show conn command to see if traffic is moving. If traffic is not moving and the memory is exhausted, a problem may be indicated.
Example
pixfirewall(config)# show blocksSIZE MAX LOW CNT FAILED4 1600 1600 160080 100 97 97256 80 79 791550 788 402 40465536 8 8 8show checksum
Display the configuration checksum. (Unprivileged mode.)
show checksum
Usage Guidelines
This command displays four groups of hexadecimal numbers that act as a digital summary of the contents of the configuration. This same information stores with the configuration when you store it in Flash memory. By using the show config command and viewing the checksum at the end of the configuration listing and using the show checksum command, you can compare the numbers to see if the configuration has changed. The PIX Firewall tests the checksum to determine if a configuration has not been corrupted.
Example
show checksumCryptochecksum: 1a2833c0 129ac70b 1a88df85 650dbb81show conn
Display all active connections. (Privileged mode.)
show conn [count] [foreign|local ip[-ip2] [netmask mask]] [protocol tcp|udp|prot]
[fport|lport port1[-port2]] [state up[,finin][,finout] [,http_get] [,smtp_data] [,smtp_banner]
[,smtp_incomplete][,nojava] [,data_in] [,data_out] [,sqlnet_fixup_data]
[,conn_inbound] [,rpc] [,h323] [,dump]Syntax Description
count
Display only the number of used connections.
foreign| local ip[-ip2] netmask mask
Display active connections by the foreign IP address or by local IP address. Qualify foreign or local active connections by network mask.
protocol tcp|udp|prot
Display active connections by protocol type. prot is a protocol specified by number. Refer to the "Protocols" section in Chapter 1, "" for a list of valid protocol literal names.
fport|lport port1[-port2]
Display foreign or local active connections by port. Refer to the "Ports" section in Chapter 1, "" for a list of valid port literal names.
state
Display active connections by their current state: up (up), FIN inbound (finin), FIN outbound (finout), HTTP get (http_get), SMTP mail data (smtp_data), SMTP mail banner (smtp_banner), incomplete SMTP mail connection (smtp_incomplete), an outbound command denying access to Java applets (nojava), inbound data (data_in), outbound data (data_out), SQL*Net data fix up (sqlnet_fixup_data), inbound connection (conn_inbound), RPC connection (rpc) , H.323 connection (h323), dump clean up connection (dump).
Usage Guidelines
The show conn command displays the number and information about the active TCP connections. lists connection slot flags:
Example
show conn6 in use, 6 most usedTCP out 204.31.17.41:80 in 10.3.3.4:1404 idle 0:00:00 Bytes 11391 flags UHrIOTCP out 204.31.17.41:80 in 10.3.3.4:1405 idle 0:00:00 Bytes 3709 flags UHrIOTCP out 204.31.17.41:80 in 10.3.3.4:1406 idle 0:00:01 Bytes 2685 flags UHrIOTCP out 204.31.17.41:80 in 10.3.3.4:1407 idle 0:00:01 Bytes 2683 flags UHrIOTCP out 204.31.17.41:80 in 10.3.3.4:1403 idle 0:00:00 Bytes 15199 flags UHrIOTCP out 204.31.17.41:80 in 10.3.3.4:1408 idle 0:00:00 Bytes 2688 flags UHrIOUDP out 192.150.50.70:24 in 10.3.3.4:1402 idle 0:01:30 flags dUDP out 192.150.50.70:23 in 10.3.3.4:1397 idle 0:01:30 flags dUDP out 192.150.50.70:22 in 10.3.3.4:1395 idle 0:01:30 flags dIn this example, host 10.3.3.4 on the inside has accessed a web site at 204.31.17.41. The global address on the outside interface is 192.150.50.70. The flags indicate that the first five TCP connections are up (U), for HTTP (H), in use (r), and that data has gone in and out. The last three UDP connections are in dump (clean up) state.
show history
Display previously entered lines. (Privileged mode.)
show history
Usage Guidelines
This command displays previously entered commands. You can examine commands individually with the up and down arrows or by entering ^p to view previously entered lines or ^n to view the next line.
Example
show historyenable...show memory
Show system memory utilization. (Privileged mode.)
show memory
Usage Guidelines
This command displays a summary of the maximum physical memory and current free memory available to the PIX Firewall operating system. Memory in the PIX Firewall is allocated as needed.
Example
show memorynnnnnnnn bytes total, nnnnnnn bytes freeshow processes
Display processes. (Privileged mode.)
show processes
Usage Guidelines
This command displays a listing of running processes. Processes are lightweight threads requiring only a few instructions. In the listing, PC is the program counter, SP is the stack pointer, STATE is the address of a thread queue, Runtime is the number of milliseconds that the thread has been running, SBASE is the stack base address, Stack is the current number of bytes used and the total size of the stack, and Process lists the thread's function.
Example
show processesPC SP STATE Runtime SBASE Stack ProcessLsi 800125de 803603d0 80075ba0 0 8035f410 4004/4096 arp_timer...show tech-support
View information to help a support analyst. (Privileged mode.)
show tech-support
Usage Guidelines
The show tech-support command lists information technical support analysts need to help you diagnose PIX Firewall problems.
Example
show tech-supportPIX Version 4.3(n) nnnCompiled on day dd-mmm-98 hh:mm by pixbuildpixfirewall up n days n hours n minsHardware: Pentium 133, 16 MB RAM, CPU Pentium 133 MHz...show traffic
Shows interface transmit and receive activity. (Privileged mode.)
show traffic
Usage Guidelines
This command lists the number of packets and bytes moving through each interface. The number of seconds is the duration the PIX Firewall has been online since the last reboot.
Example
show trafficoutside:received (in 3786 secs):97 packets 6191 bytes42 pkts/sec 1 bytes/sectransmitted (in 3786 secs):99 packets 10590 bytes0 pkts/sec 2 bytes/sec ...show version
View the PIX Firewall operating information. (Unprivileged mode.)
show version
Usage Guidelines
This command lets you view the PIX Firewall's software version, operating time since last reboot, processor type, Flash memory type, interface boards, and serial number (BIOS ID). If the Flash memory type states "atmel," then it is the 2 MB unit; otherwise, it is the 512 KB version. PIX Firewall units with serial numbers 06002016 and higher have 2 MB Flash memory cards, as do all PIX10000 units, and all PIX510 and PIX520 units.
Example
show versionPIX Version 4.3(n)nnn PointCompiled on Sat 16-May-98 04:08 by pixbuildFinesse Bios V3.3pixfirewall up 100 days 6 hours 17 minsHardware: Pentium 133, 16 MB RAM, CPU Pentium 133 MHzFlash atmel @ base 0x3000: ethernet0: address is 00a0.c90a.eb4d1: ethernet1: address is 00a0.c986.8eea2: ethernet2: address is 00a0.c90a.eb43Serial Number: 0600nnnnsnmp-server
Provide SNMP event information. (Configuration mode.)
snmp-server community key
snmp-server contact text
snmp-server host if_name local_ip
snmp-server location text
snmp-server enable traps
clear snmp-server [contact text]
clear snmp-server [host if_name local_ip]
clear snmp-server [location text]
no snmp-server [contact text]
no snmp-server [host if_name local_ip]
no snmp-server [location text]
no snmp-server enable traps
show snmp-server
Syntax Description
Usage Guidelines
Use the snmp-server command to identify your name, location, and the host to which SNMP traps should be sent. Refer to "Step 15 - Enable Syslog" in Chapter 2, "" for more information on SNMP events. The clear snmp-server and no snmp-server commands remove the information. The show snmp-server command displays the information.
To send traps to an SNMP server:
Step 1
Identify the IP address of the SNMP server with the snmp-server host command.
Step 2
Set the snmp-server options for location, contact, and the community password as required.
Step 3
Set the logging level with the logging trap command; for example:
logging trap debuggingCisco recommends that you use the debugging level during initial setup and during testing. Thereafter, set the level from debugging to errors for production use.
Step 4
Start sending syslog messages to the server with the logging on command.
Only syslog messages in the syslog MIB are controlled by this command.
Example
snmp-server community wallawallabingbangsnmp-server location Building 42, Sector 54snmp-server contact Sherlock Holmessnmp-server host perimeter 10.1.2.42show snmpsnmp-server host 10.1.2.42snmp-server location Building 42, Sector 54snmp-server contact Sherlock Holmessnmp-server community wallawallabingbangstatic
Map local IP address to a global IP address. (Configuration mode.)
static [(internal_if_name, external_if_name)] global_ip local_ip [netmask network_mask]
[max_conns [em_limit]] [norandomseq]no static [[(internal_if_name, external_if_name)] global_ip local_ip[netmask network_mask]
[max_conns [em_limit]] [norandomseq]]show static
Syntax Description
Usage Guidelines
The static command creates a permanent mapping (called a static translation slot or "xlate") between a local IP address and a global IP address. Use the static and conduit commands when you are accessing an interface of a higher security level from an interface of a lower security level; for example, when accessing the inside from a perimeter or the outside interface.
The interface names on the static command may seem confusing at first. This is further complicated by how NAT is handled on the PIX Firewall. If NAT is disabled, with the nat 0 command, statics are specified with a different set of rules than when NAT is enabled. For either no NAT or NAT, the rule of which command to access an interface stays the same as shown in .
assumes that the security levels are 40 for dmz1 and 60 for dmz2.
With NAT Enabled
NAT (Network Address Translation) is enabled with the nat n command where "n" has the value 1 or greater; for example, nat 1 0 0.
Always specify the interface name of the highest security level interface you are accessing, followed by the lower security level interface. The IP addresses are also confusing because the first IP address you specify is for the lower security level interface. The second IP address is for the higher security level interface. The way to remember this is as follows:
static (high,low) low high
For example, assume you have four interfaces on the PIX Firewall that have security levels set with the nameif command as follows:
nameif ethernet0 outside security0nameif ethernet1 inside security100nameif ethernet2 dmz1 security40nameif ethernet3 dmz2 security60To access the inside from the outside interface, you need a static command like:
static (inside,outside) outside_ip_address inside_ip_address netmask maskReplace outside_ip_address with the global IP address (an IP address on the lower security level interface). Replace inside_ip_address with the IP address of the host on the higher security level interface that you want to grant access to. Use these replacements in the rest of the commands in this section. Replace mask with 255.255.255.255 for host addresses, except when subnetting is in effect; for example, 255.255.255.128. For network addresses, use the appropriate class mask; for example, for Class A networks, use 255.0.0.0.
To access the inside from the dmz1 interface, you need a static command like:
static (inside,dmz1) dmz1_ip_address inside_ip_address netmask maskTo access the inside from the dmz2 interface, you need a static command like:
static (inside,dmz2) dmz2_ip_address inside_ip_address netmask maskTo access the dmz2 interface from the dmz1 interface, you need a static command like:
static (dmz2,dmz1) dmz1_ip_address dmz2_ip_address netmask maskTo go the other way around, from a higher security level interface to a lower security level interface, use the nat and global commands. For example, to access dmz1 from dmz2, use these commands:
nat (dmz2) 1 0 0global (dmz1) 1 global_ip_address-global_ip_addressReplace global_ip_address-global_ip_address with the IP address range of the addresses in the pool of global addresses. The nat command specifies the name of the higher security level interface; the pool of global addresses are on the lower security level interface.
View the nat command page for more information on using these commands.
Note
If you use a static command, you must also use a conduit command. The static command makes the mapping, the conduit command lets users access the static mapping.
The first IP address you specify in the static command is the first IP address you specify in the conduit command as shown in this example:
static (dmz2,dmz1) 10.1.1.1 192.168.1.1 netmask 255.255.255.255conduit permit tcp host 10.1.1.1 10.1.1.0 255.255.255.0The static command maps the address 10.1.1.1 on the dmz1 interface so that users on the dmz1 interface can access the 192.168.1.1 host on the dmz2 interface. The conduit command lets any users in the 10.1.1.0 network access the 10.1.1.1 address over any TCP port.
Note
Always make conduit statements as specific as possible. Using the any option to allow any host access should be used with caution for conduits used with statics.
With No-NAT
With no-NAT, the static command has a different sense of logic. With NAT disabled, addresses on both sides of the firewall are registered addresses. Between interfaces, addresses must be on different subnets that you control with subnetting. Refer to Appendix D, "" for more information.
Without address translation, you protect addresses on the inside or perimeter interfaces by not providing access to them. Without a conduit statement, the inside host cannot be accessed on the outside and is, in effect, invisible to the outside world. Conversely, only by opening statics and conduits to servers on the inside or perimeter interfaces, do the hosts become visible.
The format of the static command becomes different:
static (high,low) high high
Again, the security level set for each interface with the nameif command determines what information you fill in. You are using static to access a higher security interface from a lower security interface. The IP address you want visible on the lower security interface is that of the higher security interface. This is the IP address users on the lower security interface's network will use to access the server on the higher security level interface's network. Because address translation is not occurring, the actual address of the server is presented as both the visible address and the address of the host.
For example, a web server on the dmz, 204.31.17.65 needs to be accessible by users on the outside. The static and conduit statements are:
static (dmz,outside) 204.31.17.65 204.31.17.65 netmask 255.255.255.192conduit permit tcp host 204.31.17.65 eq www anyThe static command presents the 204.31.17.65 address on the outside interface. The DNS server on the outside would map this IP address to the domain of the company; for example, domain1.com. Users accessing domain1.com are permitted to access the web server via port 80 by the conduit command.
Another example of no-NAT statics would be when users on dmz1 need to access a web server on dmz2. The network uses a Class C address and subnets it with the .192 subnet. Addresses 204.31.17.65 to 204.31.17.126 are on dmz1, and addresses 204.31.17.129 to 204.31.17.190 are on dmz2. The web server is at 204.31.17.142. The static and conduit statements are:
static (dmz2,dmz1) 204.31.17.142 204.31.17.142 netmask 255.255.255.192conduit permit tcp host 204.31.17.142 eq www 204.31.17.64 255.255.255.192The static statement opens access to the web server at 204.31.17.142. The conduit statement permits access to the web server only on port 80 (www) and further refines the access to stipulate that only users on the 204.31.17.64 subnet can access the web server. Refer to Appendix D, "" for more information on subnetting.
Additional static Information
After changing or removing a static statement, use the clear xlate command. If the previous condition persists, save your configuration with the write memory command and then reboot the PIX Firewall.
You can create a single mapping between the global and local hosts, or create a range of statics known as net statics.
The static command determines the network mask of network statics by the netmask option or by the number in the first octet of the global IP address. The netmask option can be used to override the number in the first octet. If the address is all zeros where the net mask is zero, then the address is a net address.
Note
Do not create statics with overlapping global IP addresses.
You can have as many statics as needed as long the total size of your configuration does not exceed 1,625,088 characters if your PIX Firewall has a 2 MB Flash memory board, or 102,400 characters if your PIX Firewall has a 512 KB Flash memory board. To determine what type of board is in your firewall, use the show version command. The 2 MB board contains this statement in the display:
Flash atmel @ base 0x300
See also: conduit.Examples
The example that follows creates a static command and then permits users to call in through H.323 using Intel InternetPhone or MS NetMeeting to 10.1.1.222 using IP address 204.31.17.222 to 10.1.1.188 using IP address 204.31.17.188, and so on. The net static command that follows maps addresses 204.31.17.1 through 204.31.17.254 to local addresses 10.1.1.1 through 10.1.1.254.
static (inside, outside) 204.31.17.0 10.1.1.0 8 50conduit permit tcp host 204.31.17.0 eq h323 anyThe following example shows the commands used to disable Mail Guard:
static (dmz1,outside) 204.31.17.1 10.1.1.1 netmask 255.255.255.255conduit permit tcp host 204.31.17.1 eq smtp anyno fixup protocol smtp 25In this example, the static command sets up a global address to permit outside hosts access to the 10.1.1.1 mail server host on the dmz1 interface. (The MX record for DNS needs to point to the 204.31.17.1 address so that mail is sent to this address.) The conduit command lets any outside users access the global address through the SMTP port (25). The no fixup protocol command disables the Mail Guard feature.
syslog
Enable syslog message facility. Obsolete command replaced by the logging command. (Privileged mode.)
Note
Refer to the logging command for more information. The syslog command is available for backward compatibility.
sysopt
Change PIX Firewall system options. (Configuration mode.)
sysopt connection enforcesubnet
no sysopt connection enforcesubnet
sysopt connection tcpmss bytes
no sysopt connection tcpmss bytes
sysopt connection timewait
no sysopt connection timewait
sysopt security fragguard
no sysopt security fragguard
clear sysopt
show sysopt
Syntax Description
Usage Guidelines
The sysopt commands let you tune various PIX Firewall security and configuration features. In addition, you can use this command to disable the PIX Firewall IP Frag Guard feature.
sysopt connection enforcesubnet
The sysopt connection enforcesubnet command prevents external users from spoofing internal addresses. This command prevents packets with a source address belonging to the destination subnet from traversing the PIX firewall. For example if a packet arrives from the outside but has a source address belonging to the inside subnet, the PIX Firewall does not let the packet through.
Note
Do not use this command if the internal and external interfaces are on the same logical subnet as may exist when NAT is disabled.
sysopt connection tcpmss
The sysopt connection tcpmss command forces proxy TCP connections to have a maximum segment size no greater than bytes. This command requests that each side not send a packet of a size greater than bytes at any time during the initial TCP connection establishment.
Note
If the client sending the proxy TCP connection does not announce a maximum segment size, PIX Firewall assumes that the RFC 793 default value of 536 bytes is in effect. If the client announces a maximum segment size larger than the number of bytes, PIX Firewall reduces the maximum segment size to bytes.
The bytes value can be a minimum of 28 and any maximum number. You can disable this feature by setting bytes to zero. The default is 1460 bytes, which Cisco recommends for Ethernet and mixed Ethernet and Token Ring environments. If the PIX Firewall has all Token Ring interfaces, you can set bytes to 4056. However, if even one link along the path through the network is not a Token Ring, setting bytes to such a high value may cause poor throughput. In its 1460 byte default value, this command increases throughput of the sysopt security fragguard command.
The TCP maximum segment size is the maximum size that an end host can inject into the network at one time (see RFC 793 for more information on the TCP protocol). The sysopt connection tcpmss command is recommended in a network environment being attacked by an overly aggressive TCP or HTTP stack with a faulty path MTU value that is degrading the performance of the PIX Firewall IP Frag Guard feature. Environments where one or more end hosts reside on a Token Ring network are especially susceptible to attack by aggressive TCP or HTTP stacks.
Note
This command only works when the sysopt security fragguard command is enabled. Although, not advised for normal use of this feature, if you encounter the syslog IPFRAG messages 209001 and 209002, you can raise the bytes value.
sysopt connection timewait
The sysopt connection timewait command forces each TCP connection to linger in a shortened TIME_WAIT state of at least 15 seconds.
The connection timewait option is necessary for end host applications whose default TCP terminating sequence is simultaneous close instead of the normal shutdown sequence (see RFC 793). In simultaneous close, four TCP segments are exchanges in the shutdown instead of the normal three.
The default behavior of the PIX Firewall is to track the normal three shutdown sequence and release the connection after the third segment. This quick release heuristic enables the PIX Firewall to sustain high connection rate.
However with simultaneous close, the quick release will force one side of the connection to linger in the CLOSING state (see RFC 793). Many sockets in the CLOSING state can degrade the performance of an end host. For instance, some WinSock mainframe clients are known to exhibit this behavior and degrade the performance of the mainframe server. Old versions of HP/UX are also susceptible to this behavior. Enabling the connection timewait option enables a "quiet time" window for the abnormal close down sequence to complete.
The no sysopt connection timewait command disables the option, which is off by default.
Note
Use of the sysopt connection timewait command may impact PIX Firewall performance especially with low memory configuration and highly dynamic traffic pattern such as HTTP.
sysopt security fragguard
The sysopt security fragguard command enables the IP Frag Guard feature. This feature is disabled by default. This feature enforces two addition security checks in addition to the security checks recommend by RFC 1858 against the many IP fragment style attacks: teardrop, land, and so on. First, each non-initial IP fragments is required to be associated with an already seen valid initial IP fragments. Second, IP fragments are rated to 100 full IP fragmented packets per second to each internal host.
The IP Frag Guard feature operates on all interfaces in the PIX Firewall and cannot be selectively enabled or disabled by interface.
PIX Firewall uses the security fragguard command to enforce the security policy determined by a conduit permit or conduit deny command to permit or deny packets through the PIX Firewall.
Note
Use of the sysopt security fragguard command breaks normal IP fragmentation conventions. However, not using this command exposes PIX Firewall to the possibility of IP fragmentation attacks. Cisco recommends that packet fragmentation not be permitted on the network if at all possible.
Note
If PIX Firewall is used as a tunnel for FDDI packets between routers, disable the security fragguard feature.
Note
Because Linux sends IP fragments in reverse order, fragmented Linux packets will not pass through the PIX Firewall with the sysopt security fragguard command enabled.
The show sysopt command lists the sysopt commands in the configuration. The clear sysopt command resets the sysopt command to default settings. The no sysopt security fragguard disables the IP Frag Guard feature.
Example
no sysopt security fragguardshow sysoptsysopt security fragguardno sysopt connection tcpmssno sysopt connection timewaittacacs-server
Specify a TACACS+ server for use with the aaa command. (Privileged mode.)
tacacs-server [(if_name)] host ip_address [key] [timeout seconds]
clear tacacs-server
no tacacs-server [(if_name)] host [[ip_address] [key]]
show tacacs-server
Syntax Description
Usage Guidelines
Specify a TACACS+ server. Use show tacacs-server to examine the information.
Note
You can have a total of 16 URL servers, RADIUS servers, and TACACS+ servers. For example, if you have 10 RADIUS servers and 6 URL servers, if you want to add a TACACS+ server, you must disable one of either the RADIUS or URL servers from the PIX Firewall configuration to free up a server entry for the TACACS+ server.
Servers are used in the order entered in the configuration. If the server is offline or fails, the next server is checked. This continues until a working server is found. Use the tacacs-server command before you use the aaa command. The aaa command enables authentication, authorization, and accounting services for access to the TACACS+ server you designate.
The clear tacacs-server command removes all tacacs-server entries from the configuration.
Note
Before using the clear tacacs-server command, remove the aaa commands that enable TACACS+ authentication, authorization, or accounting.
Note
The key parameter is optional. If you do not specify a key, communications with the TACACS+ server are not encrypted.
Example
tacacs-server (perimeter) host 192.168.42.42 whatakey!@#$%^&*show tacacs-servertacacs-server (perimeter) host 192.168.42.42 whatakey!@#$%^&*aaa authentication any outside 192.168.42.42 255.255.255.255 0 0 tacacs+tcpchecksum
Test for a TCP checksum error. (Configuration mode.)
tcpchecksum [silent | verbose]
no tcpchecksum
show tcpchecksum
Syntax Description
silent
Disable TCP checksum error checking.
verbose
Display warning on PIX Firewall console if TCP checksum error occurs.
Usage Guidelines
Check for TCP segment integrity and report the error if found.
Example
tcpchecksum verboseshow tcpchecksumtcpchecksum verbosetelnet
Specify internal host for PIX Firewall console access via Telnet. (Privileged mode.)
telnet local_ip [netmask]
clear telnet [local_ip [netmask]]
no telnet [local_ip [netmask]]
show telnet
telnet timeout minutes
show telnet timeout
Syntax Description
Usage Guidelines
The telnet command lets you decide which host can access the PIX Firewall console with Telnet. Up to 16 hosts or networks are allowed access to the PIX Firewall console with Telnet, 5 simultaneously. The show telnet command displays the current list of IP addresses authorized to access the PIX Firewall. Use no telnet or clear telnet to remove Telnet access from a previously set IP address. Use the telnet timeout feature to set the maximum time a console Telnet session can be idle before being logged off by PIX Firewall. The clear telnet command does not affect the telnet timeout duration. The no telnet command cannot be used with the telnet timeout feature.
Use the passwd command to set a password for Telnet access to the console. The default is cisco. Use the who command to view which IP addresses are currently accessing the firewall console. Use the kill command to terminate an active Telnet console session.
If the aaa command is used with the console option, Telnet console access must be authenticated with an authentication server. Authentication of the serial console creates a potential dead-lock situation if the authentication server requests are not answered and you need access to the console to attempt diagnosis.
Note
If you have configured the aaa command to require authentication for PIX Firewall Telnet console access and the console login request times out, you can gain access to the PIX Firewall from the serial console by entering the pix username and the password that was set with the enable password command.
Usage Notes
1
To access the PIX Firewall with Telnet, specify the IP address of the inside interface. For example, if the inside interface is 192.168.1.1, use the following command:
telnet 192.168.1.12
The default password to access the PIX Firewall console via Telnet is cisco.
3
Some Telnet applications such as the Windows 95 or Windows NT Telnet sessions may not support access to the PIX Firewall's command history feature via the arrow keys. However, you can access the last entered command by pressing Ctrl-P.
4
The telnet timeout command affects the next session started but not the current session.
5
If you connect a computer directly to the inside interface of the PIX Firewall with Ethernet to test Telnet access, you must use a cross-over cable and the computer must have an IP address on the same subnet as the inside interface. The computer must also have its default route set to be the inside interface of the PIX Firewall.
6
Telnet access to the console must be configured before you use PIX Firewall Manager.
7
With Telnet, you can configure the PIX Firewall only from the inside network or over Private Link.
8
If you need to access the PIX Firewall console from outside the PIX Firewall, you can use a static and conduit command pair to permit a Telnet session to a Telnet server on the inside interface, and then from the server to the PIX Firewall. In addition, you can attach the console port to a modem (using the same terminal settings as you would for HyperTerminal—described in Chapter 2, ""), but this may add a security problem of its own.
See also: aaa, kill, passwd, who.
Examples
The following examples permit hosts 192.168.1.3 and 192.168.1.4 to access the PIX Firewall console via Telnet. In addition, all the hosts on the 192.168.2.0 network are given access.
telnet 192.168.1.3 255.255.255.255telnet 192.168.1.4 255.255.255.255telnet 192.168.2.0 255.255.255.0show telnet192.168.1.3 255.255.255.255192.168.1.4 255.255.255.255192.168.2.0 255.255.255.0You can remove individual entries with the no telnet command or all telnet statements with the clear telnet command:
no telnet 192.168.1.3show telnet192.168.1.4 255.255.255.255192.168.2.0 255.255.255.0clear telnetshow telnetYou can change the maximum session idle duration as follows:
telnet timeout 10show telnet timeouttelnet timeout 10 minutesAn example Telnet console login session appears as follows (the password does not display when entered):
PIX passwd: ciscoWelcome to the PIX firewallCopyright (c) 1995-1999 by Cisco Systems, Inc.Restricted Rights LegendUse, duplication, or disclosure by the Government issubject to restrictions as set forth in subparagraph(c) of the Commercial Computer Software - RestrictedRights clause at FAR sec. 52.227-19 and subparagraph(c) (1) (ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS sec. 252.227-7013.Cisco Systems, Inc.170 West Tasman DriveSan Jose, California 95134-1706Type help or `?' for a list of available commands.pixfirewall>terminal
Change console terminal state. (Configuration mode.)
terminal [no] monitor
Syntax Description
Usage Guidelines
The terminal monitor command lets you enable or disable the display of syslog messages in the current session for either Telnet or serial access to the PIX Firewall console. Use the logging monitor command to enable or disable various levels of syslog messages to the console; use the terminal no monitor command to disable the messages on a per session basis. Use terminal monitor to restart the syslog messages for the current session.
Example
logging monitor...terminal no monitortftp-server
Specify the IP address of the TFTP configuration server. (Configuration mode.)
tftp-server local_ip path
no tftp-server [local_ip path]
show tftp-server
Syntax Description
Usage Guidelines
The tftp-server command lets you specify the IP address of a server that you use to propagate PIX Firewall configuration files to your firewalls. Use tftp-server with the configure net command to read from the configuration or with the write net command to store the configuration in the file you specify.
The contents of the path name you specify in tftp-server are appended to the end of the IP address you specify in the configure net and write net commands. The more of a file and path name specification you provide with the tftp-server command, the less you need to do with the configure net and write net commands. If you specify the full path and filename in tftp-server, the IP address in configure net and write net can be represented with a colon ( : ).
The no tftp server command disables access to the server. The show tftp-server command lists the tftp-server statements in the current configuration.
Example
The following example specifies a TFTP server and then reads the configuration from /pixfirewall/config/test_config:
tftp-server 10.1.1.42 /pixfirewall/config/test_config...configure net :timeout
Set the maximum idle time duration. (Configuration mode.)
timeout [xlate [hh:mm:ss]] [conn [hh:mm:ss]] [udp [hh:mm:ss]] [rpc [hh:mm:ss]]
[h323 [hh:mm:ss]] [uauth [hh:mm:ss] [absolute | inactivity]]show timeout
Syntax Description

