Recent content by richardvd

For eth0 you mean? It must be, because the switch port is set to accept and send only tagged frames and it's working with the firewall disabled in 3.4-6 (and with the firewall enabled in 3.3-5). And also, all incoming and outgoing GRE packets are visible using tcpdump on vmbr0, so that rules...

eth0.1 is eth0 with VLAN tag 1, just as eth0.123 would be VLAN 123 on eth0. No problem for Linux and Netgear switches. /etc/network/interfaces: # network interface settings auto lo iface lo inet loopback iface eth0 inet manual iface eth1 inet manual auto eth2 iface eth2 inet static...

What is blocked with the firewall on: GRE packets from internet to the public IP of my pfSense VM on vtnet0 (vmbr0), and vice versa. Using tcpdump I can see on eth0.1 and vmbr0 the GRE packets coming from internet, but the packets do not arrive on vtnet0 in the pfSense VM. The GRE packets...

@avn: No, I don't think it's related to your problem. I tried to reproduce your situation. With the firewall on, I can ping from a host having eth0 linked to vmbrX (vlan N) to another host's eth0 linked to vmbrY (vlan M), with a pfSense router in between to route the two subnets. Both VMs and...

No, it still blocks GRE to/from the VM with input policy ACCEPT at the Datacenter level and the VM level.

After upgrading from 3.3-5 to 3.4-6 I can't get GRE traffic to/from pfSense VM. Other traffic (ICMP, TCP, UDP) is working fine. The firewall is disabled at the VM level, so all traffic should pass. As soon as I disable the firewall at the datacenter level, then GRE traffic to/from the VM is...

That's correct. This PoC (item 5) will crash the unpatched host process from within a Linux VM with no floppy disk configured.

Why did you replace git:// by http:// ? It is not the same. Replace your git clone line by this and try again:git clone git://git.drbd.org/drbd-8.4.git

More details please. What do you do exactly and what's the output?

These files are generated if you follow the steps indicated. You will find the .deb files in /root/drbd.

I already pointed you to the second half of this posting. If you follow these steps then it should create everything you need for drbd-8.4.3 on PVE 2.3.

Yes, for PVE 2.3 it is explained in the second half of the same posting. Just follow the steps. If you ask about 3.0, I don't know.

You can't compile drbd because of bug #285. The solution is to patch idr.h to the old content, I explained how in the thread about this bug (at posting #18).

I agree with e100's advice in posting #57. Also, I think it's a bad idea to upgrade DRBD in this unstable situation. Configuration files have changed significantly between 8.3 and 8.4, that will add to the trouble you already have.

Re: Can't compile DRBD-8.4.2 since latest PVE-2.2 update (kernel 2.6.32-82) Here is how I updated today from Proxmox VE 2.2 to 2.3, and then from drbd-8.4.2 to drbd-8.4.3. Migrate your VMs/CTs away from the current node, then start the update: aptitude update && aptitude full-upgrade...