Networking works for existing containers and VMs but not newly created ones.

[prox145]

Hi, for some reason whenever I create a new VM or Container and try to set networking up (correctly configured as far as I can see) it does not work.

The existing VMs and Containers however are able to connect just fine, if you need more information to help me solve this then please ask.

 

[Moayad]

Please post your network configuration /etc/network/interfaces and the config for the LXC/VM.

 

[prox145]

Please post your network configuration /etc/network/interfaces and the config for the LXC/VM.

Sorry for the late response, I will post in one minute.

 

[prox145]

Please post your network configuration /etc/network/interfaces and the config for the LXC/VM.

Hi, the /etc/network/interfaces config is the following:

auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 185.189.50.190
        netmask 255.255.252.0
        gateway 185.189.48.1
        bridge_ports eno1
        bridge_stp off
        bridge_fd 0

iface eno2 inet manual

Here is a container network configuration, that does not work:

Here is from another container, that has working networking:

Do you require anything else? Thank you.

 

[Moayad]

Can you ping the gateway or 1.1.1.1 from the LXC that does not work?

 

[prox145]

Can you ping the gateway or 1.1.1.1 from the LXC that does not work?

That does not work, no. It gets stuck and then after a short while this appears

 

[Spoonman2002]

Only difference between the 2 screenshots is the option Firewall (On/Off).
I do not think this is the fix for your problem, but you can always try....

 

[prox145]

Only difference between the 2 screenshots is the option Firewall (On/Off).
I do not think this is the fix for your problem, but you can always try....

It is not a fix, if you had paid attention to my post it says the one with the Firewall has working networking, the other does not.

 

[prox145]

@Moayad Do you have any suggestions on how I could possibly solve it?

 

[Moayad]

What say the output of ip r inside the CT?

 

[prox145]

What say the output of ip r inside the CT?

root@testnet1235:~# ip r
default via 185.189.48.1 dev eth0
185.189.48.0/22 dev eth0 proto kernel scope link src 185.189.50.20