First thing I’d do is to look at the client (fedora) journal for anything funky happening.

‘sudo systemctl status nfs-client’

Since it’s random I assume you won’t have any timeout in your /etc/fstab but it might be worth taking a look anyway.

Be aware that if the network drops the NFS will be disconnected and won’t auto-reconnect so this could also be the issue.

I don’t know if it plays well with container mounted volume, but looking at autofs could be a solution to auto-remount the share. I use it profusely for network mounted home directories.

tragically short life

That’s just all dogs and it’s up there in the list of the saddest part of life. It’s always living with the fact that yesterday he was a puppy and tomorrow you’ll have to say goodbye, but today, today is the best day of all.

Another is because for a decentralized ownership service to hold any ground it must be either backed by a (centralized) court of law or hold the full service you’re buying. Otherwise what’s stopping a hosting platform to remove the service you bought with your nft from their platform?

Distractible (if you already follow Markiplier, muyskerm or lordminion777)

Girls who don’t DND (a refreshing take on DND from people who take it with humour, highly entertaining)

Even in bridge mode you can still be slowed down by the modem if its CPU can’t handle your traffic. That’s unless the isp modem offer a complete passthrough. That’s what was happening to me even in bridge mode where I was getting my own IP through pppoe. The modem couldn’t be made into full passthrough and was hitting 100% CPU.

Bridge mode still means you go through their hardware. I had issues with my ISP modem because even if it was in bridge mode I was basically ddos-ing it with my usage.

In the end I got an sfp module that mimick being the modem and plugged the ISP fiber right into my opnsense box where the CPU was plenty.