{"id":8251,"date":"2019-08-14T14:01:44","date_gmt":"2019-08-14T12:01:44","guid":{"rendered":"https:\/\/www.boc.de\/watchguard-info-portal\/?p=8251"},"modified":"2025-10-21T13:56:50","modified_gmt":"2025-10-21T11:56:50","slug":"fireware-12-5-update-1-jetzt-verfuegbar","status":"publish","type":"post","link":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/2019\/08\/fireware-12-5-update-1-jetzt-verfuegbar\/","title":{"rendered":"Fireware 12.5 Update 1 jetzt verf\u00fcgbar"},"content":{"rendered":"<p>Seit dem 12.08.2019 verf\u00fcgbar:<\/p>\n<ul>\n<li><a href=\"https:\/\/software.watchguard.com\/\" target=\"_blank\" rel=\"noopener\">WatchGuard Fireware 12.5 Update 1<\/a><\/li>\n<\/ul>\n<p>Dieses Update behebt einige Probleme, die seit dem Fireware 12.5 Release Mitte Juli aufgetreten sind. \u00dcberwiegend\u00a0im Zusammenhang mit DNSWatch und Cluster-Failover in Verbindung mit PPPoE.<\/p>\n<p><!--more--><\/p>\n<p>Weitere Informationen finden Sie\u00a0in den <a href=\"https:\/\/www.watchguard.com\/support\/release-notes\/fireware\/12\/en-US\/EN_ReleaseNotes_Fireware_12_5\/index.html\" target=\"_blank\" rel=\"noopener\">Release Notes<\/a>.<br \/>\nAlles rund um die neue Fireware finden Sie unter <a href=\"https:\/\/www.boc.de\/watchguard-info-portal\/2019\/07\/whats-new-in-fireware-12-5\/\" target=\"_blank\" rel=\"noopener\">What&#8217;s New in Fireware v12.5<\/a>.<\/p>\n<p>Originaltext:<\/p>\n<ul>\n<li value=\"1\"><em>The Firebox T30, T35, T50, M200, and M300 can now successfully receive traffic from a device with a MAC address that ends in\u00a0<span class=\"Input\">:88:08<\/span>.\u00a0<span class=\"NumContinued\">[FBX-16948]<\/span><\/em><\/li>\n<li value=\"2\"><em>This release resolves an issue that causes the RADIUS NAS-IP addressed to appear in reverse order in Access-Request packets.\u00a0<span class=\"NumContinued\">[FBX-16368]<\/span><\/em><\/li>\n<li value=\"3\"><em>This release resolves a DNSWatch issue on the Firebox and corrects an error on external interfaces when retrieving data.\u00a0<span class=\"NumContinued\">[FBX-15477]<\/span><\/em><\/li>\n<li value=\"4\"><em>The\u00a0<span class=\"Input\">iked<\/span>\u00a0process no longer crashes when your Firebox has a short RSA certificate.\u00a0<span class=\"NumContinued\">[FBX-16606]<\/span><\/em><\/li>\n<li value=\"5\"><em>This release resolves a memory leak in the\u00a0<span class=\"Input\">admd<\/span>\u00a0process.\u00a0<span class=\"NumContinued\">[FBX-16915, FBX-16983]<\/span><\/em><\/li>\n<li value=\"6\"><em>This release resolves an issue which caused a FireboxV to become unregistered in WatchGuard Cloud if it uses a local DNS\u00a0server and the external interface is down for more than 4 minutes.\u00a0<span class=\"NumContinued\">[FBX-16888]<\/span><\/em><\/li>\n<li value=\"7\"><em>This release resolves an issue that causes the default route to disappear after a FireCluster failover.\u00a0<span class=\"NumContinued\">[FBX-16604, FBX-16799]<\/span><\/em><\/li>\n<li value=\"8\"><em>A proxy process crash no longer occurs when traffic connects through a SIP-ALG proxy policy.\u00a0<span class=\"NumContinued\">[FBX-16581, FBX-16778]<\/span><\/em><\/li>\n<li value=\"9\"><em>This release resolves an issue that causes some websites to fail to load with a browser message<span class=\"Input\">\u00a0ERR_CONTENT_LENGTH_MISMATCH<\/span>.\u00a0<span class=\"NumContinued\">[FBX-16354]<\/span><\/em><\/li>\n<li value=\"10\"><em>This release resolves an issue that causes the Firebox to stop sending updates to DNSWatch Cloud after an upgrade to Fireware 12.5.\u00a0<span class=\"NumContinued\">[FBX-17207]<\/span><\/em><\/li>\n<li value=\"11\"><em>This release resolves a Web UI syntax error that occurs when you configure DNS servers through Dimension Command.\u00a0<span class=\"NumContinued\">FBX-16608<\/span><\/em><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Seit dem 12.08.2019 verf\u00fcgbar: WatchGuard Fireware 12.5 Update 1 Dieses Update behebt einige Probleme, die seit dem Fireware 12.5 Release Mitte Juli aufgetreten sind. \u00dcberwiegend\u00a0im Zusammenhang mit DNSWatch und Cluster-Failover in Verbindung mit PPPoE.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[122],"tags":[564,548,137],"class_list":["post-8251","post","type-post","status-publish","format-standard","hentry","category-watchguard-software-release-news","tag-fireware-12-5","tag-fireware-release","tag-update"],"_links":{"self":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts\/8251"}],"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\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/comments?post=8251"}],"version-history":[{"count":2,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts\/8251\/revisions"}],"predecessor-version":[{"id":29495,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts\/8251\/revisions\/29495"}],"wp:attachment":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/media?parent=8251"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/categories?post=8251"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/tags?post=8251"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}