Recent content by BobhWasatch

Two IP's on the same subnet is usually a recipe for trouble. It does odd things you might not expect. What kind of software is this? Some kind of proxy? If so, it is likely expecting two different subnets so that packets can be sent between them. ETA: Depending on why you are doing this there...

So it seems to be specific to a particular Ethernet driver used by RPi4 boards. Which explains why I have never seen this problem, as my OpenWRT is running on a Celeron J1900 with Intel Ethernet. Nice find! ETA: On the other hand, the #1 cause of "temporary failure in name resolution" is a bad...

Why is managing Ubuntu remotely "troublesome" to you? Perhaps someone can help you fix that. Do you have an SSH server installed? Managing remotely by command line is much simpler than using RDP or whatever remote desktop things.

Just FYI, I have a bunch of Debian machines, both VM's and hardware, behind an OpenWRT 24.01 router, all using the router's DNS. It works fine. Whatever's wrong isn't an inherent thing in Debian or OpenWRT. I don't currently have wireguard enabled though, so that's one difference. Did you...

I think if you upgraded from an earlier version that did use syslog you might end up with leftover log files in /var/log as well.

If your use-case is to use VM's locally on your machine you might be better off with a desktop product like VirtualBox.

PVE does not install wifi support tools by default because wifi is not really suitable for this purpose. With most access points you cannot bridge multiple VM's to one wifi interface. It is not "hard", it is not possible. So you need to set up IP routing with NAT. See here for some options. If...

User space will likely be based on Debian 13 but they use Ubuntu kernels because Debian doesn't integrate ZFS.

If you are going to do a thing that isn't recommended by the people who made the software, you don't get to yell about the lack of documentation of how to do that thing. You also need to look into the actual purpose of the "nesting" feature, which isn't for what you think it is for.

Most likely Chrome is not using the DNS you expect. Is Settings>Privacy>Use Secure DNS enabled? If so, try turning it off. You might also want to look at the DNS page in chrome://net-internals and see how it is doing DNS resolution.

This is the main problem I think: cannot copy extracted data for './lib/modules/6.8.12-10-pve/kernel/net/tipc/tipc.ko' to '/lib/modules/6.8.12-10-pve/kernel/net/tipc/tipc.ko.dpkg-new': failed to write (No space left on device) You need to clean up something to make space. This will also lead...

Passing a PCI device into a VM requires that all VM memory be preallocated on startup because such devices can do DMA to or from any memory address.

Of course. If you use Kerberos+NFSv4 then you have mitigated that particular class of attack. You seemed to be saying that such attacks can't work even with traditional non-Kerberized NFS if other unspecified things are in place. You very much cannot assume that. In such a case it is "hacking...

I was responding to the specific statement you made: That is simply not true for "traditional" NFS without Kerberos. Getting root on the server is a "hacking 101" exercise, not something that is "HIGHLY speculative". It is a well-known attack! So I agree with you that if you want to use...

Not really. Traditional NFS trusts the client to provide correct information about things like the user ID (UID). One obvious attack @Johannes S slides point out is someone with root on their device creating an account with the same UID as another user. Then mount the share and su to the other...