WashingtonMatt

Please keep it in CA. I plan to continue using it until the the iOS app is no longer supported, or if I need support for a new camera at some point.

Looks like the plug has been officially pulled. Overall the impact isn't too bad for me. I run WireGuard and openvpn on an edgerouter. Guess I'll just ride that ship for now. I wonder if they'll yank app support?

So login is still working, thought maybe we dodged the bullet, then I found the update below. Frustrating... nice while it lasted. Please keep the docker available since it will still work fine with local/vpn login.

No issues updating to 3.10.12

I updated from 3.10.10 to 3.10.11 a couple days ago as well, no issues.

My upgrade to 6.8.1 was successful. Idle CPU use seems to have returned to normal. RX570 passthrough performance seems to be back to normal, I had been assuming performance issues were due to a driver update.

I've noticed a few items failing to pull metadata automatically. I didn't make a connection to unRAID, but in hindsight it did start around 6.8.0 upgrade as well as other minor SMB issues. I haven't upgraded to 6.8.1 yet.

I started having this issue on 6.8.0 with a Ubuntu VM with multiple cifs mounts. Adding "vers=v1.0" seems to have cleared it up. Not the preferred solution though...

Okay I'm happy to report that i440fx/seabios is working for 11.3+. I swear I tested the installer ISOs, but I must have only tested i440fx with an existing install, not realizing GPT partition scheme is not compatible. Converting to MBR looks possible, but risky. My FreeBSD VM runs headless, so I'm not sure what the i440fx passthrough implications are. Official patches are on the way for Q35/OVFM.

More progress on the FreeBSD side. Patch attached in bug report. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241774#c35 It really sounds like i440fx should be working on unRAID...

Great! We're making progress.

After the reboot, you have to configure DHCP uname -a FreeBSD cylon12 12.1-RELEASE FreeBSD 12.1-RELEASE GENERIC amd64

I believe the alias was added when I added a second e1000 interface for troubleshooting. It should work. At this point all I can recommend is start over and apply first patch and kernel without Netmap. <interface type='bridge'> <mac address='52:54:00:70:6f:f4'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <interface type='bridge'> <mac addres

I have not tried the second patch, so my kernel is without NETMAP. Since networking is not configured during setup, you do have to manually set it up after the custom kernel is installed. <interface type='bridge'> <mac address='52:54:00:70:6f:f4'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> vtpcim0@pci0:1:0:0: class=0x020000 card=0x11001af4 chip=0x10411af4 rev=0

Did you configure DHCP, or set up IP address? What's output of ifconfig and pciconf -lv ?