OpenVAS in IPv6-only Kubernetes: Unable to Scan IPv4 Targets

[iseabal]

I’ve deployed OpenVAS inside a Kubernetes cluster that’s IPv6-only, and I’m running into an issue trying to scan IPv4 targets from within the cluster.

my setup:

• OpenVAS is up and running.
• The cluster has no IPv4 connectivity, only IPv6.
• When I try to scan an IPv4 address, it fails.
• error message in logs:

lib  misc-Message: 13:04:49.510: pcap_lookupnet failed: eth0: no IPv4 address assigned

My questions:

1. Has anyone successfully scanned IPv4 targets from an IPv6-only environment?
2. Is there a known workaround—like using a tunnel, proxy, or dual-stack gateway—to make this work?
3. Is OpenVAS limited in this kind of setup, or is it more of a networking/routing issue?

[Lukas (Lukas.Grunwald)]

@iseabal

IPv6-only, and I’m running into an issue trying to scan IPv4 targets from within the cluster.

That just can´t work, you need IPv4 support to scan IPv4 There is nothing in the world anyone can do

You can try to do Private - Public 1to1 NAT. But you need ipv4 to scan ipv4.