Search results

It isn't needed and nothing is broken if you aren't using wifi. The kernel has a generic wifi layer that is separate from the card drivers and that's where the regulatory checks happen. If wifi is enabled in the kernel the generic layer gets loaded before the drivers. The fact that you have...

Besides firmware, wifi 7 is very, very, new. As in only a few months old. It could be that the iwlwifi driver in the PVE kernel doesn't support it yet. I have a Framework laptop and someone on their forum got a Qualcom card working with kernel 6.12, but 6.11 is the newest PVE kernel last I checked.

I was not able to log in to my PVE earlier. Now I can it it appears that the pve-firmware package is installed by default and conflicts with the Debian ones. I didn't realize that. In looking at your initial post, it looks like it is loading some firmware. Maybe too old? Not sure. You can get...

I should also add that the recommendation from Proxmox is to not use wifi as your primary interface. The reason is that you generally can't bridge wifi. See the relevant chapter in the PVE manual, which is linked at the top right of the PVE main screen. https://pve.proxmox.com/wiki/WLAN Here...

Have you installed firmware-iwlwifi package? ETA: On the other hand, this card must be very new as it claims to be wifi 7. You might have to get the firmware from kernel.org or Intel. It almost certainly isn't in the Debian stable packages.

PVE should do that automatically if you just use the regular shutdown command.

Not by default, no. There are DNS caching daemons you can install via apt if it really bothers you. Then you will find out the subtleties of that. It isn't as obvious as you clearly think. And the queries will still be made, they just won't go over the network. One query per two seconds on...

The problem is in your VMware configuration. I don't use VMware and so can't help you. Perhaps asking in a VMware forum "how to enable network access from the host to a VM" would be a way to get help.

Debian (and Ubuntu) have a thing called DKMS to semi-automate the process, including upgrades. Vendors need to support it though, it can't work with random vendor-provided scripts. Also, there are still occasional issues that you have with any out-of-tree drivers, namely that the kernel...

So DNS is working and routing is working. Which leaves a firewall somewhere that blocks UDP port 123 either inbound or outbound. ETA: Sometimes, especially on corporate networks, the firewall is set up to be an NTP server and blocks use of external servers.

Make a backup and then restore it to the new array.

The next thing I'd try is to clear all site cookies and cache for the PVE host in your browser.

So what's your point? That the installer should be changed? Maybe you are right but that does not help you today. Again I suggest installing on top of Debian. I don't use PBS but if it works anything like PVE it can be installed that way. Worst case you could install it to a container on a...

The "reach" field in the "chronyc sources" output is one byte in octal. A bit is set each time a response is received. So if it says 377, that means it got a reply for the last 8 queries. Having it be zero means that it is not receiving replies at all. This in turn could be caused by a number of...

Check the time on the client machine you are using.

Like I said, it depends on the context. It isn't clear to me whether the OP is using a web form or the API or the command line or what.

It isn't clear to me, but you seem to be running PVE inside of another virtualization. Is that correct? In that case you need to pay special attention to how the network is set up on the host side. For example, Virtualbox defaults to NAT, which means the host can't access the VM directly but the...

Likewise, he also asked for the IP of the workstation you are trying to browse from. You said "ipconfig /all" did not work. What operating system do you use? ETA: It appears from what you posted that the PVE web server is running and serving the main page and the Ethernet port is up. That means...

It said "could not resolve host LAN_IP". The only way to get that response is to have put, literally, LAN_IP, as the target of the curl command because IP addresses don't need resolving and so can't give that error. You should instead substitute your machine's real IP (e.g 192.168.1.3).

Depending on the context where you're using the password it may need to be in single quotes ('xxxx$$xxxx') or be escaped (xxx\$\$xxx).