#unifi — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #unifi, aggregated by home.social.
-
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.
-
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.
-
Love it when things just work together.
-
Love it when things just work together.
-
Love it when things just work together.
-
Just wanted to document the current limitation of the Unifi Network system for mobile/cellular backups. In my case it’s not a big deal, more of surprise that I can’t even test an additional device on the same site before taking it to its intended location.
There seems to be a way to hack it around by having the primary device on the WAN port, but it’s not really important for me.
The only real use case I can come up with is to have two mobile fallbacks on two independent sims* on a different place on the same site/house (say two corners of a larger house/garden for example).
*ignoring my hunch that most networks have merged their infrastructure in many countries to have shared towers/connectivity.
-
Just wanted to document the current limitation of the Unifi Network system for mobile/cellular backups. In my case it’s not a big deal, more of surprise that I can’t even test an additional device on the same site before taking it to its intended location.
There seems to be a way to hack it around by having the primary device on the WAN port, but it’s not really important for me.
The only real use case I can come up with is to have two mobile fallbacks on two independent sims* on a different place on the same site/house (say two corners of a larger house/garden for example).
*ignoring my hunch that most networks have merged their infrastructure in many countries to have shared towers/connectivity.
-
Just wanted to document the current limitation of the Unifi Network system for mobile/cellular backups. In my case it’s not a big deal, more of surprise that I can’t even test an additional device on the same site before taking it to its intended location.
There seems to be a way to hack it around by having the primary device on the WAN port, but it’s not really important for me.
The only real use case I can come up with is to have two mobile fallbacks on two independent sims* on a different place on the same site/house (say two corners of a larger house/garden for example).
*ignoring my hunch that most networks have merged their infrastructure in many countries to have shared towers/connectivity.
-
Just wanted to document the current limitation of the Unifi Network system for mobile/cellular backups. In my case it’s not a big deal, more of surprise that I can’t even test an additional device on the same site before taking it to its intended location.
There seems to be a way to hack it around by having the primary device on the WAN port, but it’s not really important for me.
The only real use case I can come up with is to have two mobile fallbacks on two independent sims* on a different place on the same site/house (say two corners of a larger house/garden for example).
*ignoring my hunch that most networks have merged their infrastructure in many countries to have shared towers/connectivity.
-
Just wanted to document the current limitation of the Unifi Network system for mobile/cellular backups. In my case it’s not a big deal, more of surprise that I can’t even test an additional device on the same site before taking it to its intended location.
There seems to be a way to hack it around by having the primary device on the WAN port, but it’s not really important for me.
The only real use case I can come up with is to have two mobile fallbacks on two independent sims* on a different place on the same site/house (say two corners of a larger house/garden for example).
*ignoring my hunch that most networks have merged their infrastructure in many countries to have shared towers/connectivity.
-
No fetish, just a hobby. Repatched my home network rig in my basement. Don't mind the dust 😅
#Hobby #Network #Networking #Unifi #Ubiquitiy #UDMSE #USW24POE
-
No fetish, just a hobby. Repatched my home network rig in my basement. Don't mind the dust 😅
#Hobby #Network #Networking #Unifi #Ubiquitiy #UDMSE #USW24POE
-
Syria, Cyprus Sign Ebla Cable Agreement
Nawal Jeles, SANASeptember 13, 2026 Syria’s Ministry of Communications and Information Technology says an agreement has been signed…
#Conflict #Conflicts #War #cyprus #Cyta #Mediterranean #SUBSEACABLE #Syria #Unifi
https://www.europesays.com/3252888/ -
https://www.europesays.com/iran/293462/ Syria, Cyprus Sign Ebla Cable Agreement #Cyprus #Cyta #Mediterranean #SubseaCable #Syria #Unifi
-
Syria, Cyprus Sign Ebla Cable Agreement https://www.byteseu.com/2368575/ #Conflicts #Cyprus #Cyta #Mediterranean #SubseaCable #Syria #Unifi
-
-
-
-
-
Argh, looks like the end of my current UniFi Network Controller running on #NixOS is now close to inevitable.
They only support now running a full VM appliance - the so-called "UniFi OS Server" for self-hosters instead of just the actual network controller service as standalone component within an existing system.
I feel zero motivation to spin up a VM somewhere for this kind of mutable workloads that elude sane NixOS-based management methods.
-
Argh, looks like the end of my current UniFi Network Controller running on #NixOS is now close to inevitable.
They only support now running a full VM appliance - the so-called "UniFi OS Server" for self-hosters instead of just the actual network controller service as standalone component within an existing system.
I feel zero motivation to spin up a VM somewhere for this kind of mutable workloads that elude sane NixOS-based management methods.
-
Argh, looks like the end of my current UniFi Network Controller running on #NixOS is now close to inevitable.
They only support now running a full VM appliance - the so-called "UniFi OS Server" for self-hosters instead of just the actual network controller service as standalone component within an existing system.
I feel zero motivation to spin up a VM somewhere for this kind of mutable workloads that elude sane NixOS-based management methods.
-
Argh, looks like the end of my current UniFi Network Controller running on #NixOS is now close to inevitable.
They only support now running a full VM appliance - the so-called "UniFi OS Server" for self-hosters instead of just the actual network controller service as standalone component within an existing system.
I feel zero motivation to spin up a VM somewhere for this kind of mutable workloads that elude sane NixOS-based management methods.
-
Argh, looks like the end of my current UniFi Network Controller running on #NixOS is now close to inevitable.
They only support now running a full VM appliance - the so-called "UniFi OS Server" for self-hosters instead of just the actual network controller service as standalone component within an existing system.
I feel zero motivation to spin up a VM somewhere for this kind of mutable workloads that elude sane NixOS-based management methods.
-
-
-
-
Ich habe doch gerade erst einen Travel Router gekauft 😭 https://youtu.be/TJQP7hRiWNo
-
My MacBook started complaining about the ip address being in use, which is odd because it’s a static dhcp lease. But no, there’s clearly an ARP reply coming in and MacBook rejects dhcp.
Stop 1: mikrotik/unifi know nothing about the offending mac.
Stop 2: WiFi AP says it’s coming from eth upstream based on tcpdump
Stop 3: can’t tcpdump the switch but it’s mac table has no mention of the offending macHuh.
Reading closer, reply comes on vlan 1. But I don’t have vlan 1!
Stop 4: apparently there is a hidden vlan 1 on unifi switch and it has the offending mac. Wtf unifi? It came from port 7 - the other AP
Stop 5: the other AP… generates the offending packet.So let me get this straight: something in unifi leaks from vlan 50 to vlan 1 (and I don’t even have vlan 1!) where unifi AP hallucinates a reply and then it leaks all the way to vlan 50 and fuck up my MacBook’s dhcp.
I should become a sheep farmer…
-
My MacBook started complaining about the ip address being in use, which is odd because it’s a static dhcp lease. But no, there’s clearly an ARP reply coming in and MacBook rejects dhcp.
Stop 1: mikrotik/unifi know nothing about the offending mac.
Stop 2: WiFi AP says it’s coming from eth upstream based on tcpdump
Stop 3: can’t tcpdump the switch but it’s mac table has no mention of the offending macHuh.
Reading closer, reply comes on vlan 1. But I don’t have vlan 1!
Stop 4: apparently there is a hidden vlan 1 on unifi switch and it has the offending mac. Wtf unifi? It came from port 7 - the other AP
Stop 5: the other AP… generates the offending packet.So let me get this straight: something in unifi leaks from vlan 50 to vlan 1 (and I don’t even have vlan 1!) where unifi AP hallucinates a reply and then it leaks all the way to vlan 50 and fuck up my MacBook’s dhcp.
I should become a sheep farmer…
-
My MacBook started complaining about the ip address being in use, which is odd because it’s a static dhcp lease. But no, there’s clearly an ARP reply coming in and MacBook rejects dhcp.
Stop 1: mikrotik/unifi know nothing about the offending mac.
Stop 2: WiFi AP says it’s coming from eth upstream based on tcpdump
Stop 3: can’t tcpdump the switch but it’s mac table has no mention of the offending macHuh.
Reading closer, reply comes on vlan 1. But I don’t have vlan 1!
Stop 4: apparently there is a hidden vlan 1 on unifi switch and it has the offending mac. Wtf unifi? It came from port 7 - the other AP
Stop 5: the other AP… generates the offending packet.So let me get this straight: something in unifi leaks from vlan 50 to vlan 1 (and I don’t even have vlan 1!) where unifi AP hallucinates a reply and then it leaks all the way to vlan 50 and fuck up my MacBook’s dhcp.
I should become a sheep farmer…
-
My MacBook started complaining about the ip address being in use, which is odd because it’s a static dhcp lease. But no, there’s clearly an ARP reply coming in and MacBook rejects dhcp.
Stop 1: mikrotik/unifi know nothing about the offending mac.
Stop 2: WiFi AP says it’s coming from eth upstream based on tcpdump
Stop 3: can’t tcpdump the switch but it’s mac table has no mention of the offending macHuh.
Reading closer, reply comes on vlan 1. But I don’t have vlan 1!
Stop 4: apparently there is a hidden vlan 1 on unifi switch and it has the offending mac. Wtf unifi? It came from port 7 - the other AP
Stop 5: the other AP… generates the offending packet.So let me get this straight: something in unifi leaks from vlan 50 to vlan 1 (and I don’t even have vlan 1!) where unifi AP hallucinates a reply and then it leaks all the way to vlan 50 and fuck up my MacBook’s dhcp.
I should become a sheep farmer…
-
My MacBook started complaining about the ip address being in use, which is odd because it’s a static dhcp lease. But no, there’s clearly an ARP reply coming in and MacBook rejects dhcp.
Stop 1: mikrotik/unifi know nothing about the offending mac.
Stop 2: WiFi AP says it’s coming from eth upstream based on tcpdump
Stop 3: can’t tcpdump the switch but it’s mac table has no mention of the offending macHuh.
Reading closer, reply comes on vlan 1. But I don’t have vlan 1!
Stop 4: apparently there is a hidden vlan 1 on unifi switch and it has the offending mac. Wtf unifi? It came from port 7 - the other AP
Stop 5: the other AP… generates the offending packet.So let me get this straight: something in unifi leaks from vlan 50 to vlan 1 (and I don’t even have vlan 1!) where unifi AP hallucinates a reply and then it leaks all the way to vlan 50 and fuck up my MacBook’s dhcp.
I should become a sheep farmer…
-
Ubiquiti Patches Three Maximum-Severity Flaws in UniFi Line
Ubiquiti has patched three critical vulnerabilities in its UniFi line, with a severity score of 10 out of 10, that could allow hackers to gain control of affected devices. These flaws, along with 19 others, were disclosed in a security bulletin, highlighting the need for immediate updates.
-
Ubiquiti Patches Three Maximum-Severity Flaws in UniFi Line
Ubiquiti has patched three critical vulnerabilities in its UniFi line, with a severity score of 10 out of 10, that could allow hackers to gain control of affected devices. These flaws, along with 19 others, were disclosed in a security bulletin, highlighting the need for immediate updates.
-
Ubiquiti issues critical security fixes for UniFi OS, UniFi Network, UniFi Protect, UniFi Talk
https://www.bleepingcomputer.com/news/security/ubiquiti-patches-three-max-severity-security-vulnerabilities/
- - -
Ubiquiti émet des correctifs de sécurité critiques pour UniFi OS, UniFi Network, UniFi Protect, UniFi Talk// Article en anglais //
#Ubiquiti #UniFi #InfoSec #InformationSecurity #Cybersécurité
-
Ubiquiti issues critical security fixes for UniFi OS, UniFi Network, UniFi Protect, UniFi Talk
https://www.bleepingcomputer.com/news/security/ubiquiti-patches-three-max-severity-security-vulnerabilities/
- - -
Ubiquiti émet des correctifs de sécurité critiques pour UniFi OS, UniFi Network, UniFi Protect, UniFi Talk// Article en anglais //
#Ubiquiti #UniFi #InfoSec #InformationSecurity #Cybersécurité
-
Ubiquiti issues critical security fixes for UniFi OS, UniFi Network, UniFi Protect, UniFi Talk
https://www.bleepingcomputer.com/news/security/ubiquiti-patches-three-max-severity-security-vulnerabilities/
- - -
Ubiquiti émet des correctifs de sécurité critiques pour UniFi OS, UniFi Network, UniFi Protect, UniFi Talk// Article en anglais //
#Ubiquiti #UniFi #InfoSec #InformationSecurity #Cybersécurité
-
Ubiquiti issues critical security fixes for UniFi OS, UniFi Network, UniFi Protect, UniFi Talk
https://www.bleepingcomputer.com/news/security/ubiquiti-patches-three-max-severity-security-vulnerabilities/
- - -
Ubiquiti émet des correctifs de sécurité critiques pour UniFi OS, UniFi Network, UniFi Protect, UniFi Talk// Article en anglais //
#Ubiquiti #UniFi #InfoSec #InformationSecurity #Cybersécurité
-
Ubiquiti issues critical security fixes for UniFi OS, UniFi Network, UniFi Protect, UniFi Talk
https://www.bleepingcomputer.com/news/security/ubiquiti-patches-three-max-severity-security-vulnerabilities/
- - -
Ubiquiti émet des correctifs de sécurité critiques pour UniFi OS, UniFi Network, UniFi Protect, UniFi Talk// Article en anglais //
#Ubiquiti #UniFi #InfoSec #InformationSecurity #Cybersécurité
-
Ubiquiti patched 22 UniFi flaws. Three hit CVSS 10.0, including command injection CVE-2026-77537. Update UniFi Protect, OS, and Talk now.
#Ubiquiti #UniFi #CyberSecurity #CommandInjection #CVE202677537
-
Ubiquiti patched 22 UniFi flaws. Three hit CVSS 10.0, including command injection CVE-2026-77537. Update UniFi Protect, OS, and Talk now.
#Ubiquiti #UniFi #CyberSecurity #CommandInjection #CVE202677537
-
Ubiquiti patched 22 UniFi flaws. Three hit CVSS 10.0, including command injection CVE-2026-77537. Update UniFi Protect, OS, and Talk now.
#Ubiquiti #UniFi #CyberSecurity #CommandInjection #CVE202677537
