mikegeezy

On version 6.8.3, I'm trying to follow the instructions here to add a symlink for a Wyzesense USB dongle: https://github.com/kevinvincent/ha-wyzesense/issues/66 Anything that I do in the /etc/udev/rules.d/ folder does not survive a reboot. I feel like the right thing to do is something on the flash drive similar to what I had to do for RSYNC I'm not confident enough to go mashing around there. Can anyone please advise on the correct approach here? Thank you

Has anyone gotten nvidia GPU working with this container? Mine's showing up in the logs but not getting loaded according to nvidia-smi. rdpRRGetInfo: 20-Mar-2020 14:07:25 [---] CUDA: NVIDIA GPU 0: P106-090 (driver version 440.59, CUDA version 10.2, compute capability 6.1, 3022MB, 2972MB available, 1960 GFLOPS peak)

I was using an Ubuntu VM to root my Xiaomi vacuum. I passed a USB wifi adapter to the VM so that I could connect to the vacuum AP. Then I connected my desktop to the same AP, SSH'd back into the VM and disabled the virtual ethernet interface ( ens1p0 I think) using ifconfig down. I tried to bring it back up while still connected through SSH, but it said it couldn't find it. So I rebooted the VM thinking I'll just drop back to the normal LAN, start the VM and everything will be fine. Now, I can't even access the WebUI. How is that possible? Disabling a network interface in a VM appears to have taken the network interface down on the host as well. Any suggestions on how to get it back up?

I like how helpful and responsive the whole community is. Great thing to be a part of. In 2020 I would like to see a hardened web GUI that we can feel comfortable opening up to the internet (maybe with yubikey support?)

So, it appears if you upgrade to 6.8, you'll need to change your /boot/config/go script to say: bash /boot/custom/etc/rc.d/S20-init.rsyncd

@cybrnook My dude thanks very much for the post, that got it going! The hangup on my end was the firewall rule, once I put that in place the unRAID box connected immediately. Synology didn't connect right off the bat, so I started digging around in /usr/syno/etc/ups and realized there are configuration options that aren't really exposed in the control panel GUI (like the UPS name) Clever trick to setup pfSense with what Synology is looking for. Above comment makes more sense to me now. All this had me scratching my head on why it wouldn't connect without the firewall rule, so I went back and added a LISTEN 192.168.1.1 to upsd.conf. And that appears to be working with the firewall rule disabled.

@cybrnook can you please explain the steps required to setup NUT on pfsense? I've got NUT running just fine and talking to the UPS, but I can't manage to get unRAID to connect as a client. I've added a slave user to upsd.users. I was thinking maybe it needs a LISTEN directive to allow an incoming connection from unRAID, but that just breaks the connection between pfSENSE NUT <-> UPS. I was thinking it needs a MODE=netserver in nut.conf, but seems I'm missing a step there. I would love get them talking, seems like I'm overlooking something simple. If you've got the Synology connection working too, I would love to see that as well. Seems like that needs to be routed through SNMP? THANKS

Yes, that's probably the case. I'll have to check when I get home. Although, it seems like there's not a real advantage to using the cache here. Thanks for the feedback fellas. I'm new to unRAID / the community, good to know it's so supportive.

Folks just want to make a public service announcement here for Synology Hyper Backup users (and maybe other source clients?). If your unRAID backup target share is set to use the cache drive, and your cache is smaller than the backup size, you're going to have a bad time. I'm a bit of an unRAID noob, so I beat my head against the wall with this one for like weeks. I tried running rsync in a docker. I tried spinning up a VM. The logs on both end were pretty much useless. I was able to establish the connection and start the backup, but eventually it would always fail and the rsync daemon process would evaporate. I just happened to browse the cache drive and see the backup stuff stacking up there, and wondered why that was. Once I turned off cache for that share, it worked flawlessly. Can anyone comment on potential workarounds to be able to utilize the cache drive in this scenario?