Search results

  1. F

    firewall enabled in datacenter prevent bridge VM comunication on the same node

    After analysing traffic between the two VM with firewall in datacenter ON ( 'enable: 1' in cluster.fw) I can tell the followings: - icmp trafic is OK, each VM respond to ping from the other VM - UDP trafic is OK (tested with netcat from both VM) - the problem appear with TCP traffic that is...
  2. F

    firewall enabled in datacenter prevent bridge VM comunication on the same node

    In my network I have a physical router, separated from the proxmox cluster (and also a physical switch with vlan support). So the route would be: proxmox node1: VM1 eth0 'vmbr1 tag 16' (192.168.16.10 in vlan 16) -> physical switch port (with vlan support) -> physical router interfaces...
  3. F

    firewall enabled in datacenter prevent bridge VM comunication on the same node

    Of course I have a router in my network. The problem is that the two VM can comunicate when the firewall is OFF in Datacenter -> Firewall -> Options, but when I enable the firewall the communication stop and I'm unable to set some firewall rules to reenable this commnuication (as i told you...
  4. F

    firewall enabled in datacenter prevent bridge VM comunication on the same node

    And forgot to mention that I can't enable communication between the two VM even if I configure 'Input Policy' and 'Output Policy' to Enable in Datacenter (if firewall is on in Datacenter, and VMs firewall and node firewall is off). Regards, Florin
  5. F

    firewall enabled in datacenter prevent bridge VM comunication on the same node

    I changed now the vlan on network interfaces (the standard way) but the problem still remain. Now I have on network: # network interface settings auto lo iface lo inet loopback iface eth0 inet manual iface eth1 inet manual auto eth2 iface eth2 inet static address 172.19.0.52...
  6. F

    firewall enabled in datacenter prevent bridge VM comunication on the same node

    Hi Dietmar, Sure, here are network configuration: # network interface settings auto lo iface lo inet loopback iface eth0 inet manual iface eth1 inet manual auto eth2 iface eth2 inet static address 172.19.0.52 netmask 255.255.255.0 auto eth3 iface eth3 inet static address...
  7. F

    firewall enabled in datacenter prevent bridge VM comunication on the same node

    While testing new firewall in proxmox 3.4 I encountered the following problem: when I enable firewall (in datacenter) two kvm VM that are on the same proxmox node but eth0 on each is connected to vmbr16 respectively vmbr172 can no longer communicate. vmbr16 is a bridge to eth1 (vlan 16) and...
  8. F

    Serial over Lan Hangs boot until keypress on console

    Hi, I have the same problem with serial over LAN on a Dell poweredge T320 server. Do you have found a solution for this? Thanks, Florin
  9. F

    drbd on proxmox cluster - log - kernel-provided name 'drbd1'

    I have set up some proxmox servers in cluster with drbd for replication. All work well except when I reboot servers in log I see: udevd[486]: kernel-provided name 'drbd1' and NAME= 'drbd_pve_r1' disagree, please use SYMLINK+= or change the kernel to provide the proper name This message is...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!