Access to remote services via IPv4

1

In a newly created incus (6.0.3) container in my laptop, I can do the following:

ping -4 daniel.degu.cl
ping -6 daniel.degu.cl

With IPv4 I cannot reach the server, but I can with IPv6. I can reach both if I do the same from outside the container.

The network my container is using has the following description:

config:
  ipv4.address: 10.108.130.1/24
  ipv4.nat: "true"
  ipv6.address: 1234:1234:1234:1234::1/64
  ipv6.nat: "true"
description: ""
name: incusbr0
type: bridge
used_by:
- /1.0/profiles/default
- /1.0/instances/maximum-cicada
managed: true
status: Created
locations:
- none
project: default

To me, there is no problem with the bridge configuration. Does it have an issue?

2

You mention ICMP (i.e. ping) but does the same apply to TCP connections (i.e. wget)?

This looks like a firewall issue on the host, considering that IPv4 is blocked but not IPv6.

Have a look at How to configure your firewall - Incus documentation which covers the common firewall cases.

3

@simos, wget works with IPv6, but not with IPv4. So, I guess it is a firewall issue on the host, as you said. The host is debian 12.11, so I will take a look at the possible software that may be related to the firewall. I don’t remember having installed something different from what is out-of-the-box regarding the firewall. Thank you for the link to the firewall configuration. I will read it, but it is currently giving an error 503.