I have a container where I have configured an External Interface with its own IP as illustrated below.
The Truenas Scale system itself has IP's configured on bond0 as well.
The container is reachable from the rest of the subnet, but not from the Truenas host itself.
# ping 192.168.2.11
PING 192.168.2.11 (192.168.2.11) 56(84) bytes of data.
From 192.168.2.5 icmp_seq=1 Destination Host Unreachable
From 192.168.2.5 icmp_seq=2 Destination Host Unreachable
From 192.168.2.5 icmp_seq=3 Destination Host Unreachable
From 192.168.2.5 icmp_seq=4 Destination Host Unreachable
^C
--- 192.168.2.11 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4039ms
I have run tcpdump from both the host and the container, and all I see is an arp going out, but the other side does not receive it.
I did see this thread which seems very similar, but it didn't lead to an answer.
https://www.truenas.com/community/t...ernal-interface-different-ip-than-host.98972/
Hoping someone here has an idea.
The Truenas Scale system itself has IP's configured on bond0 as well.
The container is reachable from the rest of the subnet, but not from the Truenas host itself.
# ping 192.168.2.11
PING 192.168.2.11 (192.168.2.11) 56(84) bytes of data.
From 192.168.2.5 icmp_seq=1 Destination Host Unreachable
From 192.168.2.5 icmp_seq=2 Destination Host Unreachable
From 192.168.2.5 icmp_seq=3 Destination Host Unreachable
From 192.168.2.5 icmp_seq=4 Destination Host Unreachable
^C
--- 192.168.2.11 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4039ms
I have run tcpdump from both the host and the container, and all I see is an arp going out, but the other side does not receive it.
I did see this thread which seems very similar, but it didn't lead to an answer.
https://www.truenas.com/community/t...ernal-interface-different-ip-than-host.98972/
Hoping someone here has an idea.