Search results

I know you're not in France, because you missed HDS and SecNumCloud hahaha... Generally, as pointed out, assume this is a Linux system, and apply whatever recommendations that are required, but basically, there's is not much that Proxmox themselves can do to "earn" those qualifications, it's...

You can also set it up as ZFS if you plan on using replication at some point, but if you plan on staying on a single node.. Thin LVM is the way to go!

So, easiest is indeed set up a LVM PV/VG on that raid6 device (it should appear in the Disks section of the Host settings), and create a Thin LV on top of it, and enjoy thin provisioning, snapshots, and all.

I'm guessing you run a single node setup then, with the RAID6 on it ? Just make the RAID6 a LVM pv, to host a lvmthin volume for your VMs if so, I guess you could even do it fully in the UI :P

Heh, well, if that works.. then, problem solved :P I'm surprised it sees the boot option but doesn't allow you to set it.. OVH had some servers that would reset the boot order also without asking.. anyway, now you know a bit more about UEFI and GRUB, heh!

Aw, I thought you meant the MAC for the VM/CT on the vnet, not the bridge itself, sorry.. and it could be interesting for any type of bridge then no?

If curl can access it, and not your browser, your browser is at fault. Are you sure you try to reach https and not using http? I hate those browsers hiding the scheme by default in the URL.. you can also display the details of the request to see. But I'd say you're trying to connect using http...

Then you're good, hit https://192.168.2.2:8006 in your browser :P

Try what @Onslow says. check the layer 1, cable, WiFi.. then make sure you don't have a VLAN set on the switch, and that you can reach your router from the PC. Does the PC has a firewall? :P probably seeing ip a ; ip r ; ip n on the PC will tell you what you need for troubleshooting. Make sure...

This is confusing.. and probably not in the good part of the forum. Why would you want to use the ssd from your home computer? Proxmox VE can use both your disks, the system itself is quite small (you could give it 50 GB in your setup), then use thin-lvm or zfs to store your VMs disks on the...

I'm not sure why you go for dual boot there, and not just use a different VMs, imaged with each OS? To have a single FOG procedure for users? In the physical world, that may make sense to avoid redeploying to switch between OS, but on a VM? Also, FOG (or clonezilla) is fine, but you'd probably...

Can't you actually set the proxmox option there in the Setup? You can maybe change the entry, or just map BOOTX64.EFI to grubx64.efi in proxmox.. maybe proxmox-boot-tool (and its --grub option) can do it for you..

I really think we need either generally allowing disabling link-local on an interface, or simply deny any IP configuration on the SDN bridges.. or a bit nicer, being able mark it for VM traffic only. This bug is not good on default setup btw.. This allows for so many kind of attacks on hosts...

The firewall way works for the underlying bridge.. but it seems that by default vnets allow that traffic (set up using SDN), which to me, is a bug, I'll investigate.. EDIT: Yes.. damned. I'll open a bug but if you have firewall on, on a host, link local is blocked from a bridge set directly on...

There is a bug discussion here, that do not fix it but discusses options: https://bugzilla.proxmox.com/show_bug.cgi?id=1251 Another one, with mostly opinions, and the same idea I gave, use ifupdown2 and an up script: https://bugzilla.proxmox.com/show_bug.cgi?id=4538

You can use the firewall to restrict those access to the host as it is, no code, no edit :P But it's true it could be disabled using ifupdown2, so that interfaces with something like "enable (or disable) link local v6" have the appropriate sysctl set. Go and patch it. And it could be...

The Wiki gives you keys heh, use a debian live CD or a rescue shell.. you can try efibootmgr -n 0000 to avoid the 0003 entry that is probably unhappy.  If that works, well, set the boot order to start with the proxmox entry. If it fails, mount your system disks, and at least root and...

you can logrotate / delete it, but you'll lose track of people trying to get to your server.. however, I'm guessing this is urgent, but maybe try to back it up before deleting it. I'd suggest setting up a firewall to restrict who can connect using SSH (If this is a proxmox host, which I guess...

Well, unless you actually restore a backup, it won't leave the cluster, that's quite a given. But a NIC can easily be replugged to another bridge.. I guess if it's more of a marker, and if you make sure you don't reconfigure the NIC it's fine, but there are many cases where you'd change that...

Not that I know of, maybe room for a contribution here.. However, technically, the MAC is linked to the VM/CT, not to the network it's hooked on, so that may not be a reasonable feature. Imagine a NIC whose MAC would change depending on the switch it's plugged in, I'd be unhappy :P