Comments
-
WatchGuard will close this thread as answered. If there are any new comments please post a new thread in the WiFi sections. Mark Boscolo WatchGuard Moderator.
-
Perry, the outlined procedure is to create a new configuration file, regardless from when it was created. We strongly recommend that you follow the information in this link - https://techsearch.watchguard.com/KB?type=Article&SFDCID=kA16S000000SO3iSAG&lang=en_US Mark Boscolo WatchGuard Moderator
-
Hello Markus, Fireboxes process SSLVPN connections using only CPUs, the encryption chips are not used to process SSLVPN encryptions. To ensure the best performance we recommend using an AES encryption - Encryption Select an algorithm to encrypt the traffic: 3DES, AES (128-bit), AES (192-bit), or AES (256-bit). In Fireware…
-
Thanks, The developers are currently checking into this, thanks for responding and confirming. Mark
-
Can you confirm if the issue which you are encountering is outlined in this Knowledge Base article. https://techsearch.watchguard.com/KB/WGKnowledgeBase?lang=en_US&SFDCID=kA10H000000g6BaSAI&type=Article
-
WatchGuard has posted to the General downloads pages both v12.6.2 U3 and v12.5.5 U1, which resolves the software problems introduced in the original release. We recommend reviewing the release notes for a list of all issues which have been fixed in this release. Mark Boscolo WatchGuard Representative
-
WatchGuard has posted to the General downloads pages both v12.6.2 U3 and v12.5.5 U1, which resolves the software problems introduced in the original release. We recommend reviewing the release notes for a list of all issues which have been fixed in this release. Mark Boscolo WatchGuard Representative
-
WatchGuard has posted to the General downloads pages both v12.6.2 U3 and v12.5.5 U1, which resolves the software problems introduced in the original release. We recommend reviewing the release notes for a list of all issues which have been fixed in this release. Mark Boscolo WatchGuard Representative
-
WatchGuard has posted to the General downloads pages both v12.6.2 U3 and v12.5.5 U1, which resolves the software problems introduced in the original release. We recommend reviewing the release notes for a list of all issues which have been fixed in this release. Mark Boscolo WatchGuard Representative
-
Can you check if the DHCPD process is reporting a Fault. We are in the process of creating a Known Issue for v12.5.4 DHCPrelay crash.
-
It is not at all related to Authpoint. This is a Firewall problem which communications with Radius would trigger a deadlock on the processes. Which is why the release note was drafted naming Radius and Firebox. Mark Boscolo
-
The root cause is with internal processes deadlocking while exchanging data. Does this help? Mark Boscolo
-
Hello Abertay, Can you open a Support case for the DNSWatchGo slow issue so that we can review and help identify the issue. Mark Boscolo
-
You can set these options: Per Server Quota The Per Server Quota applies a limit to the number of connections per second from any external source to the Firebox external interface. This includes connections to internal servers allowed by a static NAT policy. The Per Server Quota is based on the number of connection…
-
WathcGuard is working on an official response to this vulnerability. Once the write up is available a link will be provided.
-
Thanks for the suggestion Bruce. I have submitted the suggested navigation improvements to our Web Development Team.
-
Do you have details on the specific issues you have encountered? Also have you reported them in any support cases Best regards, Mark Boscolo
-
WatchGuard is working on getting this issue fixed both on the Appliance and DNSWatch cloud server side. Tracking ID FBX-17207
-
DNSWatchGO is intended to be independent product, not tied to any Firewall licensing.
-
There is an open NAT issue that is defined in the following Knowledge Base Article ID - Article ID: 000011920 https://watchguardsupport.secure.force.com/publicKB?type=KBKnownIssues&SFDCID=kA40H000000J55RSAS&lang=en_US
-
The properties is one which the Firewall is not aware of. However the TCP flag should be passed and not dropped. If you are encountering problems with packets dropping, I would recommend opening a Support case to further investigate the the traffic in the TCP headers. Mark Boscolo
-
Firebox uses TCP port 4115 for TDR communications with Cloud. This is the traffic observed in that case.
-
Bruce is TDR configured on your appliance?
-
A link in "Before you Begin" has a link to the article "Release_specific upgrade notes". In the v12.4 release notes
-
With the introduction of SDWAN it is necessary to define rule that have Policy Based Routing and SNAT to be unique. It is no longer possible to have a single rule that controls the traffic with 2 different actions. There is a knowledge base article that has an explanation for the change Article ID: 000011870
-
If you are using both FQDN and IP address in Dimension this issue will occur. To fix the problem you need to list only 1 in the Server Management Section. If you can login to your Support account you can search for the following Knowledge Base article - Article ID: 000011683