Thanks, I misunderstood the usage of /24. I thought in order to export to a whole subnet, I had to put the subnet address 192.168.0.0/24 while 192.168.0.20/24 would imply a single client within that subnet. I removed the prefix length entirely as CallMeAl suggested, so that’s sorted out.
There’s another issue remaining, see my reply to Al’s comment if you’d like.
Thank you. I’m closer to what I want now. Can you help me explain this behavior though:
For testing purposes, I commented out every line in /etc/exports but these:
/srv/nfsv4 192.168.0.10(ro,sync,secure,root_squash,subtree_check,fsid=0) \
192.168.0.20(ro,sync,secure,root_squash,subtree_check,fsid=0)
Client 192.168.0.20 can mount nfs-server:/ and listing the contents gives both directories foo and bar. It cannot see the contents of foo, as intended, but it can see what’s inside bar (EDIT: it can see down one level, so the subdirectories of bar, but nothing further down). I cannot figure out why? I rebooted the machine in hopes it was just a caching thing, to no avail.
Apart from that, I was hoping 192.168.0.20 could not even mount foo, but as long as its contents are hidden, I can live with that for now.
Non-sysadmin here, I could only find some generic info on ISO 27002/27001, what does it say about containerized applications?
Someone posted this in another thread and I was surprised to see how many well-known projects were listed among them
Worth noting that cards such as this (with mote than one M.2 slot) require the mainboard to support PCIe bifurcation – which most old boards likely do not.
Edit: Cards with just one slot do not require this feature so you can plug them into any board that has a free PCIe slot. Unless you also want to boot from them, in which case you might need to modify your UEFI. I went that route and succeeded, but be aware of the risks involved.
I’ve actually been working my way through the proxmox-on-top-of-debian guide recently, but after installing the proxmox-ve kernel and rebooting, I was left with SSH disabled (connection refused) and no local console (more precisely no monitor output past “loading initial ramdisk”). I have so little time on my hands that troubleshooting is sometimes taking the fun out of it. Probably just going to re-install using the Proxmox ISO.
You seem like the right person to ask this:
What route do I go if I want to up my admin slowly so I eventually feel able to run pure Debian? Currently running Docker on Unraid with two minor VMs but looking to migrate away from Unraid with the intention to only run FOSS (and get a deeper understanding of everything under the hood).
I know that’s little information, all I need is a nudge in the right direction so I can figure things out by consulting documentation and forums.
Even with bar exported to this client, it cannot see its subdirectories’ contents. What the hell is going on? Just to be clear, I did run
exportfs -arvafter every change to /etc/exports.