Search results

  1. thommie

    Proxmox claiming MAC address

    I will test this on Hetzner, but would like to see a reply from proxmox staff on this ...
  2. thommie

    Proxmox claiming MAC address

    The issue is not solved yet, even not with root@tokoeka ~ # pveversion pve-manager/7.0-11/63d82f4e (running kernel: 5.11.22-4-pve) Today I received a new abuse complaint from Hetzner again for Proxmox using "diced MACs" which are unknown to the Hetzner robot. @proxmox staff: any comment...
  3. thommie

    PVE upgrade 6.4 > 7 network completely down

    See also https://forum.proxmox.com/threads/proxmox-claiming-mac-address.52601/ for reference - this was the reason for the PVE update. In my case, I had to solve MAC abuse complaints from Hetzner with updating to iproute2 first and then switch from PVE 6.4 to 7 and debian 11. Hetzner confirmed...
  4. thommie

    Proxmox claiming MAC address

    In my case the update to Debian Bullseye 11 and PVE 7.0.11 is now finished. According to Hetzner staff the MAC problem is solved. Would be nice if we can see a statement from proxmox guys here. This bug is causing big trouble when using PVE 6.x in a hosted environment.
  5. thommie

    Proxmox claiming MAC address

    I ran into an ugly problem during upgrade PVE 6.4 > 7 and following https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0, I first upgraded ifupdown >> ifupdown2 on the 6.4 and debian 10. The package update failed somehow which resulted in an inaccessible server. The whole networking including...
  6. thommie

    PVE upgrade 6.4 > 7 network completely down

    I am in the middle of upgrading PVE to 7.0 and - while still on 6.4. - I have no more network connection after a reboot. The primary network device is down (and therefore also the vm bridges) and it is impossible to activate it manually with ifup ifup fails too I am trying to fix this with...
  7. thommie

    Proxmox claiming MAC address

    @proxmox Team: aside from the workarounds presented here: doesnt't this qualify for a general solution (patch) in PVE as there are a number of affected customers with running PVE servers on Hetzner? I am surprised that this thread dates back to 2019 and there still is no "real" solution (at...
  8. thommie

    pve 6.4 crashing frequently with e1000e "Detected Hardware Unit Hang"

    Good morning, our PVE 6.4-13 with kernel 5.4.128-1-pve crashes unplanned every few days with the following error msg: Sep 01 01:55:42 tokoeka sshd[2837222]: Disconnected from invalid user developer 162.243.91.84 port 48918 [preauth] Sep 01 01:55:55 tokoeka sshd[2837252]: rexec line 24...
  9. thommie

    Detected Hardware Unit Hang: NIC resetting unexpectedly during high throughput

    I also saw this Hardware Unit Hang in the last few days, although I have kernel 5.4.128-1 on my PVE server. Just to get a clear picture of the status now: As I understand, this issue was fixed in current 5.x kernels. The "downgrade" on the NIC ("ethtool -K <interface> tso off gso off" for...
  10. thommie

    PVE 6.4: lxc masquerading from private to public net on ipv4 and ipv6

    Hi, I have lxc containers which shall only have an internal networking connection (on vmbr1 = private 10.010.10.x network). The PVE host has a masquerading rule to allow updating/installation jobs for the inernal lxc containers. For the ipv4 masquerading I followed this info...
  11. thommie

    udp port blocking is not working

    I disabled all firewall settings on vm level, node level, datacenter level through web UI and re-enabled them. iptables-save shows the same result. root@tokoeka ~ # iptables-save # Generated by iptables-save v1.8.2 on Tue Jun 23 11:40:43 2020 *filter :INPUT ACCEPT [393993755:32834110527]...
  12. thommie

    udp port blocking is not working

    Hm, ups, nothing: root@tokoeka /etc/pve/qemu-server # iptables-save | grep tap102 root@tokoeka /etc/pve/qemu-server # and un-grepped: root@tokoeka /etc/pve/qemu-server # iptables-save # Generated by iptables-save v1.8.2 on Mon Jun 22 14:40:24 2020 *filter :INPUT ACCEPT...
  13. thommie

    udp port blocking is not working

    Datacenter: "Firewall: Yes" Node: Firewall: yes VM: Firewall yes net0, firewall=1 VM config: agent: 1 bootdisk: scsi0 cores: 2 ide2: none,media=cdrom memory: 2048 name: idp3 net0: virtio=00:50:56:00:2B:66,bridge=vmbr0,firewall=1 net1: e1000=FE:DD:91:12:4D:47,bridge=vmbr1,firewall=1 numa: 0...
  14. thommie

    udp port blocking is not working

    Hi, I have a problem with abuse messages from hetzner on behalf of the german BSI for my root server with proxmox PCE 6.2.4. On one of the kvm VMs there is an univention installation with open ports on udp 111 which are known to be misused if they are public. I created a firewall rule for this...
  15. thommie

    Extracting data from *.vma file

    Thx, yes, I already managed this, its just a raw file which needs a loop device for mounting. Bye, Thommie
  16. thommie

    Extracting data from *.vma file

    Hi, I have a de-compressed dump file (*.vma decompressed from *.lzo) with 250 GB and want to extract all contents of the /var/www directory selectively from the main drive of this VM (drive-scsi0). I can not find any documentation to handle this with the vma cli tool. So, what is the correct...
  17. thommie

    sockets or virtual cpus?

    Hi together, this may have been asked many times before, sorry: I want to switch from a free PVE installation to a paid one, as this fine software is worth it ;-). On my data center root server I have CPU(s) 8 x Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (1 Socket) Kernel Version Linux...
  18. thommie

    change LXC from unprivileged back to privileged

    Hi Thomas, ok, thanks, the CT runs for some time and I simply don't know if there was some manual manipulation before. There was a mixture of "standard" UIDs and mapped UIDs from namespaces in /va/log/, /cache /lib. Deletion of the "old style" temp files helped, backup is successful now.
  19. thommie

    change LXC from unprivileged back to privileged

    The problem is, that I can not even create the initial backup. In both snapshot and "stop" backup modes, I get the following errors: INFO: starting new backup job: vzdump 106 --mode stop --compress gzip --remove 0 --node tokoeka --storage storagebox_191707 INFO: filesystem type on dumpdir is...