Recent content by dj_bobo

As always a little RTFM goes a long way. For anyone else interested here is the reference in the manual. With a little script I can define it exaclty how I want them.

Hi, So first off big shoutout to the developers, that managed to pull of what I see as the second marvel of technology, that is PBS. The first is obviously PVE. I have been toying with PBS for a few days, and love the deduplication feature, I am getting about 6X dedup rate, that is fantastic...

@wolfgang - I can confirm same issue on 4.13 and stable with 4.10 GUEST: Windows Server 1607 ( OS 14393.1715 ) vCPU: default (kvm64)

Do you have the net skills to write your own iptables rules from top to bottom ? Can you deploy a box between the world and your network and write your own rules ? If so use Proxmox Firewall, it's just a wrapper for iptables

Nice setup, It's quite easy to do what you want, how ever there are many ways So here's mine: 1. standard bridges, each bridge with it's own vlan eg vmbr10 => eth1.10 2. Trunk 3. setup like virtio0 to vmbr10, virtio1 to vmbr20.... virtio9 to vmbr 999 4. PfSense has VirtIO drivers so VirtIO...

@teerix... Had the same issue a few minutes ago... Just update the DRBD kernel module version to 8.4.10 #!/bin/bash export KVER=`uname -r` apt-get install build-essential flex apt-get install pve-headers-$KVER cd /usr/src wget http://oss.linbit.com/drbd/8.4/drbd-8.4.10-1.tar.gz tar zxvf...

I need to better understand your setup in regard to IP and subnets. by best educated guess. PVE-HOST: has one ip public IP For the Guests you have either a few directly connected IP address or a subnet routed to the PVE-host... what is your case ? But since HOST-VM network is working.. best...

It's a rather simple process of source routing, Google LARTC for full details. You have to tell the kernel that some IP's must go thru other gateway, and with other source address than the default on interface. FOR EACH IP ADDRESS OTHER THEN THE DEFAULT ip rule add from 85.xxx.154.15 lookup...

Quick idea: Make sure that your backup traffic and inter VM traffic is not going thru this dedicated network Also check (I had this) one cable was faulty and flapping, best use BOND as per Recommended_system_requirements (wiki)

Since you speak of a new block and IP: - check that OVH allows migration of that block to new host and that it dose not require manual intervention from them - you can try on the pve host to setup an Ip from that block and ping it (asuming firewall allows ping) -> If this dose not work -...