home.social

#unifi — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #unifi, aggregated by home.social.

fetched live
  1. 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
    europesays.com/3252888/

  2. 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.

    #NixOS #UniFi

  3. 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.

    #NixOS #UniFi

  4. 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.

    #NixOS #UniFi

  5. 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.

    #NixOS #UniFi

  6. 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.

    #NixOS #UniFi

  7. 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 mac

    Huh.

    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…

    #networking #unifi #bullshit

  8. 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 mac

    Huh.

    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…

    #networking #unifi #bullshit

  9. 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 mac

    Huh.

    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…

    #networking #unifi #bullshit

  10. 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 mac

    Huh.

    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…

    #networking #unifi #bullshit

  11. 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 mac

    Huh.

    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…

    #networking #unifi #bullshit

  12. 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.

    osintsights.com/ubiquiti-patch

    #Ubiquiti #Unifi #Cve202677537 #Cve202677550 #Cve202677554

  13. 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.

    osintsights.com/ubiquiti-patch

    #Ubiquiti #Unifi #Cve202677537 #Cve202677550 #Cve202677554

  14. Ubiquiti issues critical security fixes for UniFi OS, UniFi Network, UniFi Protect, UniFi Talk

    bleepingcomputer.com/news/secu
    - - -
    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é

  15. Ubiquiti issues critical security fixes for UniFi OS, UniFi Network, UniFi Protect, UniFi Talk

    bleepingcomputer.com/news/secu
    - - -
    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é

  16. Ubiquiti issues critical security fixes for UniFi OS, UniFi Network, UniFi Protect, UniFi Talk

    bleepingcomputer.com/news/secu
    - - -
    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é

  17. Ubiquiti issues critical security fixes for UniFi OS, UniFi Network, UniFi Protect, UniFi Talk

    bleepingcomputer.com/news/secu
    - - -
    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é

  18. Ubiquiti issues critical security fixes for UniFi OS, UniFi Network, UniFi Protect, UniFi Talk

    bleepingcomputer.com/news/secu
    - - -
    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é

  19. Automate importing ACME Let's Encrypt SSL certs into the UniFi Network Application Java keystore using keytool. Convert PEM files seamlessly on Ubuntu/Debian. #unifi #ssl #letsencrypt

    valtersit.com/vault/automated-

  20. Automate importing ACME Let's Encrypt SSL certs into the UniFi Network Application Java keystore using keytool. Convert PEM files seamlessly on Ubuntu/Debian. #unifi #ssl #letsencrypt

    valtersit.com/vault/automated-

  21. Deploy a headless UniFi Controller using Docker Compose and external MongoDB 7.0. Configured with persistent storage mounts and essential port mappings for L3 adoption and AP management. #docker #unifi #mongodb

    valtersit.com/vault/deploying-

  22. Deploy a headless UniFi Controller using Docker Compose and external MongoDB 7.0. Configured with persistent storage mounts and essential port mappings for L3 adoption and AP management. #docker #unifi #mongodb

    valtersit.com/vault/deploying-

  23. Hey #network nerds. I've got a #Unifi Dream Machine behind my Xfinity modem. I need to enable a port forward for Plex, but it doesn't seem to work unless I turn on bridge mode on the modem. But if I do that, it seems to negatively impact my speeds (a lot, down to 100Mbps up/30 down, from 1G/1G). So I've enabled DMZ on the modem for my router's internal IP address (only device connected to the modem). Since the UDM is designed to be directly connected to the net anyway, it feels like using DMZ is a non-issue. Am I understanding that correctly? TIA

  24. Hey #network nerds. I've got a #Unifi Dream Machine behind my Xfinity modem. I need to enable a port forward for Plex, but it doesn't seem to work unless I turn on bridge mode on the modem. But if I do that, it seems to negatively impact my speeds (a lot, down to 100Mbps up/30 down, from 1G/1G). So I've enabled DMZ on the modem for my router's internal IP address (only device connected to the modem). Since the UDM is designed to be directly connected to the net anyway, it feels like using DMZ is a non-issue. Am I understanding that correctly? TIA

  25. Hey nerds. I've got a Dream Machine behind my Xfinity modem. I need to enable a port forward for Plex, but it doesn't seem to work unless I turn on bridge mode on the modem. But if I do that, it seems to negatively impact my speeds (a lot, down to 100Mbps up/30 down, from 1G/1G). So I've enabled DMZ on the modem for my router's internal IP address (only device connected to the modem). Since the UDM is designed to be directly connected to the net anyway, it feels like using DMZ is a non-issue. Am I understanding that correctly? TIA

  26. Hey #network nerds. I've got a #Unifi Dream Machine behind my Xfinity modem. I need to enable a port forward for Plex, but it doesn't seem to work unless I turn on bridge mode on the modem. But if I do that, it seems to negatively impact my speeds (a lot, down to 100Mbps up/30 down, from 1G/1G). So I've enabled DMZ on the modem for my router's internal IP address (only device connected to the modem). Since the UDM is designed to be directly connected to the net anyway, it feels like using DMZ is a non-issue. Am I understanding that correctly? TIA

  27. Hey #network nerds. I've got a #Unifi Dream Machine behind my Xfinity modem. I need to enable a port forward for Plex, but it doesn't seem to work unless I turn on bridge mode on the modem. But if I do that, it seems to negatively impact my speeds (a lot, down to 100Mbps up/30 down, from 1G/1G). So I've enabled DMZ on the modem for my router's internal IP address (only device connected to the modem). Since the UDM is designed to be directly connected to the net anyway, it feels like using DMZ is a non-issue. Am I understanding that correctly? TIA

  28. DIY Checkpoint:

    All working. I need to neaten up the cabling, but #ev charger and garage door are on my #IoT wifi network finally.

    Next up, wiring in my Shelly relays and installing the #UniFi cameras.

  29. DIY Checkpoint:

    All working. I need to neaten up the cabling, but charger and garage door are on my wifi network finally.

    Next up, wiring in my Shelly relays and installing the cameras.

  30. DIY Checkpoint:

    All working. I need to neaten up the cabling, but #ev charger and garage door are on my #IoT wifi network finally.

    Next up, wiring in my Shelly relays and installing the #UniFi cameras.