I am trying to scan targets on a local IP using wireguard. But unfortunately it seems the scan is just stuck at 0%.
I have a self-compiled version running on Debian 12.
From the host itself I can ping and also ssh into the private IPs. So wireguard + routing is working.
It detects the hosts as alive, but does not do anything further:
libgvm boreas:MESSAGE:2025-02-09 15h33.36 utc:3165:757a0e11-7ea0-4184-b5c0-3f0e84d2e10a: Alive scan 757a0e11-7ea0-4184-b5c0-3f0e84d2e10a started: Target has 5 hosts
sd main:MESSAGE:2025-02-09 15h33.37 utc:3174:757a0e11-7ea0-4184-b5c0-3f0e84d2e10a: Vulnerability scan 757a0e11-7ea0-4184-b5c0-3f0e84d2e10a started for host: 192.168.50.21
sd main:MESSAGE:2025-02-09 15h33.37 utc:3175:757a0e11-7ea0-4184-b5c0-3f0e84d2e10a: Vulnerability scan 757a0e11-7ea0-4184-b5c0-3f0e84d2e10a started for host: 192.168.50.5
sd main:MESSAGE:2025-02-09 15h33.37 utc:3176:757a0e11-7ea0-4184-b5c0-3f0e84d2e10a: Vulnerability scan 757a0e11-7ea0-4184-b5c0-3f0e84d2e10a started for host: 192.168.50.23
sd main:MESSAGE:2025-02-09 15h33.37 utc:3177:757a0e11-7ea0-4184-b5c0-3f0e84d2e10a: Vulnerability scan 757a0e11-7ea0-4184-b5c0-3f0e84d2e10a started for host: 192.168.50.22
sd main:MESSAGE:2025-02-09 15h33.37 utc:3179:757a0e11-7ea0-4184-b5c0-3f0e84d2e10a: Vulnerability scan 757a0e11-7ea0-4184-b5c0-3f0e84d2e10a started for host: 192.168.50.40
libgvm boreas:MESSAGE:2025-02-09 15h33.39 utc:3165:757a0e11-7ea0-4184-b5c0-3f0e84d2e10a: Alive scan 757a0e11-7ea0-4184-b5c0-3f0e84d2e10a finished in 3 seconds: 5 alive hosts of 5.