ZyXEL Communications ZYWALL 5 - V4.04 Betriebsanweisung Seite 147

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 181
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 146
ZyXEL Confidential
404XD3C0.docx
147/181
31. [BUG FIX]
Symptom: Save a legal VPN gateway policy but the ZyWALL shows an error
message.
Condition:
(1) GO to eWC>VPN>GATEWAY POLICY – EDIT
(2) Save a GATEWAY POLICY whose name = GW, My Address =
www.abc.com.tw, Remote Gateway Address = www.cde.com.tw and Pre-Shared
Key = 12345678
(3) GO to eWC>VPN>NETWORK POLICY - EDIT
(4) Save a NETWORK POLICY whose name = NW, Active = Yes, Starting IP
Address = 192.168.1.33, Starting IP Address = 192.168.2.33 and Pre-Shared Key
= 12345678
(5) Go back to eWC>VPN>Rules and edit rule "GW" and set its My Address as
0.0.0.0, then save
(6) The ZyWALL shows an error message "This IKE rule has static policy rules.", but
it should not.
32. [BUG FIX]
Symptom: There are no logs in eWC>Logs>Log Settings when SMTP authentication
fail .
Condition:
(1) Go to eWC>Logs>Log Settings. Configure a wrong Mail Server/Send Log
to/Send Alerts to/ User Name of SMTP Authentication/Password of SMTP
Authentication and save.
(2) Go to eWC>Logs>View Log. There are no logs about SMTP Auth failures/SMTP
failures.
(3) If the configuration is correct. There is also no log to tell users that the result is
successful.
33. [ENHANCEMENT] Add port information in centralized log message when a netbios
packet was blocked.
34. [ENHANCEMENT] After the device rebooting, the system will synchronize Time
server until any WAN is up or all WAN links are failed exceed 5 minutes. If NTP
server is on LAN/DMZ subnet, DUT still won’t sync when WAN interface is down.
35. [BUG FIX]
Symptom: VPN tunnel can be established but traffic cannot go through tunnel.
Condition: PC1 -- ZyWALL -- Any Router/Internet -- ZyWALL -- PC2
(1) Configure corresponding VPN setting in both ZyWALLs.
(2) Dial VPN tunnel
(3) After tunnel established, PC1 cannot ping PC2 vice versa.
36. [BUG FIX]
Symptom: The router cannot flush correctly in eWC->LOGS->Reports.
Condition:
(1) In Bridge Mode.
(2) In eWC->LOGS->Reports, enable “Collect Statistics”, interface = LAN, Report
type= "Host IP Address".
(3) When pressing "Flush" button, there is still one record existing "192.168.70.123
Outgoing 3913 bytes". "192.168.70.123" is router's IP address.
Seitenansicht 146
1 2 ... 142 143 144 145 146 147 148 149 150 151 152 ... 180 181

Kommentare zu diesen Handbüchern

Keine Kommentare