|
|
|
|
| ZyWALL 2 and ZyWALL 2WE | ||
|
|
|
|
|
|
|
|
|
| Index: |
| Date/Time: | Log: |
|
|
|
|
|
| ||||
|
|
|
| ||||
|
| 001 | 01 | Jan 08:02:22 | Send Main Mode request to <192.168.100.101> |
|
|
|
| 002 | 01 | Jan 08:02:22 | Send:<SA> |
|
|
|
| 003 | 01 | Jan 08:02:22 | Recv:<SA> |
|
|
|
| 004 | 01 | Jan 08:02:24 | Send:<KE><NONCE> |
|
|
|
| 005 | 01 | Jan 08:02:24 | Recv:<KE><NONCE> |
|
|
|
| 006 | 01 | Jan 08:02:26 | Send:<ID><HASH> |
|
|
|
| 007 | 01 | Jan 08:02:26 | Recv:<ID><HASH> |
|
|
|
| 008 | 01 | Jan 08:02:26 | Phase 1 IKE SA process done |
|
|
|
| 009 | 01 | Jan 08:02:26 | Start Phase 2: Quick Mode |
|
|
|
| 010 | 01 | Jan 08:02:26 | Send:<HASH><SA><NONCE><ID><ID> |
|
|
|
| 011 | 01 | Jan 08:02:26 | Recv:<HASH><SA><NONCE><ID><ID> |
|
|
|
| 012 | 01 | Jan 08:02:26 | Send:<HASH> |
|
|
|
| Clear IPSec Log (y/n): |
|
|
| ||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
VPN Responder IPSec Log
The following figure shows a typical log from the VPN connection peer.
Index: |
| Date/Time: | Log: |
001 | 01 | Jan 08:08:07 | Recv Main Mode request from <192.168.100.100> |
002 | 01 | Jan 08:08:07 | Recv:<SA> |
003 | 01 | Jan 08:08:08 | Send:<SA> |
004 | 01 | Jan 08:08:08 | Recv:<KE><NONCE> |
005 | 01 | Jan 08:08:10 | Send:<KE><NONCE> |
006 | 01 | Jan 08:08:10 | Recv:<ID><HASH> |
007 | 01 | Jan 08:08:10 | Send:<ID><HASH> |
008 | 01 | Jan 08:08:10 | Phase 1 IKE SA process done |
009 | 01 | Jan 08:08:10 | Recv:<HASH><SA><NONCE><ID><ID> |
010 | 01 | Jan 08:08:10 | Start Phase 2: Quick Mode |
011 | 01 | Jan 08:08:10 | Send:<HASH><SA><NONCE><ID><ID> |
012 | 01 | Jan 08:08:10 | Recv:<HASH> |
Clear IPSec Log (y/n):
DiagramThis menu is useful for troubleshooting. A log index number, the date and time the log was created and a log message are displayed.
Double exclamation marks (!!) denote an error or warning message.The following table shows sample log messages during IKE key exchange.
Log Descriptions | 81 |