Differentiate connection lines in Network Topology by connection type (solid for wired, dashed for Wi-Fi)

[Gaspode-1974]

Hi, first off — the Network Topology view is genuinely great once it's set up. One small thing that would push it further:

Right now the topology shows a different icon per device depending on whether Parent Node Port is set (Ethernet icon) or empty (Wi-Fi icon). With a larger tree though, it's hard to tell wired from wireless at a glance — you end up zooming in on each icon one by one.

Could the connection line itself use the same signal that already drives the icon?

• Solid line → wired (Port set)
• Dashed line → Wi-Fi (Port empty/0)

Separately, but related: I've been adding manually-created "virtual" devices (Relationship Type: virtual) for Docker services and NAS packages running under a host. They obviously don't have a real switch port, so they default to the Wi-Fi icon — the only workaround I found was entering an arbitrary port number, which feels like misusing the field. "Wired vs wireless" doesn't really apply to a software service in the first place, so it'd make more sense if virtual devices got their own icon, or at least skipped the Wi-Fi one regardless of the Port value.

Checked the open issues and discussions first, didn't find this covered — point me at an existing thread if I missed it.

Environment: NetAlertX v26.8.5, Docker (jokobsk/netalertx image), network_mode: host.

[jokob-sk]

The next version will render solid lines for ethernet connections (where port is a number), otherwise a dashed line is shown. The wifi icon will only render if an SSID is available, otherwise a (?) icon is shown:

It would be great if you could test the ghcr.io/netalertx/netalertx-dev-unsafe Docker image in ~15 minutes (or once the latest GitHub Action finishes).

⚠️ Please back up everything first, or ideally spin up a separate container (make sure you use a unique PORT and GRAPHQL_PORT if running instances concurrently) with its own DB and config (a copy of your current setup), as database changes may occur.

After updating:

• Click the 🔄 refresh button in the blue header at the top
• Hard refresh your browser cache (shift + reload) to force js and css files reload

👉 If I don’t receive confirmation that this works, I may revert the changes to avoid introducing bugs.

Disclaimer: Running the dev container long-term may lead to data loss, as upgrade paths are not guaranteed.

Thanks in advance,
j