Ruckus AP not stable when running on WPA2/WPA3-Mixed SAE Passphrase mode

Workaround:

Failback to WP2-PSK

Ruckus AP not stable when running on WPA2/WPA3-Mixed SAE Passphrase mode

Upgrade a old DIR-850L which is running on 1.13 (Hardware version A1) to the latest version firmware 1.20

1. Upgrade to 1.14b07b01 (files.dlink.com.au - /products/DIR-850L/REV_A/Firmware/)
2. Upgrade to 1.15b04 (http://files.dlink.com.au/products/DIR-850L/REV_A/Firmware/Firmware_v1.20b03/DIR850LA1_FW115WWb04.bin)
3. Upgrade to 1.20b03 (files.dlink.com.au - /products/DIR-850L/REV_A/Firmware/)

DIR-850L Firmware Release Notes
=================================

**Note: a factory reset is recommended after upgrading to ensure correct configuration is applied**


Hardware: A1
Firmware: V1.20
Date: 20/09/2017


NOTE:
THE FIRMWARE V1.15WWB04 NEEDS TO BE UPLOADED FIRST AS A TRANSITIONAL FIRMWARE V1.15, BEFORE UPGRADING TO V1.20WWB03.
Upgrade to Firmware V1.15 and then instantly go back into the web user interface and upgrade to Firmware V1.20

Problems Resolved:
1. Fixed the following security issues
- Firmware Protection
- WAN & LAN XSS exploit
- WAN - weak cloud control
- WAN & LAN - Stunnel Private Keys
- WAN & LAN - Nonce brute force for DNS configuration
- Local - WEak file permission and credentials stored in clear text
- Local - DoS attack against some daemons

Source: D-Link Support Resources

Upgrade a old DIR-850L which is running on 1.13 (Hardware version A1) to the latest version firmware 1.20

Cisco ASA and FirePower 1000 and 1200 max VPN peers

Cisco ASA and FirePower 1000 and 1200 max VPN peers

Veeam just release a new version of Linux agent which can support Rocky linux 8.10

https://helpcenter.veeam.com/docs/agentforlinux/userguide/system_requirements_nosnap.html?ver=60

Veeam just release a new version of Linux agent which can support Rocky linux 8.10

Windows 11 hardening by hotcakex.github.io

https://github.com/HotCakeX/Harden-Windows-Security

Windows 11 hardening by hotcakex.github.io

Receive OpenSSL error from one IP and another one IP is normal

SSL_ERROR_SYSCALL

One destination IP address able to connect another cannot. 

Solution: Add the URL to URL whitelist on Cloud Fortinet Fortigate Firewall

Receive OpenSSL error from one IP and another one IP is normal

Identifying and preventing unwanted DNS queries from FortiGate's FQDN Address ObjectYES

FQDN on firewall rule to AWS service, sometime need to fine tune the DNS TTL

Reference:

Identifying and preventing unwanted DNS q... - Fortinet Community

Explanation of the FQDN default cache-ttl... - Fortinet Community

How to deal with FQDN with short DNS TTL - Fortinet Community

How To Change Session TTL For A Firewall Policy In FortiGate (hex64.net)

Identifying and preventing unwanted DNS queries from FortiGate's FQDN Address ObjectYES