優比快 Ubiquiti UniFi Professionals (持續更新)

pctine wrote:
USW-Flex-Mini...(恕刪)

willyyen wrote:
但在開了幾十天後仍需要重新再開一次，所以才在思考USG(恕刪)

gfx wrote:
請問買2組或更多的Unifi...(恕刪)

gfx wrote:
請問買2組或更多的Unifi無線ap延伸目前家網的架設，
不使用Unifi路由功能可以組mesh嗎?...(恕刪)

gfx wrote:
請問買2組或更多的Unifi無線ap延伸目前家網的架設，
不使用Unifi路由功能可以組mesh嗎?...(恕刪)

• Adds firmware support for netconsole configuration provisioned by controller (using config under Settings, Site). Supported in controller versions >= 5.12.2. 

• If IDS/IPS signature update fails for any reason, an alert is sent to the controller including information about the problem. Other general improvements to signature update process.
• Limit permitted SSH MAC algorithms to OpenSSH’s most recent defaults, disabling some older options. This will break compatibility with some very outdated SSH clients, but such clients likely have bigger problems than limited supported MAC algorithms and should no longer be used in any case.
• Switch speed test to speed.ui.com
• Support latest hardware revision of USG3.
• Changed certificate generation parameters for USG's local web UI so it creates and maintains certificates in accordance with the new requirements in macOS Catalina and iOS 13. On the first bootup using this version, it will create a new certificate.

• Fix GeoIP signature updates. Updated URL used so they work in general, and fixed bugs in the script that would make updates fail in some edge cases.
• Fix crash in guest redirector service where a host header is missing in the request.
• Do not make unifi resolve to 127.0.0.1 when USG goes into self-run. Fixes problems where USG itself, and/or other UniFi devices behind USG, end up stuck in disconnected state in certain configurations.
• IDS/IPS signature updates triggered during bootup are delayed until Internet connectivity is established. This fixes cases where people were seeing signature updates during the post-upgrade reboot not working until the next scheduled update a few hours later.
• Change DDNS client configuration format to ensure credentials and hostname are used only with the associated provider. Previously where more than one provider was configured on a specific WAN, and one of those had a custom server defined, if a provider server returned an error code the client would retry using the other DDNS provider’s credentials and hostname. This is because of a quirk in ddclient which treats configuration options defined on their own line as global options for the interface rather than being specific to a particular hostname. 

gfx wrote:
請問買2組或更多的Unifi...(恕刪)