Search results

Erstes Terminal: watch -n 10 xtightvncviewer localhost & ---- Hetzner Webinterface Rescue System starten Zweites Terminal: scp ISO/proxmox-ve_8.1-1.iso RESCUE: ssh RESCUE -L 5900:127.1:5900 altnames der Netzwerkinterfaces ermitteln: ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc...

1. ping 8.8.8.8 from your container 2. on the host check with tcpdump -ni vmbr0 icmp if you see the packets 3. check if you see the packets on your external interface with tcpdump -ni enp1s0 icmp for the outgoing packets, the sender address should be changed to 192.168.178.126 by the masquerade...

Please post your /etc/network/interfaces Bridges in proxmox must be named vmbrX

ok, ipcalc 63.141.251.170/29 Address: 63.141.251.170 00111111.10001101.11111011.10101 010 Netmask: 255.255.255.248 = 29 11111111.11111111.11111111.11111 000 Wildcard: 0.0.0.7 00000000.00000000.00000000.00000 111 => Network: 63.141.251.168/29...

The subnet entry is: Subnet: 63.141.251.170/29 see above

The subnet is the first IP in your range, the broadcast is the last. The subnet mask can either be written /29 (CIDR Notation) or 255.255.255.248

I assume 63.141.251.171 is the gateway, 172 is your proxmox host, so your VM will have to be the next free IP 173: Subnet: 63.141.251.170/29 Address: 63.141.251.173/29 Gateway: 63.141.251.171 Nameserver: 8.8.8.8 or 1.1.1.1 or 9.9.9.9

Do a static IP configuration in your vm

Sounds good So inside your VM configure another of your IPs. Ping 8.8.8.8 Do tcpdump -ni vmbr0 icmp on your host, you should see the ICMP echo request and reply packets. tcpdump -ni enp3s0 icmp should show the same, these are the packets leaving/entering your system

Does your proxmox host have an IP in that range? Can you ping the default gw and 8.8.8.8 (Google nameserver) Is that IP on your vmbr interface? brctl show should show your vmbr0 bridge interface, please post your /etc/network/interfaces Are you allowed to have additional Mac addresses...

Tell us more about your setup. I suppose you have a proxmox server in a server hosting somewhere and a /29 network with a gateway from your provider, like 188.16.12.0/29. In this example 188.16.12.1 would be your gateway, 2-6 your 5 ips.

ZFS is a complex beast but there is documentation. ;) Your disks are in one (or more) pools, in that pool you have volumes (filesystems) and blockdevices (zvols) in case of your dead proxmox server, you just set up a new one, attach your proxmox backup server and restore your vms and...

Der Vorteil von topgrade ist dass es nicht nur die apt pakete updated, sondern auch flatpak, snap, rust etc. Allerding sind auf einem Proxmox host diese normal nicht installiert

Output of ceph -s ? Do you still need this vm 102? You should be able to move the file 102.con from the deletet host to another host: mv /etc/pve/nodes/host-deleted/qemu-server/102.conf /etc/pve/nodes/host-still-existing/qemu-server/102.conf Then try deleting /etc/pve/nodes/host-deleted/

zpool import ... -R /new/path/to/mount/under

Optional syslog, journald default sounds good

Kurze Antwort: Nein Längere Antwort: Das manipulierte Paket ist nur in Debian testing / unstable gewesen, NICHT in stable

grep -ris enterprise /etc/apt should show you the file and line, just add a # in front of it

Just comment out the enterprise repository line in your sources

Can i whitelist a sender for clamav scans instead of spamassassin, if so , how?