Search results

  1. H

    Internal network between containers

    I can't use net0, since I'm already using it for my public IP interface :/
  2. H

    Internal network between containers

    Oh I didn't, thanks! :) I'm going to give it a try and see if it works.
  3. H

    Internal network between containers

    DHCP it's active only for IPv6, which I don't care at the moment. I don't need IP forwarding neither Masquerading, as each container has another interface with a public IP that is used for internet access. I just need the second interface with the internal network for internal communication -...
  4. H

    Can't login with console (noVNC)

    Hey there! I'm having a weird problem with my Proxmox server. I can't login to any of my virtual machines/containers using the console. I tried logging in with root, inserted my password, and I always get an error. I even tried to reset the password to 123456, and couldn't login... If I...
  5. H

    Internal network between containers

    I don't see any arp from any of my containers :/ I've tried to recreate the VM's and the bridge, but isn't working :(
  6. H

    Internal network between containers

    Yes, it's the container, sorry about using the wrong expression. I have everything in the same host :/
  7. H

    Internal network between containers

    Yes, I restarted the containers, and also the host server. Here is the config file (I'm using CentOS): [root@vpn03 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1 DEVICE=eth1 ONBOOT=yes BOOTPROTO=none IPADDR=192.168.1.2 NETMASK=255.255.255.0 GATEWAY=192.168.1.254 IPV6INIT=yes...
  8. H

    Internal network between containers

    Hmmm. I changed it to this: And the other to 192.168.1.3/24. The problem now is different. In one of the VM's I don't get any connectivity (not even the eth0 public IP that was working), and on the other, the eth1 interface seems to be disabled: 23: eth1@if24...
  9. H

    Internal network between containers

    Absolutely. This is container 1: And this is container 2:
  10. H

    Internal network between containers

    I can't ping 192.168.1.254 either :( [root@maestro ~]# ping 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. From 192.168.1.2 icmp_seq=1 Destination Host Unreachable What would you do, step by step, to have the internal network working? I feel like i'm missing some...
  11. H

    Internal network between containers

    Here's the output: root@blackpearl:~# brctl show bridge name bridge id STP enabled interfaces vmbr0 8000.74d02b26be58 no eth0 veth102i0 veth103i0 vmbr1 8000.000000000000 no vmbr192...
  12. H

    Internal network between containers

    I did it, and it's not working... I have this bridge, set up this way: https://cloudup.com/cTxjh3dGBhP On the containers I have two interfaces, eth0 and eth1, where eth1 is the internal interface, and it's configured as follows: https://cloudup.com/cUph80duvpz I have the same setup for...
  13. H

    Internal network between containers

    Hey there. I'm having a few troubles implementing the following scenario: I have a dedicated server from OVH. I have a few fallover IP's that are working fine with my LXC containers. The problem is, I want to implement some internal networking (192.168.1.0/24 for example), so I can set up an...

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!