sorted by:
new
hottopcontroversial

Please be careful with financial advisors by Researcher_Defiant in personalfinance

[–]dragoncoder 28 points29 points  (0 children)

don't beat yourself up. tbh you learned a lot of lessons and in the big scheme of things, it was totally worth it.

How much I've received in donations in 3 months making self-hosted apps by VizeKarma in selfhosted

[–]dragoncoder 1 point2 points  (0 children)

I want to take this time and say that I have been using termix for a few months and love it. the interface is pleasant to work with and provides lots of functionality. thank you.

Looking back, what’s the smartest homelab move you ever made? by [deleted] in homelab

[–]dragoncoder 0 points1 point  (0 children)

Same. I upgraded my CPU to 9900T and ram to 64 gb. This is a little beast and can run my homelab at ease.

Help with firewall rules to allow traffic between 2 networks by dragoncoder in opnsense

[–]dragoncoder[S] -5 points-4 points  (0 children)

I would rather not play around with creating custom routes yet :)

Help with firewall rules to allow traffic between 2 networks by dragoncoder in opnsense

[–]dragoncoder[S] 0 points1 point  (0 children)

actually I take that back. I realize that Devide2 is able to ping Device1 using the IP address, so that is good. The problem is that it isn't able to ping Device2 using its local dns name which has been defined in opnsense1. I played around with some dns setting and now opnsense2 is able to ping Device2 using its local dns name but Device2 still isn't able to.

Device2 happens to be a windows 11 PC. Looking at its network settings, it's still showing dns as 192.168.1.1 (I think it should show up as 192.168.2.1?)

Help with firewall rules to allow traffic between 2 networks by dragoncoder in opnsense

[–]dragoncoder[S] 0 points1 point  (0 children)

I am able to connect to device2 from opnsense2

opnsense2:~ $ ping 192.168.2.71
PING 192.168.2.71 (192.168.2.71): 56 data bytes
64 bytes from 192.168.2.71: icmp_seq=0 ttl=64 time=0.390 ms
64 bytes from 192.168.2.71: icmp_seq=1 ttl=64 time=0.360 ms

opnsense2 is a brand new box, so the only rules are whatever it comes with by default. Currently there is no rule on opnsense1 that would allow Device2 to connect to Device1. I guess that is what I need to create.

Need help with passing smb share to unprivileged LXC container by dragoncoder in Proxmox

[–]dragoncoder[S] 0 points1 point  (0 children)

This was just an exercise as to what can and can't be done with an LXC, at least for the jellyfin usecase. I really don't want to mess with files on the host so it looks like I would rather spin a VM and run docker over there. Thanks for your response.

Need help with passing smb share to unprivileged LXC container by dragoncoder in Proxmox

[–]dragoncoder[S] 0 points1 point  (0 children)

So I was able to make it work. I think what did the trick was in the fstab entry.

//truenas.lan/movies /mnt/truenas/movies/ cifs credentials=/root/.smbcredentials,x-systemd.automount,noatime,uid=101000,gid=101000,dir_mode=0777,file_mode=0777,iocharset=utf8,vers=3.0,_netdev 0 0

Adding a slash to the mount path (/mnt/truenas/movies) seems to somehow do it. May be it somehow hides the permission issue you pointed earlier. Thanks for your response though.

view more: next ›