UniFi OS - Dream Machines 2.x #416

StiviiK · 2022-09-22T14:23:20Z

Ubiquiti recently annouced in the latest update notes for the UniFi OS - Dream Machines, they will migrate to 2.x soon.
https://community.ui.com/releases/UniFi-OS-Dream-Machines-1-12-30/a4f85653-7bc6-461a-8715-94298cb69164

If I am not mistaken, that means they will align the firmware with the firmware of the UDM SE.
Do you know what are the effects of that and how the work of this awesome project will be affected?
I am only aware that this will drop Podman?

SamErde · 2022-09-22T15:54:40Z

I've been wondering the same thing.

boostchicken · 2022-11-16T09:15:47Z

So this means a couple things I believe. You will have to install podman via our udm-se builds probably. Beyond that the baseOS will have systemd now and if I remember correctly they let you customize. I think it will get rid of the need for the deb install and we will just have to update all instructions here to take 2.0 into account.

Slychocobo · 2022-11-16T18:29:32Z

That's good to hear, I've been holding off upgrading because quite used to using Pihole :)

dvcrn · 2022-11-17T00:19:04Z

Curious if anyone had success with recent versions and installing podman from udm-se? My UDM is stuck on 1.11.4 (with podman 1.x) because of trauma from updating firmwares in the past

user45876 · 2022-12-15T13:11:58Z

Version 2.4 is now live for UDM (base, pro): https://community.ui.com/releases/UniFi-OS-Dream-Machines-2-4-23/aebbba64-9e7e-4151-bcca-34ed08761f08
Thanks a lot for your work so far! I am badly wanting to get DNS-Requests redirected :)

OfficialHoSay · 2022-12-15T16:05:26Z

Has anyone performed the migration to 2.4.23?

Did any data related to on_boot remain on disk?

Does the migration nuke everything?

I'm hesitant to upgrade this early as I do need my DNS redirect and cloudflared services to remain running.

aniolpages · 2022-12-15T16:24:16Z

All erased on my UDMB, no data folder in mnt

bananaman2020 · 2022-12-15T16:25:33Z

Has anyone performed the migration to 2.4.23?

Did any data related to on_boot remain on disk?

Does the migration nuke everything?

I'm hesitant to upgrade this early as I do need my DNS redirect and cloudflared services to remain running.

For me it got rid of the on_boot.d folder and any podman containers I had it also completely got rid of podman. It leaves Unifi OS related configs such as network but anything custom is gone.

mabunixda · 2022-12-15T18:07:53Z

Yes, everything was purged from this partition

mabunixda · 2022-12-15T18:14:02Z

root@udmp:/persistent# dpkg -i udm-boot_1.0.5_all.deb 
Selecting previously unselected package udm-boot.
(Reading database ... 50954 files and directories currently installed.)
Preparing to unpack udm-boot_1.0.5_all.deb ...
/var/lib/dpkg/tmp.ci/preinst: 19: /var/lib/dpkg/tmp.ci/preinst: /sbin/ssh-proxy: not found
dpkg: error processing archive udm-boot_1.0.5_all.deb (--install):
 subprocess new pre-installation script returned error exit status 127
/var/lib/dpkg/tmp.ci/postrm: 24: /var/lib/dpkg/tmp.ci/postrm: /sbin/ssh-proxy: not found

Well the current installation does not run, cleaning it with

root@udmp:~# dpkg --purge --force-all udm-boot

But with this update tools like ansible are working fine now

bennettp123 · 2022-12-15T23:03:55Z

All erased on my UDMB, no data folder in mnt

For me, /mnt/data/ is missing, but /mnt/.rwfs/data exists. However, it looks like it's been cleared out.
unifi-os shell results in -bash: unifi-os: command not found
The install script fails with Missing dependencie(s): `podman`

Not sure why /mnt/data is missing—the overlayfs is mounted

overlayfs-root on / type overlay (rw,noatime,nodiratime,lowerdir=/mnt/.rofs,upperdir=/mnt/.rwfs/data,workdir=/mnt/.rwfs/.workdir)

Edit: derp, it's mounted at /data, I guess that's the new location in 2.x.

How are people installing podman?

Edit 2: Got it working. I downloaded the install script, and modified the case "$(udm_model)" statement to run the udr|udmse case for udm:

From b368017f4f3e83161549e36c93ada2dede7d6ffc Mon Sep 17 00:00:00 2001
From: Bennett Perkins <bennettperkins@gmail.com>
Date: Fri, 16 Dec 2022 07:49:03 +0800
Subject: [PATCH] got remote_install.sh working on UDM 2.4.23

---
 on-boot-script/remote_install.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/on-boot-script/remote_install.sh b/on-boot-script/remote_install.sh
index 62de92c..87ce59e 100755
--- a/on-boot-script/remote_install.sh
+++ b/on-boot-script/remote_install.sh
@@ -160,7 +160,7 @@ depends_on curl
 ON_BOOT_D_PATH="$DATA_DIR/on_boot.d"
 
 case "$(udm_model)" in
-  udm|udmpro)
+  udmpro)
     echo "UDM/Pro detected, installing on-boot script..."
     depends_on podman
 
@@ -172,7 +172,7 @@ case "$(udm_model)" in
 
     echo "UDM Boot Script installed"
     ;;
-  udr|udmse)
+  udr|udmse|udm)
     echo "UDR/UDMSE detected, installing on-boot script..."
     depends_on systemctl
 
-- 
2.37.1 (Apple Git-137.1)

timrettop · 2022-12-15T23:10:13Z

The install script fails with Missing dependencie(s): `podman`

You will have to install podman via our udm-se builds probably.

In README.md
All artifacts can be found on IPFS https://unifi.boostchicken.io/

Extract the zip to the root of your device! Look at the assets on the Podman workflow.

timrettop · 2022-12-16T01:21:19Z

Using @bennetp123's advice, I was also able to install after updating my UDM base using the modified remote_install.sh
I tested the https://github.com/fire1ce/UDM-Persistent-SSH-Keys script and made two modifications to 99-ssh-keys.sh to use the /data path and to test for the existence of and make the /root/.ssh folder if necessary.

After that I'm able to ssh in with my key after reboot!

dvcrn · 2022-12-16T02:12:35Z

In README.md
All artifacts can be found on IPFS https://unifi.boostchicken.io/
Extract the zip to the root of your device! Look at the assets on the Podman workflow.

can someone confirm this working on UDM? Last upgrade I had to leave podman at 1.0 since the updated variants didn't work for me. Do those SE builds work on normal UDM as well?

Also how is the unifi-shell now executed? Previously that was a podman container, but that is no longer the case I presume?

jinkang23 · 2022-12-16T06:19:03Z

This worked for me but my testing is limited.
If you're willing to test it, you can use this:

curl -fsL "https://raw.githubusercontent.com/jinkang23/unifios-utilities/main/on-boot-script/remote_install.sh" | /bin/sh

I just submitted PR to add this change: #451

user45876 · 2022-12-16T07:13:40Z

Thanks, @jinkang23 , I tested it and it seems to be working. One question: The CNI Bridge is not needed if I only want to execute a startup script. Is it needed anyway, as there are no more containers on UDM FW2.x onwards?

bennettp123 · 2022-12-16T11:11:32Z

In README.md
All artifacts can be found on IPFS https://unifi.boostchicken.io/
Extract the zip to the root of your device! Look at the assets on the Podman workflow.

can someone confirm this working on UDM? Last upgrade I had to leave podman at 1.0 since the updated variants didn't work for me. Do those SE builds work on normal UDM as well?

I can confirm it's working, at least enough to get podman run --rm -it busybox working (edit: I got pihole up and running too, so I'd say it's thoroughly working)—though I needed to create some missing files manually, as outlined in #384:

/etc/containers/registries.conf
/etc/containers/policy.json
/etc/containers/storage.json

I used udmpro-podman-install.zip from https://unifi.boostchicken.io/ —not sure if that's the right version, or if there is even a difference between them (udmse-podman-install.zip seems to work fine too, though I didn't try to run any containers).

Also how is the unifi-shell now executed? Previously that was a podman container, but that is no longer the case I presume?

No idea—podman ps can't see it so I guess it doesn't exist 🙃

jinkang23 · 2022-12-16T15:56:24Z

Thanks, @jinkang23 , I tested it and it seems to be working. One question: The CNI Bridge is not needed if I only want to execute a startup script. Is it needed anyway, as there are no more containers on UDM FW2.x onwards?

Yea, I'm not sure about that. I figured it was there because you can still technically install podman. I suppose you could remove them afterwards if you don't plan on using it.

user45876 · 2022-12-16T19:19:04Z

I would suppose so as well. I just deleted the install (05...) and startup (06...) script and be fine with it.
I can also confirm that it is working well and also surviving reboots.

Thanks again for your efforts, very much appreciated, happy camper here :)

dvcrn · 2022-12-17T01:47:59Z

Thanks for the comments all! I know what my evening project will be, fingers crossed it goes equally smooth. I only have 2 podman containers to migrate but let's see...

Did upgrading the firmware wipe everything that was previously persisted in /mnt/data or did data files stay / got migrated to /data?

jfroy · 2022-12-17T02:34:14Z

Did upgrading the firmware wipe everything that was previously persisted in /mnt/data or did data files stay / got migrated to /data?

The migration will delete all data.

zlangbert · 2022-12-19T06:26:52Z

For anyone looking to install Podman I put together a build here. It's distributed through a Debian package so easy to install and remove (setup could done easily as an on_boot script). It uses current versions of Podman and its dependencies. So far working well for me on my UDMP on 2.4 and I plan to maintain this going forward.

Heavily inspired by the work done in this repo and the comments here about getting podman running. Wanted to share as it seemed it might save some people headache getting it working.

georgeboot · 2022-12-19T14:23:46Z

Does the configuration of Podman also get lost?

As in, if I install podman again after the update, will all my previously running containers be running in the state they were before the update? Or do I have to re-create / restore everything by hand?

gatesry · 2022-12-19T14:35:48Z

Does the configuration of Podman also get lost?

As in, if I install podman again after the update, will all my previously running containers be running in the state they were before the update? Or do I have to re-create / restore everything by hand?

The migration will delete all data.

henessy31 · 2022-12-20T09:58:15Z

For anyone looking to install Podman I put together a build here. It's distributed through a Debian package so easy to install and remove (setup could done easily as an on_boot script). It uses current versions of Podman and its dependencies. So far working well for me on my UDMP on 2.4 and I plan to maintain this going forward.

Heavily inspired by the work done in this repo and the comments here about getting podman running. Wanted to share as it seemed it might save some people headache getting it working.

Thank you so much! My UDM-PRO auto-updated over night to the 2.4 Firmware and everything was gone. With your Podman build I managed to bring back up my multicast-relay on my UDM-PRO.

dvcrn · 2022-12-23T09:18:13Z

Looks like they pulled the 2.x upgrade for UDM again. Anyone happen to have the firmware upgrade downloaded?

OfficialHoSay · 2023-02-28T16:39:55Z

One thing I noticed is that the following iptable rules seem to have stopped working for me after the migration to 2.4.27:
-A PREROUTING ! -s 192.168.6.254/32 ! -d 192.168.6.254/32 -i br76 -p udp -m udp --dport 53 -j LOG --log-prefix "[DNAT-br76-udp]"
-A PREROUTING ! -s 192.168.6.254/32 ! -d 192.168.6.254/32 -i br76 -p udp -m udp --dport 53 -j DNAT --to-destination 192.168.6.254
-A PREROUTING ! -s 192.168.6.254/32 ! -d 192.168.6.254/32 -i br76 -p tcp -m tcp --dport 53 -j LOG --log-prefix "[DNAT-br76-tcp]"
-A PREROUTING ! -s 192.168.6.254/32 ! -d 192.168.6.254/32 -i br76 -p tcp -m tcp --dport 53 -j DNAT --to-destination 192.168.6.254
They are supposed to redirect any DNS traffic to Pi-hole at 192.168.6.254, but none of these rules are getting hit... 😞

Try using this syntax, I'm using that and it works:

iptables -t nat -A PREROUTING -i br76 -p tcp ! -s 192.168.6.254 ! -d 192.168.6.254 --dport 53 -j DNAT --to 192.168.6.254
iptables -t nat -A PREROUTING -i br76 -p udp ! -s 192.168.6.254 ! -d 192.168.6.254 --dport 53 -j DNAT --to 192.168.6.254
iptables -t nat -A PREROUTING -i br76 -p tcp ! -s 192.168.6.254 ! -d 192.168.6.254 --dport 53 -j LOG --log-prefix "[DNAT-br76-tcp]"
iptables -t nat -A PREROUTING -i br76 -p udp ! -s 192.168.6.254 ! -d 192.168.6.254 --dport 53 -j LOG --log-prefix "[DNAT-br76-udp]”

What did stop working for me was the iptables statistics module to redirect DNS to multiple servers, I was formerly using:

iptables -t nat -A PREROUTING -i br0 -p tcp ! -s 10.0.1.0 ! -d 10.0.1.0 --dport 53 -m statistic --mode random --probability 0.5 -j DNAT --to 10.0.1.0
iptables -t nat -A PREROUTING -i br0 -p udp ! -s 10.0.1.0 ! -d 10.0.1.0 --dport 53 -m statistic --mode random --probability 0.5 -j DNAT --to 10.0.1.0

It seems like the kernel module for statistics: xt_statistic.ko is gone now. Anyone know a solution? Will it be there in 3.x FW?

pedropombeiro · 2023-02-28T18:12:46Z

Try using this syntax, I'm using that and it works:

@OfficialHoSay I'm actually using the same syntax. The syntax you see above is what gets output by ìptables-save | grep PREROUTING. Does your ìptables-save also change things to --to-destination?

pedropombeiro · 2023-02-28T18:16:25Z

Nevermind, it seems to be working after all. I tried changing the DNS server on another machine and it still hits the Pi-hole. My work laptop was in a strange state this morning, and I needed to reboot it in order to get it to not attempt to use 1.1.1.1 as the DNS server. All is well now, uff. Thanks for the help!

OfficialHoSay · 2023-02-28T18:32:08Z

Does your ìptables-save also change things to --to-destination?

Ah, I hadn't caught that. Yes mine also does that, but I'm not sure if it has always done that?

All is well now, uff. Thanks for the help!

But I'm glad it is now working.

I am running FW 2.5.16 and noticing that -m statistic is not working anymore, which is a bummer for us load-balancing DNS redirections. Is anyone running 2.5 or 3.X on a UXG-Pro, UDM-SE, or UDR that can tell me if -m statistic is working for them? Is there a way to add it back?

dvcrn · 2023-03-08T03:50:09Z

Just a little comment so people don't make the same mistake as me...

A few of my boot scripts were created under the assumption that the filesystem is ephemeral and lots of stuff will get wiped/reset between reboots, and I used them as-is for 2.x. For 1.x that was fine, but for 2.x that isn't the case, so I ran into some issues that caused my UDM to fill up and randomly crash/force reboot. Took me a while to figure out what's going on

Basically, make sure your scripts check for the current state before doing their thing

dvcrn · 2023-03-08T04:58:30Z

Slightly related, but could anyone do me a favor and upload their /usr/sbin/odhcp6c, or give me information on which version is running on the base UDM? I wiped mine by accident. Filled it with a recent deb variant, but there are slight differences, for example, the one I have not had a -D parameter

spali · 2023-03-08T15:36:11Z

@dvcrn Bit offtopic 😉 but here from my UDMP on 2.5.16:

Show

root@udmp:~# apt-cache show odhcp6c
Package: odhcp6c
Status: install ok installed
Priority: important
Section: misc
Installed-Size: 58
Maintainer: Yurii Haman <yurii.haman@ui.com>
Architecture: arm64
Version: 1.0.0-339+gee712e8
Depends: libc6 (>= 2.17)
Description: odhcp6c - Embedded DHCPv6 Client
Description-md5: 981e3b92ae88f0c7fe87b5c78ab768c8
Homepage: https://github.com/openwrt/odhcp6c

timrettop · 2023-03-08T18:02:28Z

@dvcrn Bit offtopic 😉 but here from my UDMP on 2.5.16:

Same output/md5 on my UDM Base with 2.5.16

dvcrn · 2023-03-08T22:08:15Z

@dvcrn Bit offtopic 😉 but here from my UDMP on 2.5.16:

Show


root@udmp:~# apt-cache show odhcp6c

Package: odhcp6c

Status: install ok installed

Priority: important

Section: misc

Installed-Size: 58

Maintainer: Yurii Haman <yurii.haman@ui.com>

Architecture: arm64

Version: 1.0.0-339+gee712e8

Depends: libc6 (>= 2.17)

Description: odhcp6c - Embedded DHCPv6 Client

Description-md5: 981e3b92ae88f0c7fe87b5c78ab768c8

Homepage: https://github.com/openwrt/odhcp6c

1.0.0-339+gee712e8

Awesome, thanks! I'll see if I can find/build that one for aarch64

It's installed in apt but not through a repository. So when it's gone you sadly can't just apt-get install it again. did a apt-get remove odhcp6c to fresh reinstall but now it's gone and I had to find a source/package that provides it. Debian experimental does, but the version is 1.1, hence the small differences 😅

bugsnatch · 2023-03-14T14:56:00Z

I had a working pihole setup on 1.x UDMP and after I decided to upgrade to 2.4.17 it doesn't work anymore

By following this thread and new input I did configuration from scratch (including onboot and podman installation) but somehow it looks like my container don't have internet access.

Did anybody experienced this already?

[i] FTL binding to default interface: eth0 [i] Enabling Query Logging [i] Testing lighttpd config: Syntax OK [i] All config checks passed, cleared for startup ... [i] Docker start setup complete
[i] Time until retry: 120 [i] Time until retry: 120 [✗] DNS resolution is not available

Shouldn't the binding interface a different one (ex. using default setup br5 )?

dvcrn · 2023-03-14T22:30:47Z

By following this thread and new input I did configuration from scratch (including onboot and podman installation) but somehow it looks like my container don't have internet access.

Sounds like something wrong with your dns or postman network settings. Can you post your dns/network config scripts?

Are those logs from within the container? It's still going to be en0 inside

pedropombeiro · 2023-03-18T10:17:02Z

I've upgraded from 2.4 to 2.5 and noticed that the multicast-relay container is not healthy. It keeps logging the following error:

starting multicast-relay
Using Interfaces: eth8 br46 br56 br76 br96
Using Options --foreground  --noSonosDiscovery
Traceback (most recent call last):
  File "//./multicast-relay/multicast-relay.py", line 1029, in <module>
    sys.exit(main())
  File "//./multicast-relay/multicast-relay.py", line 1024, in main
    packetRelay.addListener(addr, port, relay[1])
  File "//./multicast-relay/multicast-relay.py", line 294, in addListener
    rx = socket.socket(socket.AF_INET, socket.SOCK_RAW, socket.IPPROTO_UDP)
  File "/usr/lib/python3.10/socket.py", line 232, in __init__
    _socket.socket.__init__(self, family, type, proto, fileno)
PermissionError: [Errno 1] Operation not permitted

Anyone else seeing this?

joshuaspence · 2023-03-18T11:09:44Z

@pedropombeiro how are you running it exactly?

pedropombeiro · 2023-03-18T11:11:29Z

@pedropombeiro how are you running it exactly?

@joshuaspence

#!/bin/bash

CONTAINER=multicast-relay

# kill all instances of avahi-daemon (UDM spins an instance up even with mDNS services disabled)
killall avahi-daemon

# Starts a multicast-relay container that is deleted after it is stopped.
if podman container exists "${CONTAINER}"; then
  podman start "${CONTAINER}"
else
  podman run -d \
    --name "${CONTAINER}" \
    --net="host" \
    --security-opt=no-new-privileges \
    --restart=always \
    -e OPTS="--noSonosDiscovery" \
    -e INTERFACES="eth8 br46 br56 br76 br96" \
    -e TZ="$(cat /data/system/timezone)" \
    scyto/multicast-relay
fi

joshuaspence · 2023-03-18T11:30:12Z

Could be no-new-privileges?

pedropombeiro · 2023-03-18T11:56:52Z

Could be no-new-privileges?

That was the first thing I tried (removing it), but no change.

joshuaspence · 2023-03-18T12:43:33Z

Ok, not sure then. I am using multicast-relay on a UXG with Unifi OS 3 without issues. UniFi OS 3 doesn't have Podman though so I'm not running it inside a container

georgeboot · 2023-03-21T19:26:37Z

Anyone tried the upgrade from 2.x to 3.x?

pedropombeiro · 2023-03-21T23:40:34Z

Anyone tried the upgrade from 2.x to 3.x?

@georgeboot where have you seen 3.x available?

waffles0042 · 2023-03-22T00:01:19Z

@pedropombeiro , I believe @georgeboot is referring to 3.0.19, which was just made available in EA; https://community.ui.com/releases/UniFi-OS-Dream-Machines-3-0-19/aae685bb-4b96-4016-9125-29e57d7f2844

mabunixda · 2023-03-22T07:32:00Z

Yeah did the update right now ...


root@unifi-udmp:/data# dpkg -i udm-boot_1.0.6_all.deb 
Selecting previously unselected package udm-boot.
(Reading database ... 56626 files and directories currently installed.)
Preparing to unpack udm-boot_1.0.6_all.deb ...
/var/lib/dpkg/tmp.ci/preinst: 19: /sbin/ssh-proxy: not found
dpkg: error processing archive udm-boot_1.0.6_all.deb (--install):
 new udm-boot package pre-installation script subprocess returned error exit status 127
/var/lib/dpkg/tmp.ci/postrm: 24: /sbin/ssh-proxy: not found
dpkg: error while cleaning up:
 new udm-boot package post-removal script subprocess returned error exit status 127
Errors were encountered while processing:
 udm-boot_1.0.6_all.deb

Seems the ssh-proxy is also removed now... running the manuall install script runs nice :)

curl -fsL "https://raw.githubusercontent.com/unifi-utilities/unifios-utilities/HEAD/on-boot-script/remote_install.sh" | /bin/sh
  _   _ ___  __  __   ___           _
 | | | |   \|  \/  | | _ ) ___  ___| |_
 | |_| | |) | |\/| | | _ \/ _ \/ _ \  _|
  \___/|___/|_|  |_| |___/\___/\___/\__|

 Execute any script when your udm system
 starts.

UniFi Dream Machine Pro version 3.0.19 was detected
Installing on-boot script...
Removed /etc/systemd/system/multi-user.target.wants/udm-boot.service.
Creating systemctl service file
Enabling UDM boot...
Created symlink /etc/systemd/system/multi-user.target.wants/udm-boot.service → /etc/systemd/system/udm-boot.service.
Job for udm-boot.service failed because the control process exited with error code.
See "systemctl status udm-boot.service" and "journalctl -xe" for details.
UDM Boot Script installed

Downloading of CNI bridge script skipped
CNI plugins script installed
Executing CNI plugins script...
Pouring /data/.cache/cni-plugins/cni-plugins-linux-arm64-v1.2.0.tgz

Downloading of CNI bridge script skipped
CNI bridge script installed
Executing CNI bridge script...
/data/on_boot.d/06-cni-bridge.sh

On boot script installation finished

You can now place your scripts in `/data/on_boot.d`

georgeboot · 2023-03-22T07:40:08Z

@mabunixda does /data persists throughout the update? And does one need to run the installer again, or does it remain intact just like with the upgrade from 2.4 to 2.5?

mabunixda · 2023-03-22T07:43:39Z

Yes all data is still available - all my scripts and data is still available, but i had to reinstall udm package by script ...

mabunixda · 2023-03-22T08:26:21Z

The /etc/apt/sources.list is still pointing to stretch 👎

georgeboot · 2023-03-22T09:47:14Z

Heads up: podman doesn't work on 3.x! See #510

mabunixda · 2023-03-22T10:42:08Z

Yeah i try to find some solution, but i cannot use the @fabianishere kernels on the udm, because theudm-bootctl is only support 1.x as far as i have seen so far ...

dvcrn · 2023-03-23T02:16:54Z

Shall we create a 3.x thread? Unless it's similar enough to 2.x to keep it in here

Did the 3.x upgrade again wipe everything?

jherby2k · 2023-03-23T02:48:51Z

My scripts are still in /mnt/data after the 2.5 and 3.0 upgrades.

pedropombeiro · 2023-03-23T05:00:58Z

Created #523 to track 3.x issues and leave this one for 2.x.

StiviiK changed the title ~~UDM Pro 2.x~~ UniFi OS - Dream Machines 2.x Sep 22, 2022

owine mentioned this issue Dec 15, 2022

Support for UDM(P) 2.4.x #450

Closed

jinkang23 mentioned this issue Dec 16, 2022

Updated script to support UDM/UDMPro 2.x firmware #451

Merged

powellcn mentioned this issue Dec 16, 2022

Does this work on UDMP 2.4.23 peacey/split-vpn#148

Closed

KittyKatt mentioned this issue May 11, 2023

UDM Pro firmware 2.4.x podman-install script fails to download zip file #485

Closed

UniFi OS - Dream Machines 2.x #416

UniFi OS - Dream Machines 2.x #416

Comments

StiviiK commented Sep 22, 2022 • edited Loading

SamErde commented Sep 22, 2022

boostchicken commented Nov 16, 2022

Slychocobo commented Nov 16, 2022

dvcrn commented Nov 17, 2022

user45876 commented Dec 15, 2022 • edited Loading

OfficialHoSay commented Dec 15, 2022

aniolpages commented Dec 15, 2022 • edited Loading

bananaman2020 commented Dec 15, 2022

mabunixda commented Dec 15, 2022

mabunixda commented Dec 15, 2022 • edited Loading

bennettp123 commented Dec 15, 2022 • edited Loading

timrettop commented Dec 15, 2022 • edited Loading

timrettop commented Dec 16, 2022 • edited Loading

dvcrn commented Dec 16, 2022 • edited Loading

jinkang23 commented Dec 16, 2022 • edited Loading

user45876 commented Dec 16, 2022

bennettp123 commented Dec 16, 2022 • edited Loading

jinkang23 commented Dec 16, 2022

user45876 commented Dec 16, 2022 • edited Loading

dvcrn commented Dec 17, 2022

jfroy commented Dec 17, 2022

zlangbert commented Dec 19, 2022

georgeboot commented Dec 19, 2022

gatesry commented Dec 19, 2022

henessy31 commented Dec 20, 2022

dvcrn commented Dec 23, 2022

OfficialHoSay commented Feb 28, 2023 • edited Loading

pedropombeiro commented Feb 28, 2023

pedropombeiro commented Feb 28, 2023 • edited Loading

OfficialHoSay commented Feb 28, 2023 • edited Loading

dvcrn commented Mar 8, 2023 • edited Loading

dvcrn commented Mar 8, 2023

spali commented Mar 8, 2023

timrettop commented Mar 8, 2023

dvcrn commented Mar 8, 2023

bugsnatch commented Mar 14, 2023 • edited Loading

dvcrn commented Mar 14, 2023

pedropombeiro commented Mar 18, 2023

joshuaspence commented Mar 18, 2023

pedropombeiro commented Mar 18, 2023

joshuaspence commented Mar 18, 2023

pedropombeiro commented Mar 18, 2023

joshuaspence commented Mar 18, 2023

georgeboot commented Mar 21, 2023

pedropombeiro commented Mar 21, 2023

waffles0042 commented Mar 22, 2023

mabunixda commented Mar 22, 2023 • edited Loading

georgeboot commented Mar 22, 2023

mabunixda commented Mar 22, 2023

mabunixda commented Mar 22, 2023

georgeboot commented Mar 22, 2023

mabunixda commented Mar 22, 2023

dvcrn commented Mar 23, 2023

jherby2k commented Mar 23, 2023 via email

pedropombeiro commented Mar 23, 2023

StiviiK commented Sep 22, 2022 •

edited

Loading

user45876 commented Dec 15, 2022 •

edited

Loading

aniolpages commented Dec 15, 2022 •

edited

Loading

mabunixda commented Dec 15, 2022 •

edited

Loading

bennettp123 commented Dec 15, 2022 •

edited

Loading

timrettop commented Dec 15, 2022 •

edited

Loading

timrettop commented Dec 16, 2022 •

edited

Loading

dvcrn commented Dec 16, 2022 •

edited

Loading

jinkang23 commented Dec 16, 2022 •

edited

Loading

bennettp123 commented Dec 16, 2022 •

edited

Loading

user45876 commented Dec 16, 2022 •

edited

Loading

OfficialHoSay commented Feb 28, 2023 •

edited

Loading

pedropombeiro commented Feb 28, 2023 •

edited

Loading

OfficialHoSay commented Feb 28, 2023 •

edited

Loading

dvcrn commented Mar 8, 2023 •

edited

Loading

bugsnatch commented Mar 14, 2023 •

edited

Loading

mabunixda commented Mar 22, 2023 •

edited

Loading