Search results

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

hmm, just set the policy to DROP maybe? and disallow everything.. but at that point, why even connect the NIC? EDIT: Ah, because you want IPv4 only heh. Well, I'm not sure you need ipv6-icmp if you block ipv6, it's enough for me (and do not allow NDP/RA).

You could use it as outgoing filter for your typo3 instance, I'd say this is a reasonnable usecase for PMG, heh! You'd need to setup 587 port either using the firewall, or by tweaking postfix conf (setting up "submission" protocol the same way smtp is done in master.conf, for example..)

Yeah, it's a bit weird, I wonder what the 1001 user is about on some files.. What ! would do is set up a user/group on the NAS, give it permissions on the dir to be exported still on the NAS, and mapall (root included) to that user. then disable/enable the mount on the host. Unless done...

Well, if they are not detected physically, you won't see options at all here (no boot from nic, no option to set them up..).. Did lshw / dmidecode yield anything interesting?

If you really need to isolate stuff, setup a VLAN / subnet for each zone you want to isolate, and use the router to decide what gets through ?

Check in the BIOS setup that your hardware is detected there maybe? Usually you can setup PXE or some options (like.. disabling them) in the setup.. If you don't see anything in dmesg, linux probably doesn't see it at all anyway. You can still try to check dmidecode or lshw, but I'd say there...

And what does it look like inside dump after the failure? ls -al /mnt/pve/NAS_NFS/dump/ It is indeed quite weird.

Very nice, you can mark your thread as solved to signal it's a possible solution :P

extstor1, probably, it's just a security so you don't delete a datastore accidentally :P

And also, but I don't suggest doing that.. since you only have one ESP, that you don't boot on ZFS nor use secure boot, I'd just bypass proxmox-boot-tool, and use grub directly.. but well, it's there :P

The upgrade path was not too smooth there.. If you need details about all this, you can check https://pve.proxmox.com/wiki/Host_Bootloader on the wiki, btw.

Another one bites the dust.. Sorry!

well, proxmox-boot-tool here thinks it's driving systemd-boot, and so does the UEFI setup. You could re-enable it (install the tooling, then make sure it boots the proper kernel). But I'd suggest going back with GRUB if you don't need systemd-boot. You don't need to reformat, init will just...

yeah, re-init with grub using proxmox-boot-tool, as I suggested, that should do it. Or switch to UEFI entry 0007 (cue the James Bond theme..), possibly with efibootmgr, but more likely in your UEFI/BIOS setup.

OK, what about efibootmgr ? It seems that proxmox-boot-tool is not set to use grub.. so I'd say either format / init the partition (proxmox-boot-tool init /dev/disk/by-uuid/AED9-4562 grub probably), so that it gets back on grub.

Could you check the permission after that in /mnt/pve/NAS_NFS/dump/ ? It could be telling that it's not permitted because it's full as well, df -h /mnt/pve/NAS_NFS/ is alright?

Many DHCP servers allow you to specify custom codes (250 here) for a given MAC, without scripting.. you can also cheat and use info from the request in apache or nginx to match a file on the server..

Well, you can use DHCP to provide a different URL, or DNS as stated in https://pve.proxmox.com/wiki/Automated_Installation#Answer_Fetched_via_HTTP..

Well, after all those years of mounting images manually, at least I discover libguestfs-tools.. that is something... I don't really like using debian cloud img for a few opinionated choices there.. top of my head.. no LVM / all in one partition, no swap, default editor.. So, I usually use...