The Complete Guide to Configuring netProfileManager Managing network configurations across different environments can be challenging. netProfileManager simplifies this process by allowing users to automate network switching based on locations or conditions. This guide will walk you through setting up and optimizing the tool. Prerequisites and Installation
Before starting, ensure your system meets the basic requirements.
Operating System: Windows 10 or higher / Linux (with network-manager). Dependencies: .NET Runtime 6.0 or later.
Privileges: Administrator or root access for network control.
To install, download the latest release from the official repository, extract the files to your desired directory, and run the executable installer. Understanding the Configuration File
The application relies on a central configuration file, typically named profile.config.json. This file houses all environment definitions.
{ “Profiles”: [ { “ProfileName”: “Office-Secure”, “TriggerType”: “SSID”, “TriggerValue”: “Corporate_WI_FI”, “Settings”: { “DHCP”: false, “IPAddress”: “10.15.2.45”, “SubnetMask”: “255.255.255.0”, “Gateway”: “10.15.2.1”, “DNS”: [“10.10.1.10”, “8.8.8.8”] } } ] } Use code with caution. Step-by-Step Profile Setup Follow these steps to configure your profiles effectively. 1. Define Triggers
Triggers determine when a specific network profile activates.
SSID: Activates when connected to a specific Wi-Fi network name.
MAC Address: Triggers based on the gateway router’s hardware address.
IP Range: Switches when an assigned DHCP address matches a subnet. 2. Configure IP and DNS Settings
For each profile, decide between dynamic and static routing.
DHCP: Set to true for automatic assignment at home or public cafes.
Static IP: Enter the IP, Subnet, and Gateway for strict corporate networks.
Custom DNS: Add specific server addresses to bypass default provider restrictions. 3. Automation and Scripts
You can execute custom scripts immediately after a profile loads.
Pre-Connect: Runs before switching networks (e.g., stopping a VPN).
Post-Connect: Runs after a successful connection (e.g., mounting network drives). Troubleshooting Common Issues
If your profiles are not switching correctly, verify these components.
Permission Errors: Ensure netProfileManager runs with elevated administrator privileges.
Trigger Mismatch: Double-check spelling and casing of Wi-Fi SSIDs.
Leave a Reply