Can't ping network device on host from container and vice-versa

kimmer2k

New Member
Jan 6, 2023
3
0
1
Let me preface this post by saying I am somewhat of noob and can't fully grasp "how things work" even after reading a bunch of docs, forums, and tutorials - and appreciate any help this community can provide!

Problem
I cannot seem to ping a device I setup on the host (homelab) from a container (emby), and vice-versa. I tried disabling firewalls on the host and container, but still unable to get a ping. The "Destination Host Unreachable" is curious, but for the life of me, can't figure this out. Thanks in advance!

Failed pings to container device from host:
Code:
root@homelab:~# ping 192.168.200.196 -c 3
PING 192.168.200.196 (192.168.200.196) 56(84) bytes of data.

--- 192.168.200.196 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2023ms
Failed pings to host device from container:
Code:
root@emby:/# ping 192.168.200.2 -c 3
PING 192.168.200.2 (192.168.200.2) 56(84) bytes of data.
From 192.168.200.196 icmp_seq=1 Destination Host Unreachable
From 192.168.200.196 icmp_seq=2 Destination Host Unreachable
From 192.168.200.196 icmp_seq=3 Destination Host Unreachable

--- 192.168.200.2 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2052ms

Background
I am trying to setup my old Ceton Cable Card Tuner on my Proxmox install. I believe I have properly installed the driver and manually assigned an ip (192.168.200.2) to the device (enp2s8) on the host (homelab). This device is pingable on the host:
Code:
root@homelab:~# lspci -v -s 02:08.0
02:08.0 Non-VGA unclassified device: Device 1b7c:0004 (rev 01)
        Subsystem: Device 1b7c:0004
        Flags: bus master, slow devsel, latency 32, IRQ 16
        Memory at 9f800000 (32-bit, non-prefetchable) [size=128K]
        Memory at 9f820000 (32-bit, non-prefetchable) [size=64K]
        Kernel driver in use: ctn91xx
        Kernel modules: ctn91xx

root@homelab:~# ip address show dev enp2s8
3: enp2s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether 00:22:2c:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet 192.168.200.2/32 scope global enp2s8
       valid_lft forever preferred_lft forever

root@homelab:~# ping 192.168.200.2 -c 1
PING 192.168.200.2 (192.168.200.2) 56(84) bytes of data.
64 bytes from 192.168.200.2: icmp_seq=1 ttl=64 time=0.014 ms

--- 192.168.200.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.014/0.014/0.014/0.000 ms

On the host, I created a bridge (vmbr1) for this device:
1673042455063.png

On the container (emby), I added a device (eth1) to the vmbr1 bridge, and assigned it an address of 192.168.200.196. This device is pingable within the container
1673042594450.png
Code:
root@emby:/# ping 192.168.200.196 -c 1
PING 192.168.200.196 (192.168.200.196) 56(84) bytes of data.
64 bytes from 192.168.200.196: icmp_seq=1 ttl=64 time=0.015 ms

--- 192.168.200.196 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.015/0.015/0.015/0.000 ms
 
192.168.196.xxx/24
192.168.200.xxx/24
192.168.200.2/32

The first two networks will never be able to "see" each other (unless you create some routes)
The third is a single ip address (/32) and will not be able to "see" other devices on 192.168.200.xxx/24 network.
You can use 192.168.200.xxx/24 as network for ALL your devices.
 

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!