Sorry for the ambiguous subject but I am not sure how to describe it. Basically, I run the following setup on my host (Debian 12):
/etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
iface enp42s0 inet manual
# Bridge
auto br0
iface br0 inet static
bridge_ports enp42s0.100 dhcp
address 10.100.0.198/26
broadcast 10.100.0.255
gateway 10.100.0.193
dns-nameservers 10.0.0.2
My container is attached to br0 as follows: incus config device add graynode-1 eth0 nic nictype=bridged parent=br0
Previously, this setup work. The DNS Server can “see” the container - it knows its MAC and provides an IP. However, while the container does get an IP, it can no longer reach the outside world/lan, and the outside world/lan can not reach the container.
Any ideas?
Oh, here is the container info:
╰─ incus info graynode-1 1 ↵
Name: graynode-1
Description:
Status: RUNNING
Type: container
Architecture: x86_64
PID: 3251820
Created: 2024/12/01 17:45 EST
Last Used: 2025/01/11 20:12 EST
Started: 2025/01/11 20:12 EST
Resources:
Processes: 66
Disk usage:
root: 185.59GiB
CPU usage:
CPU usage (in seconds): 16
Memory usage:
Memory (current): 137.02MiB
Network usage:
eth0:
Type: broadcast
State: UP
Host interface: vethe2c85841
MAC address: 00:16:3e:4d:b4:de
MTU: 1500
Bytes received: 1.18kB
Bytes sent: 12.54kB
Packets received: 4
Packets sent: 64
IP addresses:
inet: 10.100.0.232/26 (global)
inet6: fe80::f406:46bc:58b0:7cd5/64 (link)
lo:
Type: loopback
State: UP
MTU: 65536
Bytes received: 233.04kB
Bytes sent: 233.04kB
Packets received: 2384
Packets sent: 2384
IP addresses:
inet: 127.0.0.1/8 (local)
inet6: ::1/128 (local)
Maybe check iptables -L -n -v and nft list ruleset just to be sure.
But otherwise, something that may be worth trying is starting two instances and see if they can communicate with each other. If they can and only can’t reach the outside, then it could mean that your physical network is enforcing something like a single-MAC policy on the physical switch port or something along those lines.
So the container in question is an opensearch node and I have two other data nodes up and running. As such, I took the easy way out and deleted the problematic node/container and created a new node and container with the same config.
Everything is working as intended and my shards are balancing
Ghost in the machine, perhaps? Irrespective, thank you for your help!