ZyXEL Communications ZYWALL 35 - V4.03 Informacje Techniczne Strona 6

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 84
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 5
(2) In eWC->SECURITY->CONTENT FILTER->Customization page, enable
"Web site customization" and "Don't block Java/ActiveX/Cookies/Web
proxy to trusted Web sites". Add "web.haccpsoft.it" to "Trusted Web
Sites".
(3) A PC in ZYWALL's LAN side browses "http://web.haccpsoft.it:8080"
website.
(4) Login in and click the date, the popup window should show a calendar
instead of another login page.
(5) It is blocked by content filter.
5. There is a forward log of the blocked web site.
Condition:
(1) Register Content Filter service.
(2) Enable Content Filter and Enable External Database Content Filtering.
Block “Email” category.
(3) Log “Forward Web Sites”, “Blocked Web Sites”, “Blocked Java etc.” in
“Log Settings”.
(4) Visit http://www.email.com
which is in Email category in LAN PC, the web
site will be blocked and there is a blocked log of it. But there is another
forward log of this blocked web site too.
(5) This problem is existed in 4.01 Patch 2 C0 too.
6. http://info.zyxel.com.tw
was recognised as “google”.
Condition:
(1) Input “google” in Keyword Blocking of Customization.
(2) Visit http://info.zyxel.com.tw in LAN PC. The web site is opened
successfully. But there is a Keyword Blocking log say “info.zyxel.com.tw:
Keyword blocking” (see attached file).
(3) Visit other web site is normal.
(4) This problem is also existed in 4.01 Patch 2 C0 too.
7. Keyword blocking has functioned even if “Web site customization” was disabled.
Condition:
(1) Enable Content Filter.
(2) Add google into Customization>>Keyword Blocking. Keep “Web site
customization” was disabled.
(3) PC in LAN visit www.google.com
will be blocked there are blocked log
(see attached picture).
(4) This problem does NOT exist in “Forbidden Web Site List”.
This problem is exited in 4.01 Patch 2 C0 too.
[Firewall]
1. Some limitations on Firewall CLI configuration, (1) User can not delete specific
address or custom port entry from a rule. (2) CLI doesn’t support Modify and Move
for rules implemented in eWC. (3) eWC can not display firewall rule field correctly if
rule is added by CI command and its type is port/address range.
2. Ping of Death Log has some fault when argument in CI “ip icmp death” bigger than
1500.
Conditions:
Przeglądanie stron 5
1 2 3 4 5 6 7 8 9 10 11 ... 83 84

Komentarze do niniejszej Instrukcji

Brak uwag