NetworkManager

NetworkManager is a self-hosted web application for keeping an inventory of hosts, ports, and services across local networks.

  • Infrastructure
  • Network Services
  • Productivity
  • Tools & Utilities
NetworkManager is a self-hosted web application for keeping an inventory of hosts, ports, and services across local networks. It supports multiple networks defined by subnet and size, and lets you record the ports used and services running on each host for homelab or LAN administration.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

12/100 Low

Maintained
0last commit 884 days ago
Popular
144 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 33 days ago

GitHub stars
4
Open issues
3
Last commit
2024-06-20
License
MIT
Activity
stale

Checked 9 days ago - source: GitHub (Sander0542/Network-Manager)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Let NetworkManager manage an ignored interface If a network interface isn't controlled by NetworkManager, add a [device] section that matches the interface name and sets managed=1. Without this, NetworkManager ignores that card or port, so you can't set up the connection through it. source
  • Set a fixed IPv4 address with nmcli Use nmcli ipv4.addresses to enter an address like 192.168.1.100/24 and answer yes to set ipv4.method to manual. If the method stays automatic or DHCP, NetworkManager may not use your static address and the machine may lose its intended IP. source
  • Add Wi-Fi PSK for secured networks For a secured Wi-Fi connection, provide the Pre-Shared Key (the Wi-Fi password) using a line like wifi-sec.psk:the_password. Without the PSK, NetworkManager cannot authenticate to the Wi-Fi network and the connection will fail. source
  • Container setup Run the container on port 9000 and set PUID, PGID, TZ, and a 32-character APP_KEY; MySQL connection variables are optional. source

Fetched 44 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I configure the required application key for the Network Manager Docker image?

Set APP_KEY to a random string of 32 alphanumeric characters before running the container. It is required and is used to secure data.

Which port does the Network Manager web interface use?

Expose container port 9000 for the web GUI, for example with -p 9000:9000.

How do I point the container at my own MySQL database?

Set DB_HOST, DB_PORT, DB_USERNAME, DB_PASSWORD, and DB_DATABASE as needed. The defaults are 127.0.0.1, 3306, root, an empty password, and network_manager.

How should I configure Network Manager when running it behind an HTTPS reverse proxy?

Set OCTANE_HTTPS=true so the webserver generates HTTPS links instead of HTTP links. Keep the container listening on port 9000.

Answers sourced from github.com

Community

Collected 47 days ago - public community threads