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...
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...
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
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.
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...
No. A new PVE-kernel was released recently (2.6.32-83), where the idr.h file was touched but not changed.
In the meanwhile, if you want to compile a new drbd, you have to re-insert in /usr/src/linux/include/linux/idr.h the four missing lines of code that were removed by this bug.
Re: Can't compile DRBD-8.4.2 since latest PVE-2.2 update (kernel 2.6.32-82)
To answer myself, the error of 'module-assistant -l 2.6.32-16-pve auto-install drbd8':
/usr/src/modules/drbd/drbd/compat/idr.c:16: error: ‘MAX_LEVEL’ undeclared (first use in this function)
...was caused by this change...
Re: Can't compile DRBD-8.4.2 since latest PVE-2.2 update (kernel 2.6.32-82)
This is the output of 'module-assistant -l 2.6.32-16-pve auto-install drbd8' on the latest kernel (2.6.32-82), this comes from the build logs that are saved in /var/cache/modass:
dpatch deapply-all
rm -rf patch-stamp...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.