Best Of
Re: AuthPoint MFA for Watchguard System manager and Policy Manager
Just to add - this is 100% coming. My insurance company is now forcing MFA for all network equipment on the network (inc network switch which have a GUI - you must enable MFA or remove from the network) I used to be able to place these appliances in a "admin" VLAN but from next year, this will no longer be an option to have cyber / business insurance coverage. Rules state that all equipment must have MFA / 2FA which access is via a GUI / management program.
Re: multiple ssl vpn on a single machine
@Francesco
This likely will not work. Even if you use another OpenVPN client, the OpenVPN TAP may still conflict.
Consider setting up tunnel switching so that you can access both networks from one firewall's SSLVPN:
(Branch Office VPN Tunnel Switching)
https://www.watchguard.com/help/docs/help-center/en-us/Content/en-US/Fireware/bovpn/manual/manual_bovpn_tunnel_switching_summary_wsm.html
Re: IKE VPN with AuthPoint RADIUS in remote office.
BOVPN Vif / VPN Routes / Assign virtual interface IP addresses config.
Firebox is now using this address when it is connecting to the remote radius server through the VPN tunnel. Configure also this virtual IP as the radius client in the NPS server.
Without this virtual IP config the firebox is using its external IP as the source IP when trying to connect to the radius server...
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
