ZyXEL Communications ZYWALL 70 - V4.03 Informacje Techniczne Pobierz pdf (Strona 24)

17. [BUG FIX] SPR ID: 070411473, 070411474, 070411475, 070411476 ITS #: 16872

Symptom: VPN traffic stops between two gateways.

Condition:

Topology:

(192.168.100.0/24)

PC1--(LAN) ZyWALL 5-----+ +--- ZyWALL 70(LAN)----PC2

| |

----+--+--+----

ZyWALL 35

(DMZ)| |(LAN)

(Safenet) | |

PC3-------------+ +---------------PC4

(10.10.10.0/24) (192.168.10.0/24)

(1) Reset ZyWALL5/35/70 ROM file.

(2) Configure the DMZ IP(10.10.10.1/24) and LAN(192.168.10.0/24) for ZyWALL35,

LAN IP 192.168.100.0/24 as ZyWALL70’s LAN.

(3) Build the Gateway-to-Gateway VPN between ZyWALL35 and ZyWALL70 with the

both LAN IP, then PC2 ping PC4, at this moment, it should be okay.

(4) Configure the Dynamic VPN rule in the ZyWALL5 with the Local IP as PC1.

(5) Build the VPN tunnel from PC3 (Safenet) to the ZyWALL5,after the tunnel build

successfully, remove the PC1, then using the PC3 ping the PC1's IP.

(6) Then, you will find PC2 can＊t ping PC4.

18. [BUG FIX] ITS #: 17937

Symptom: ZyWALL CPU usage goes up to 100% with AS enable.

Condition:

Topology:

Mail server(A)-----(LAN)ZyWALL35(WAN)----Internet----Mail Relay(B)

(1) Enable AS and select the WAN1->LAN.

(2) Send mail from Mail Relay(B) to Mail Server(A). Mail server(A) is a sendmail on

linux.

(3) The usage of CPU will go up to >95% if the mail traffic includes PWAS option.

19. [ENHANCEMENT] SPR ID: 070614815, 070614816, 070614817, 070614818

Modified DDNS Log is not readable.

(1) View DDNS Log in LOGS>>View Log.

(2) DDNS Log is not readable, for example:

2007-05-07 17:44:52 DDNS update IP:138.188.40.255 (host 1) successfully

Was: DNS update IP:138.188.40.255 (host 1) successfully

Is: Update domain name zywall2wg.dyndns.org with IP:138.188.40.255

successfully|DDNS

1 2 ... 19 20 21 22 23 24 25 26 27 28 29 ... 81 82

Brak uwag

ZyXEL Communications ZYWALL 70 - V4.03 Informacje Techniczne Strona 24