#unifi — Public Fediverse posts

For those running new #AppleWatch or #iPhone and a #Ubiquiti #Unifi set up. Make sure to turn on UAPSD in your WiFi settings as it seems without Apple Watch stays on WiFi permanently rather than standing down and just occasionally turning on.

For those running new #AppleWatch or #iPhone and a #Ubiquiti #Unifi set up. Make sure to turn on UAPSD in your WiFi settings as it seems without Apple Watch stays on WiFi permanently rather than standing down and just occasionally turning on.

For those running new #AppleWatch or #iPhone and a #Ubiquiti #Unifi set up. Make sure to turn on UAPSD in your WiFi settings as it seems without Apple Watch stays on WiFi permanently rather than standing down and just occasionally turning on.

For those running new #AppleWatch or #iPhone and a #Ubiquiti #Unifi set up. Make sure to turn on UAPSD in your WiFi settings as it seems without Apple Watch stays on WiFi permanently rather than standing down and just occasionally turning on.

In the same time frame, all the traffic on the fediverse that reaches my server plus 22GB of me transferring files did not exceed my guest's Facebook traffic.

#statistics #unifi #fediverse #trafficanalysis

The new #UniFi router allows me to import a CSV, because duh. Why would that not be a feature?

The new #UniFi router allows me to import a CSV, because duh. Why would that not be a feature?

The new #UniFi router allows me to import a CSV, because duh. Why would that not be a feature?

The new #UniFi router allows me to import a CSV, because duh. Why would that not be a feature?

Another #unifi related post - I can't but notice how heavily #Ubiquiti is pushing the #UX7 for a mesh network component, which is a bit weird as my first encounter with it was as a "cloud" gateway + AP. Here, "cloud" means that it has a controller software built in, which generally makes their devices the only Unifi controller, so how can they recommend having more than one?

My first Unifi device was a switch, but only after I learned that you don't need a "Cloud Key" as you can #selfhost their management software. This then turned upside down when I chose to add a Cloud Gateway Ultra, not realising that the builtin controller ("Cloud" - nomen est omen) means self-hosting the management is now not just unneeded, but not even possible: I had to start using the built in component of the gateway.

That makes considering the UX7 quite confusing - I know I can add a UX7 as an AP, as it's sold like that, but could I add it as a cloud key + AP to a system to replace a selfhosted controller?

The main disadvantage of it is that port-wise it's a very stripped down device; while having 10G AND 2.5G is a somewhat premium feature, having only these two ports is super weird.

If you have a 2.5G WAN, why would you need 10G anywhere else?

If you have 10G upstream, why would you be OK with 2.5G leaving the device?

Well, now I glossed over it being a Wifi7 AP, easily reaching 1+ Gb today, so some of the extra bandwidth can go there, but 5+Gb of Wifi7 is not something I can imagine used by consumer devices to offset the lack of a second 10G port.

It's still a great AP, but maybe not at today's prices, though it could perhaps become a great microserver in a few years time when Unifi finally abandons it for UX9.

Another #unifi related post - I can't but notice how heavily #Ubiquiti is pushing the #UX7 for a mesh network component, which is a bit weird as my first encounter with it was as a "cloud" gateway + AP. Here, "cloud" means that it has a controller software built in, which generally makes their devices the only Unifi controller, so how can they recommend having more than one?

My first Unifi device was a switch, but only after I learned that you don't need a "Cloud Key" as you can #selfhost their management software. This then turned upside down when I chose to add a Cloud Gateway Ultra, not realising that the builtin controller ("Cloud" - nomen est omen) means self-hosting the management is now not just unneeded, but not even possible: I had to start using the built in component of the gateway.

That makes considering the UX7 quite confusing - I know I can add a UX7 as an AP, as it's sold like that, but could I add it as a cloud key + AP to a system to replace a selfhosted controller?

The main disadvantage of it is that port-wise it's a very stripped down device; while having 10G AND 2.5G is a somewhat premium feature, having only these two ports is super weird.

If you have a 2.5G WAN, why would you need 10G anywhere else?

If you have 10G upstream, why would you be OK with 2.5G leaving the device?

Well, now I glossed over it being a Wifi7 AP, easily reaching 1+ Gb today, so some of the extra bandwidth can go there, but 5+Gb of Wifi7 is not something I can imagine used by consumer devices to offset the lack of a second 10G port.

It's still a great AP, but maybe not at today's prices, though it could perhaps become a great microserver in a few years time when Unifi finally abandons it for UX9.

Another #unifi related post - I can't but notice how heavily #Ubiquiti is pushing the #UX7 for a mesh network component, which is a bit weird as my first encounter with it was as a "cloud" gateway + AP. Here, "cloud" means that it has a controller software built in, which generally makes their devices the only Unifi controller, so how can they recommend having more than one?

My first Unifi device was a switch, but only after I learned that you don't need a "Cloud Key" as you can #selfhost their management software. This then turned upside down when I chose to add a Cloud Gateway Ultra, not realising that the builtin controller ("Cloud" - nomen est omen) means self-hosting the management is now not just unneeded, but not even possible: I had to start using the built in component of the gateway.

That makes considering the UX7 quite confusing - I know I can add a UX7 as an AP, as it's sold like that, but could I add it as a cloud key + AP to a system to replace a selfhosted controller?

The main disadvantage of it is that port-wise it's a very stripped down device; while having 10G AND 2.5G is a somewhat premium feature, having only these two ports is super weird.

If you have a 2.5G WAN, why would you need 10G anywhere else?

If you have 10G upstream, why would you be OK with 2.5G leaving the device?

Well, now I glossed over it being a Wifi7 AP, easily reaching 1+ Gb today, so some of the extra bandwidth can go there, but 5+Gb of Wifi7 is not something I can imagine used by consumer devices to offset the lack of a second 10G port.

It's still a great AP, but maybe not at today's prices, though it could perhaps become a great microserver in a few years time when Unifi finally abandons it for UX9.

Another #unifi related post - I can't but notice how heavily #Ubiquiti is pushing the #UX7 for a mesh network component, which is a bit weird as my first encounter with it was as a "cloud" gateway + AP. Here, "cloud" means that it has a controller software built in, which generally makes their devices the only Unifi controller, so how can they recommend having more than one?

My first Unifi device was a switch, but only after I learned that you don't need a "Cloud Key" as you can #selfhost their management software. This then turned upside down when I chose to add a Cloud Gateway Ultra, not realising that the builtin controller ("Cloud" - nomen est omen) means self-hosting the management is now not just unneeded, but not even possible: I had to start using the built in component of the gateway.

That makes considering the UX7 quite confusing - I know I can add a UX7 as an AP, as it's sold like that, but could I add it as a cloud key + AP to a system to replace a selfhosted controller?

The main disadvantage of it is that port-wise it's a very stripped down device; while having 10G AND 2.5G is a somewhat premium feature, having only these two ports is super weird.

If you have a 2.5G WAN, why would you need 10G anywhere else?

If you have 10G upstream, why would you be OK with 2.5G leaving the device?

Well, now I glossed over it being a Wifi7 AP, easily reaching 1+ Gb today, so some of the extra bandwidth can go there, but 5+Gb of Wifi7 is not something I can imagine used by consumer devices to offset the lack of a second 10G port.

It's still a great AP, but maybe not at today's prices, though it could perhaps become a great microserver in a few years time when Unifi finally abandons it for UX9.

Another #unifi related post - I can't but notice how heavily #Ubiquiti is pushing the #UX7 for a mesh network component, which is a bit weird as my first encounter with it was as a "cloud" gateway + AP. Here, "cloud" means that it has a controller software built in, which generally makes their devices the only Unifi controller, so how can they recommend having more than one?

My first Unifi device was a switch, but only after I learned that you don't need a "Cloud Key" as you can #selfhost their management software. This then turned upside down when I chose to add a Cloud Gateway Ultra, not realising that the builtin controller ("Cloud" - nomen est omen) means self-hosting the management is now not just unneeded, but not even possible: I had to start using the built in component of the gateway.

That makes considering the UX7 quite confusing - I know I can add a UX7 as an AP, as it's sold like that, but could I add it as a cloud key + AP to a system to replace a selfhosted controller?

The main disadvantage of it is that port-wise it's a very stripped down device; while having 10G AND 2.5G is a somewhat premium feature, having only these two ports is super weird.

If you have a 2.5G WAN, why would you need 10G anywhere else?

If you have 10G upstream, why would you be OK with 2.5G leaving the device?

Well, now I glossed over it being a Wifi7 AP, easily reaching 1+ Gb today, so some of the extra bandwidth can go there, but 5+Gb of Wifi7 is not something I can imagine used by consumer devices to offset the lack of a second 10G port.

It's still a great AP, but maybe not at today's prices, though it could perhaps become a great microserver in a few years time when Unifi finally abandons it for UX9.