ZyXEL Communications ZYWALL 70 - V4.03 Información técnica descargar pdf (Pagina 10)

Symptom: ZyWALL doesn't forward "no such name" response to DNS client.

Condition:

(1) Configure ZyWALL as DNS server on PC.

(2) PC resolves a nonexistent domain name, and it will wait response until timeout.

13. [BUG FIX] SPR ID: 071109671

Symptom: ZyWALL can not record system report based on IP address which is not in

the same subnet of ZyWALL itself.

Topology:

(bridge mode)

PC-----(LAN)ZyWALL5(WAN)----ZyWALL70----Internet

PC:10.0.0.34

ZyWALL5:192.168.10.40

ZyWALL70(LAN):10.0.0.1, ip alias:192.168.10.1

Condition:

(1) Enable Collect Statistics of ZyWALL5 under system reports.

(2) PC visits a web page on the internet.

(3) We can not see the statistics of host IP reports in ZyWALL5.

14. [BUG FIX] SPR ID: 070411476

Symptom: VPN traffic stops between two gateways.

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)

Condition:

(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.

1 2 ... 5 6 7 8 9 10 11 12 13 14 15 ... 81 82

Sin comentarios

ZyXEL Communications ZYWALL 70 - V4.03 Información técnica Pagina 10