[SOLVED] Need ping for networking work

[sozie]

Hello,

I am making this message because I have a small problem that nobody seems to have complained about. I am using 2 blocks of IPv4 (185.171.202.0/24) with which I have no problem. I recently took a new block (45.154.96.0/24).

When creating an LXC container with an IP of 185.171.202.0/24, I have no problems, and I can establish an SSH connection directly without any problems.

However, when I create an LXC container with an IP of 45.154.96.0/24, it does not work. I have to connect from my PVE to the container in question, and run the

ping 8.8.8.8

command to be able to access SSH afterwards.

We checked with my provider, and the problem does not seem to come from their side. At the router level the configuration is identical for the 185.171.202.0 block and for the 45.154.96.0. At first sight it looks like an ARP problem, but on their side the ARP update is forced every 60 seconds.

And we can't at the moment determine where the problem comes from, that's why I'm turning to you, in the hope that someone has an answer to this problem.

I thank all the people who will take the time to read this topic.
Have a nice day !

P.S: Here are some screenshots of the different configurations.

# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto ens2f1
iface ens2f1 inet manual

iface ens2f0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.4.5/24
        gateway 192.168.4.254
        bridge-ports ens2f1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

 

[sozie]

Hello,

Nobody has a solution to this problem?

Thanks again in advance to all the people who are likely to look into it.

Rémi.

 

[Lorenz.S]

Hi,

This sounds very much like a networking issue. Could have many reasons, though...

Do you have to "ping" for each container, or each IP address, or for the whole block once?

Could also be some sort of (IPsec) tunnel, which needs to be established before a bidirectional communication is possible

 

[sozie]

Hello,

Thank you for your answer. The problem has been solved, it was obviously a problem with the Cisco N9K.

Rémi.