Best Of
Feature Request: Update SNMPv3 Encryption Algorithms (SHA256, AES128, AES256, etc.)
Dear Watchguard Support Team,
I would like to kindly request the opening of a feature request to update the encryption algorithms available for SNMPv3 on Watchguard devices, specifically to include modern standards such as SHA256, AES128, AES256, and similar options.
Background:
Currently, on a FireboxV running version 12.11.1 (Build B711554), the available options for SNMPv3 encryption are limited to the following:
Authentication Protocol:
- None
- MD5
- SHA
Encryption Protocol:
- None
- DES
These protocols no longer align with current security standards and are widely considered insecure. Additionally, the upcoming Zabbix cluster, based on AlmaLinux 9, no longer supports the DES protocol at all. According to the Red Hat Enterprise Linux 9 documentation (see: https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/considerations_in_adopting_rhel_9/assembly_shells-and-command-line-tools_considerations-in-adopting-rhel-9#ref_changes-to-system-management_assembly_shells-and-command-line-tools), the DES algorithm has been removed from net-snmp communication in RHEL 9 due to its insecurity and lack of support in the OpenSSL library.
Impact:
Without updated encryption options, encrypted SNMPv3 monitoring will not be possible with the new Zabbix system unless the firewall is monitored via a proxy running AlmaLinux 8. This limitation could significantly affect secure network management moving forward.
Request:
Please consider adding support for modern encryption algorithms (e.g., SHA256, AES128, AES256) to SNMPv3 in future Watchguard firmware updates to ensure compatibility with current and future systems and to meet modern security standards.
Thank you for your attention to this matter. Please let me know if you need any further details to process this request.
Best regards,
Fabian Öttl
Re: Mobile VPN ipsec on fireware 12.1.3 Firebox T30-W connection OK, but no network access.
Check your AD connection from the firewall.
Seems like it is being denied
Re: Traffic monitor, history
You can setup a watchguard dimension or you enable your watchguard to cloud reporting.
And thean you can search für logs from history and offer interesting Information.
The easiest way is you setup your watchguard too cloud reporting.
https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/WG-Cloud/Devices/device_add_locally_managed.html
https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/logging/set_up_logging_on_device_wsm.html?Highlight=Logging
https://www.watchguard.com/help/docs/help-center/en-US/content/en-us/Fireware/dimension/get-started_dimension_d.html
Re: Traffic Management Limitations
@JohnS I've seen customers with well over 500 rules on small devices. There is a ceiling to how many policies you can have, but it has to do with the amount of memory available on the device, not the number of policies.
For example, if you load each policy with a server load balancing policy that sources from an extensive list of FQDNs, you'd probably max out at around 50.
(When customers find that limit, they're almost always asking more of their firewall than it's capable of, and it's almost always on the smallest devices we sell. The M4800 should reasonably be capable of handling thousands of complex policies if needed.)
Re: Traffic Management Limitations
Not a problem for you.
I have over 100 policies on a T20.
Re: Allocate AP to different subscriber
I "think" the AP retains whatever config it was running, in that reallocation does not reset it, but your control/visibility over that configuration is lost until you Add AP steps which is starting the config. With regards to AP sites you might then have to Add AP and then Add to Site option in the early stage of settings it back up

Re: Traffic Management Limitations
Hi @JohnS
For traffic management policies per-ip you are correct. There is a limit per-policy.
There's a few ways around this:
-Making rules by subnet (works best with /23s and /24s because of the per IP limitation)
-Using user groups instead of IPs to implement the policy.
See: https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/authentication/sso_quick_start.html
Re: Deploy VPN client with intune: installation failed when wgsslvpnsrc.exe is running
This method would kill a VPN in use. Users may not like that. Instead, for an Intune install, I use the requirements section to run a PowerShell and only succeed if the process is not running. It will then update when the user is back in the office and not using the VPN, so no interruptions and happy users.
Re: Mobile VPN with SSL certificates expired
@Bruce_Briggs said:
Delete the old expired cert & reboot your firewall.
A new one should be generated.
Thank you very much: it works fine after the delete & reboot as you suggested me.
Thanks again!
Ciao
Re: Video freezes in Teams and Google Meets
Hi @D4rkSeven
It looks like a TCP/UDP proxy is unable to write that specific traffic to the proxy. Considering the source port is 59418 and the destination port is 3478, a TCP-UDP proxy is likely the type of policy this traffic is being sent via.
Is there a reason you are proxying this traffic? Does this traffic work if you create a packet filter to allow it?
I'd suggest opening a support case so that our team can get more details and help find a solution.