Network setup, can't ping CT routed IP

[NIIcK]

Hello,

I have this issue on the Proxmox 5.1.

I have a container with 2 network interfaces. One for LAN and one with routed IP.

eth0 -> routed IP (82.xx.xx.xx)
eth1 -> LAN IP (192.168.x.x)

I can ping any IP on the network from the CT (both routed class and local class) and I can ping the LAN IP of the CT from any other device on the local network as well as from any other device on the internet however I cannot reach the routed IP (eth0) from within the LAN network.

I need to be able to directly reach the routed IP from the LAN network. If I remove eth1 then I can ping eth0 quite fine but as soon as I add it I lose connectivity to it. I need the LAN for Samba purposes.

Any help will be appreciated, thank you in advance!

 

[GarrettB]

What are you using for routing outside of the container?

I'm not sure what you mean by "as well as from any other device on the internet" ...LAN should not be pingable from the internet.

 

[NIIcK]

A router. I can ping the Proxmox' server IP address (both LAN and routed) as well as other servers in the network. It is just the CTs and VMs created within the Proxmox that I can't ping on routed IP while a second NIC with LAN IP is present.

 

[GarrettB]

Where is the eth0 gateway?

 

[GarrettB]

I have experienced not being able to reach a domain I was hosting, but I've always been able to reach the ip.

You'll have to provide more routing details.

 

[NIIcK]

eth0 gateway is the router (one WAN 2 LAN NIC's); one LAN -> internal (192.xx.xx.xx) second LAN routed class (82.xx.xx.xx). The thing is, if there was a wrong setup on the router itself I couldn've been able to ping the routed class at all (on other machines) from LAN but I can. It only happens on the containers and virtual machines from Proxmox.

 

[GarrettB]

Do you have two network devices for the container in the Hardware settings?

 

[NIIcK]

Yes; vmbr0 and vmbr1
vmbr0 -> eth0 - bound to the routed NIC on the server
vmbr1 -> eth1 - bound to the LAN NIC on the server

 

[GarrettB]

I was expecting net0 and net1. You are referring to bridges..what are they bridging?

 

[NIIcK]

auto vmbr0
iface vmbr0 inet dhcp -> dhcp is dealt with by the router itself
bridge_ports eno8
bridge_stp off
bridge_fd 0
auto vmbr1 -> dhcp is dealt with by the router itself
iface vmbr1 inet dhcp
bridge_ports eno9
bridge_stp off
bridge_fd 0

I need the routed IP to be directly accessible on the internet as well.

 

[GarrettB]

Are you using OVS or Linux bridge setup? (System>Network)

 

[NIIcK]

Linux bridge

 

[GarrettB]

Your iface should be followed by port, not bridge, is my thought.

EDIT: no, forget that. Where are the addresses?

 

[GarrettB]

If eno8 and 9 are on the device, then you are trying to bridge only with the container. But bridging is not what you want, I don't think. That would tie the ports together into the same network.

auto vmbr0
iface vmbr0 inet dhcp -> dhcp is dealt with by the router itself
bridge_ports eno8 ***should be another ports here?
bridge_stp off
bridge_fd 0
auto vmbr1 -> dhcp is dealt with by the router itself
iface vmbr1 inet dhcp
bridge_ports eno9 *** should be another port here?
bridge_stp off
bridge_fd 0

Maybe:
iface eno8 inet dhcp
address...
netmask...
gateway...

 

[GarrettB]

In Proxmox Network settings, I have vmbr1, 2, 3 etc. linux bridges.

In VM Hardware settings I have Network Device net0, net1, net2, etc. with a bridge noted in the settings.

Then, in the VM itself, if I have allocated more than one network device, I just run straight iface setups with addresses, gateways, etc.

 

[NIIcK]

Hmm ... will give it a try. Regarding the NIC ports, they are correct; eno8 and eno9 are the network cable connected ones.

Thank you!

 

[GarrettB]

Bridging is done in Proxmox between node and VM/container, but then you should be able to set each virtual NIC to whatever network you need with no bridging in those settings.

 

[GarrettB]

eno8 and eno9 are the network cable connected ones.

Ahhh, these are the node's ports.

So vmbr0 would note eno8 and vmbr1 would note eno9, and then those bridges are able to be used by the VM.
Net0 on VM would note bridge vmbr0, and in the VM settings, whatever ethernet name is given for the virtual NIC, that should be in the iface settings.

BTW, This will put the node on the local network if you only have two NICs to Proxmox. It will not be isolated in its own network, if I'm following you correctly.

 

[NIIcK]

eno8 connected to router routed class LAN port -> vmbr0 (82.xx.xx.x1) on Proxmox -> eth0 on CT (82.xx.xx.x2)
eno9 connected to router LAN class, LAN port -> vmbr1 (192.168.1.5) on Proxmox -> eth1 on CT (192.168.1.6)

 

[NIIcK]

I can ping any IP (both routed and local) from the CT but I can only ping the local IP from within the network.