scan only 1 physical interface

[svanhoutte]

It seems the script only scan 1 physical interface

atlas | 2025/09/22 08:38:15 ❌ DB init failed: schema execution failed: duplicate column name: online_status
atlas | 2025-09-22 08:38:15 🔹 🚀 Running fast scan...
atlas | 🚀 Running fast scan...
atlas | Scanning subnet: 192.168.128.1/24
atlas | 🌐 External IP recorded:
atlas | ✅ Fast scan complete.
atlas | 2025-09-22 08:38:17 🔹 ✅ Fast scan complete.
atlas | 2025-09-22 08:38:17 🔹 🐳 Running Docker scan...
atlas | 🐳 Running Docker scan...
atlas | ✅ Docker scan complete.
atlas | 2025-09-22 08:38:25 🔹 ✅ Docker scan complete.
atlas | 2025-09-22 08:38:25 🔹 🕵️ Running deep host scan...
atlas | 🚀 Running deep scan...
atlas | 🔍 Discovering live hosts...
atlas | ✅ Deep scan complete.
atlas | 2025-09-22 08:41:51 🔹 ✅ Deep scan complete.

from inside the container i can see both interface
ifconfig ens160
ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.128.1 netmask 255.255.255.0 broadcast 192.168.128.255

ifconfig ens192
ens192: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.51 netmask 255.255.255.0 broadcast 192.168.0.255

[karam-ajaj]

@svanhoutte I used some help from copilot to get this done and it should be working but I dont have any host to test on now.

There is no need to specify anything and it will scan all the subnets on all of the interfaces, would you be able to test this version and let me know about any issues? keinstien/atlas:pr-62

[svanhoutte]

@karam-ajaj Thanks for the update and the project ! This really a great work
The new code works great, i get the scan on the other interface as well now. The display shows the interface name under the remote host. If possible that would be i think more helpful to have the full ip address or the relevant digit information like .1 .2 ... .254 for a /24 and get the name of the interface under the full subnet (bellow 192.168.128.X there would be ens160) once

Current rendering

Potential upgrade

[svanhoutte]

@karam-ajaj there is i think an inconsistency in the the display, the subnets are cascaded behind each other in the display rather than being originated from the same host.

[karam-ajaj]

@karam-ajaj there is i think an inconsistency in the the display, the subnets are cascaded behind each other in the display rather than being originated from the same host.

Thank you for the feedback!
I tried to solve this and many other issues in version dev3.3, it would be great if you can test it and let me know.

I don't currently have a host with multiple interfaces to test further but will look into it in future releases, let me know if this issue is fixed or needs further modifications, thanks!

[svanhoutte]

@karam-ajaj Just tested the dev3.3 docker image, the display is the same.