Figure 240 Routing Command Example; Log Command Example - ZyXEL Communications P-660HW-Tx v3 User Manual

Log Command Example

This example shows how to set the ZyXEL Device to record the access logs and alerts and
then view the results.
ras> sys logs load
ras> sys logs category access 3
ras> sys logs save
ras> sys logs display access
# .time
message
0|06/08/2004 05:58:21 |172.21.4.154
BLOCK
Firewall default policy: IGMP (W to W/ZW)
1|06/08/2004 05:58:20 |172.21.3.56
BLOCK
Firewall default policy: IGMP (W to W/ZW)
2|06/08/2004 05:58:20 |172.21.0.2
BLOCK
Firewall default policy: IGMP (W to W/ZW)
3|06/08/2004 05:58:20 |172.21.3.191
BLOCK
Firewall default policy: IGMP (W to W/ZW)
4|06/08/2004 05:58:20 |172.21.0.254
BLOCK
Firewall default policy: IGMP (W to W/ZW)
5|06/08/2004 05:58:20 |172.21.4.187:137
BLOCK
Firewall default policy: UDP (W to W/ZW)
Routing Command
Syntax:
ip nat routing [0:LAN] [0:no|1:yes]
Use this command to set the ZyXEL Device to route traffic that does not match a NAT rule
through a specific interface. An example of when you may want to use this is if you have
servers with public IP addresses connected to the LAN.
The following command example sets the ZyXEL Device to route traffic that does not match a
NAT rule through the LAN interface.

Figure 240 Routing Command Example

ras> ip nat routing 2 0
Routing can work in NAT when no NAT rule match.
-----------------------------------------------
LAN: yes
P-660HW-Tx v3 User's Guide
source
Appendix E Command Interpreter
destination
|224.0.1.24
|239.255.255.250
|239.255.255.254
|224.0.1.22
|224.0.0.1
|172.21.255.255:137
notes
|ACCESS
|ACCESS
|ACCESS
|ACCESS
|ACCESS
|ACCESS
351