Repository navigation
Configuration and Data Files
NetworkScanner uses two kinds of files: reference data shipped with the app, and user data written per user.
These ship next to the executable and are read-only from the user's perspective. In the source tree they live in the NetworkScanner/ (WPF) project and are linked into the Avalonia project at build time (copied to output, not duplicated).
| File | Purpose |
|---|---|
ouiinfo.ini |
MAC OUI → vendor mapping (IEEE public data, generated via the OUIConvertor utility). |
reservedports.ini |
Reference list of reserved (well-known) ports. |
prohibitports.ini |
List of risky ports known to be used by backdoors / trojans. |
User data is written to a per-user directory so that Velopack updates — which replace the app folder — don't wipe your settings and results:
-
Windows:
%APPDATA%\NetworkScanner -
macOS / Linux:
~/.config/NetworkScanner
| File / folder | Purpose |
|---|---|
setting.ini |
Settings: FTP account (password encrypted), schedule hours, port list, language, etc. |
iprange.ini |
List of IP ranges to scan (auto-seeded with the local subnet on first run). |
annotations.ini |
User-entered name / note per IP, re-applied on later scans. |
env/ |
Scan-result output folder (CSV etc.). |
On first run the app migrates any of these files it finds in the old locations (working directory / exe directory) into the per-user directory.
The FTP password is stored in the OS credential store, not in plain text:
- Windows — DPAPI
-
macOS — Keychain (
security) -
Linux — libsecret (
secret-tool)
Where those tools are unavailable, it falls back to Base64 obfuscation and logs a warning.
Do not commit user-data files. Tests set UserDataPaths.OverrideRoot instead of touching the real profile. See Architecture.