{"id":2220,"date":"2009-05-06T12:27:00","date_gmt":"2009-05-06T10:27:00","guid":{"rendered":"https:\/\/www.boc.de\/watchguard-info-portal\/webblocker-active-inactive\/"},"modified":"2016-08-23T15:50:29","modified_gmt":"2016-08-23T13:50:29","slug":"webblocker-active-inactive","status":"publish","type":"post","link":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/2009\/05\/webblocker-active-inactive\/","title":{"rendered":"WebBlocker active \/ inactive"},"content":{"rendered":"<p>Bisweilen findet man im Traffic Monitor Eintr\u00e4ge wie:<\/p>\n<p>proxy[1756] webblocker server=IP:5003\/udp is now active<br \/>proxy[1756] webblocker server=IP:5003\/udp is now inactive<br \/>proxy[1756] webblocker server=IP:5003\/udp is now active<br \/>proxy[1756] webblocker server=IP:5003\/udp is now inactive<\/p>\n<p>Diese Meldungen haben nur informellen Charakter, man kann sie getrost ignorieren. Das Verhalten ist durchaus normal und tritt dadurch auf, dass der WebBlocker-Dienst eine gewisse Zeit lang nichts zu tun hat, wodurch die udp-Verbindung zwischen der Firebox und dem WebBlocker Server in einen idle-Timeout l\u00e4uft, getrennt wird und dadurch die Meldung &#8220;inactive&#8221; ausl\u00f6st. Wenn der WebBlocker dann das n\u00e4chste Mal wieder angesprochen wird, springt der Status wieder auf &#8220;active&#8221;. In den allermeisten F\u00e4llen liegt somit kein akutes Problem vor.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Bisweilen findet man im Traffic Monitor Eintr\u00e4ge wie: proxy[1756] webblocker server=IP:5003\/udp is now activeproxy[1756] webblocker server=IP:5003\/udp is now inactiveproxy[1756] webblocker server=IP:5003\/udp is now activeproxy[1756] webblocker server=IP:5003\/udp is now inactive Diese Meldungen haben nur informellen Charakter, man kann sie getrost ignorieren. Das Verhalten ist durchaus normal und tritt dadurch auf, dass der WebBlocker-Dienst eine gewisse Zeit lang nichts zu tun hat, wodurch die udp-Verbindung zwischen der &hellip; <a href=\"https:\/\/wordpress.boc.de\/watchguard-info-portal\/2009\/05\/webblocker-active-inactive\/\" class=\"more-link\">Weiterlesen <span class=\"screen-reader-text\">WebBlocker active \/ inactive<\/span> <span class=\"meta-nav\">&raquo;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[336,81,323,107],"class_list":["post-2220","post","type-post","status-publish","format-standard","hentry","category-watchguard-technischer-blog","tag-application-proxy","tag-traffic-monitor","tag-utm-services","tag-webblocker"],"_links":{"self":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts\/2220"}],"collection":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/comments?post=2220"}],"version-history":[{"count":1,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts\/2220\/revisions"}],"predecessor-version":[{"id":2390,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts\/2220\/revisions\/2390"}],"wp:attachment":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/media?parent=2220"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/categories?post=2220"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/tags?post=2220"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}