Search results

kernel 5.0.21-1-pve Cluster 4 identical nodes, 2 network cards each all fresh installs pve6 network cards driver: ixgbe version: 5.1.0-k firmware-version: 0x80000aee, 1.1927.0 expansion-rom-version: bus-info: 0000:03:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes...

while 1 € is still extortion, the mean thing is those are bound to the host, and failoverips costs you 5€ a month. and you need to buy them seperatly because a fialover network can only be switched together. and to compare that ovh ip cost you 2€once no monthly. so if you need a lot of public...

its not strange, its just another way todo it. it should not make any difference either way

JUST FYI I had such issues before but they are not related to ZFS or the disk itself. Instead its NFS and kernel. heres what happend: nfs was mounted via automount. one of the nfs shares gone byebye but forgot to disable automount. host suddenly dropped its i/o and troughput of the harddisks...

had same thing on a cluster @ovh. vrack is used for corosync only. what happens is that one host suddely decided to go for a lower mtu while i was trying to get this host back into that cluster it was the other way around i had to restart corosync on all the other nodes, after restart they...

for hetzner i use a NAT setup. outgoing and incomming nat port mappings done with fwbuilder. resons for this is: moving VMs to another server requires manual intervention anyway except you pay an extra premium for an failoverip your ips are bound to the host. that can have major implications...

uhm what? what do you mean exactly you added those mac adress es on the vmlevel? you need to add the VMs mac adresses in hetzners robot. take one of the assigned ips an ad the corresponding mac adress to this ip. public ip on the vm need to match with the mac of the vm in hetzners portal...

even this started ages ago, since the last is from aprili think ill join the party. had this today on pve 6 3 node cluster, node 1 was sending lot of migration data to node 3. while in the middle of the migration i had the great idea to migrate an emtpy template (basically just a machine...

please update the guide for seperation of the clusternetwork and express that this is only till version 6 its really confusing as a example: this thread :)

BUMP Setting MTU can be more useful than just hetzner. Leaving this to the guest is pretty unclean. Looks like Mr. Dietmar reject this https://pve.proxmox.com/pipermail/pve-devel/2018-August/033558.html As he dislikes device specific options. That makes no sense. While i can see where he is...

panclaws solution does work but only with 2 disk max. this is because qemus default is IDE and well 4devices are max there (good old times) if you need mroe disks use this qemu-system-x86_64 -enable-kvm -m 4096 -cpu host -smp 8 \ -drive...

uhh btw, it would be nice if that behaviour was documented in the firewall section. i suspected that after seeing the new virtual bridges comming up,.. still wasnt shure because i could not find it in big red warning letters in the documentation :) also in networking a hin at nat section to not...

isnt there a way tp have those pairs beeing persistent? i mean that practically means the firewall option in promox is useless for windows guests yea yea yea,.. i feared something like that so firewall is also not useable with nat then ? besides would be nice to have nat as an firewall...

why would promos has an answer? you already said ubuntu 18 even on a physical machine has that issue. debians dont even as a vm. so my best guess is its ubuntu. maybe something with the default networking/driver whatever. maybe offload issue or some qos service? wouldnt be a big shock, i mean...

Wierd issue. Networkconfig eth0 with publicip vmbr0 with internal for VM natting - outgoing traffic only firewallconfig - block all incomming except openvpn to the host Now to the wierd part. if i activate the firewall on datacenter level and reboot a 2012r2 VM the VM detects a new...

then you may wanna read what OVS can do. when you create a bridge its basically a stupid switch, that kinda supports vlan and thats about it. OVS is kinda a smart switch that let you isolate certain ports, port mirror,qos, and so on. i woudl actually love to see OVS nativly implemented into...

bridges and vlans are not the same if you create 2 bridges you have 2 independent lans (virtually but thats still not a vlan) now you can assign different vlan id´s to each interface. now you have vlans, only interfaces with the same vlan id can reach each other on ethernet level. however...

ur shure about this ? i do nothing iwth lcx at all but a regular linux you can set a tun as a static interface in interfaces like auto tun0 iface tun0 inet static address 192.168.15.1 netmask 255.255.255.255 network...

pfsense is just fine. virtualpf is a fork 4 years old doesnt look that mature compared to pf sense with its massive active development. that said whats exactly the config of your pf sense? you have only one nic on the kvm host? how did you configure wan and lan interface on the pfsense? where...

be warned, if you close now promox ports to the outside (why else woudl you use vpn) then you have the chicken egg problem when doing upgrades and such if you do so install anohter openvpn on the host as an emergency access too and close promos to the outside world