AmpliFi HD Firmware v3.6.0
-
AmpliFi firmware v3.6.0 for AmpliFi HD, Instant and Teleport hardware has been released.
Release notes:
- Fixed FragAttacks vulnerabilities
- Improved stability
- Enhanced auto channel selection
- Other minor improvements and fixes
We use a gradual rollout and it may take up to a week for the devices to receive this update.
-
@UI-AmpliFi People been asking for years now about Wifi Schedule Off/On.
And WPA3 ?
-
Hi@UI-AmpliFi,
I have been running for a couple of days now with the new fw. No issues at all.
What’s positive is that I got better speed to my home office, noticed speed increases on all my devices.
All the best,
Mike
-
I am not seeing this update, was it pulled? Enabling beta firmware updates only shows 3.6.0rc2 available.
-
@cmdshft Hello. This is a public firmware release. Please disable the checkbox that allows you to receive the latest Beta firmware.
-
@UI-AmpliFi The gradual rollout makes sense, but I wish I could get a push notification or email when it’s ready for my device. As it is I just have to check every day.
-
@UI-AmpliFi Ah, sorry. I made the mistake of thinking this was the Alien forum for some reason. Apologies!
-
Been running the new FW update since it was released. My setup is 4x RAMPs connected via ethernet backhaul servicing about 45 clients (25% wired and 75% wireless). No issues so far since the upgrade. Network connectivity appears to be stable with 2 people working remotely via separate VPNs alongside media streaming, etc. Noticed some speed improvements as well.
-
@UI-AmpliFi will there ever be vlan tagging support on wifi networks. Or is there already and I just do not know?
-
is there someone here that uses the Amplifi HD unit on PPPoE (Vlan) fiber and uses DHCP6 IPV6? i get a "check ipv6 settings" message in the app and the weird thing is.. IPV6 DHCP6 works ok when i check the network information on all my IPV6 supported devices (same thing happens on my Alien with the 3.6.0RC2 firmware), i think the amplifi app needs a big update
-
@dexx64
Yes same bug on mine with DHCP 6 with client ID. Sky broadband. But ipv6 works if I ask google what my IP address is. It comes back as ipv6
-
@krisdelta ok cool, this is a bug for sure
-
This is the first time I’ve been mildly tempted to update from 3.1.2 - anyone else in the same boat?
-
@John-Samuelson I too had not updated from 3.1.2, mainly because of the number of problems that were being encountered by updates since the 3.1.2 update. I would wait at least a month before deciding to do an update. In most cases, the number of reported problems after the first week was enough to make me shy away from an update.
For 3.6 the number of problems after a week has been so few that I decided to not wait a month before making the decision to update to 3.6. I updated this morning and will post about any problems I encounter.
-
@James-Earl-Ford Thanks for going guinea pig for me! Also interested in any new functionality you find/like. I’m currently using a little Edgerouter with the Amplifis just as access points.
-
@John-Samuelson We live in an apartment, therefore we have the simplest of environments, only 1 Amplifi HD. We normally have 12-15 devices connected.
The only changes I made were to turn on IPv6 and enable "spanning tree". I have noticed a slight uptick in speed from 400/20 to 450/21.
-
@James-Earl-Ford Interesting. We have around 30 devices, gigabit internet and 3x HDs backhauled. No IPV6 yet sadly…
-
@John-Samuelson Is your ISP not providing it? I turned it on in the Web UI. It can also be turned on via the Amplifi app. Here is a link showing both methods.
https://help.amplifi.com/hc/en-us/articles/115009768148-Setting-Up-IPv6
So far no issues with it.
-
@John-Samuelson I’m also on 3.1.2. It works and have been hesitant to upgrade based on the comments for all of the subsequent releases. This one might be the one where I finally do
-
Not for the first time in Amplifi FW updates, 3.6.0 completely borks wired connections for me. I reset the Amplifi's and ethernet switches multiple times without any success. Rolling back to 3.4.4 instantly resolved the issue.
