Installation
Prerequisites
Hardware & Software requirements
| Type | Minimum | Recommended |
|---|---|---|
| Processor | 64-bit (x86-64) compatible | > 2.0 GHz, > 4 Cores |
| Memory | 2 GB RAM | 16 GB RAM |
| Graphics | DirectX 9 | DirectX 12 |
| Display | 1920x1080 screen resolution | 2560x1440 screen resolution |
| Operating System | Windows 10 version 1607 | Windows 11 version 24H2 or later |
Network Packet Capture
- One of:
- WinPcap: Version 4.1.3 or later.
- Npcap: Version 1.6 or later.
If you decide to use Npcap, ensure you have a valid license. Licensing details are available at Npcap Licensing.
WeConfig may offer to install WinPcap if it detects the need.
If so, a notification will appear in the user interface with a link to install WinPcap.
If neither WinPcap nor Npcap is installed, WeConfig will operate in a reduced mode with limited functionality.
WeConfig may not detect the connection between the computer and the network if the Network Interface Card (NIC) discards LLDP frames. This issue is common with low-end USB NICs.
Installation Packages
Standard Installation Package
- Executable Name: WeConfigSetup.exe
- Usage: Recommended for general use.
- Installation Process:
- Installs WeConfig in the user's directories.
- WeConfig, once installed, will be able to automatically update to newer versions if configured to do so, see Application Settings
- Administrative access rights are not required for this installation.
MSI Installation Package
- Executable Name: WeConfig.Msi.(Version).msi
- Usage: Recommended for strict IT environments where automatic software updates are prohibited.
- Installation Process:
- Installs WeConfig into a desired location, typically C:\Program Files\ or similar.
- WeConfig, once installed, will not be able to automatically update itself, but will attempt to notify the user when an update becomes available.
- Administrative access rights are required for this installation
Portable Installations
- Executable Name: Irrelevant, generated as a full directory with all relevant files
- Usage: Recommended for airgapped systems.
- Installation Process:
- Generated from an existing installation of WeConfig
- Will not attempt to check for updates
- Any shortcuts and similar handling must be set up manually.
- See Portable Installations for more information.
Usage requirements
Certain functionality in WeConfig requires an elevated level of access. These requirements exist due to the functional requirements of WeConfig as a network configuration manager, which implies a certain level of desired access, as detail below.
Requirement 1: Manipulation of network adapter addressing
In order to function properly against local network devices that lack a DHCP server, which is often the case in offline networks, WeConfig needs to be able to change the the IP address of the network adapter which is being used to connect to these devices. Alternatively, the user running the program can, by themselves, alter their IP address on said adapter, but doing so requires a similar level of permission be granted to the user.
Specifically, this is used by WeConfig to edit addresses and routes on selected network adapters, via the software known as WeConfig.LinkLocal.Daemon.exe, a small executable that uses the windows-native IpHlpApi to add linklocal addressing to a specific network adapter, and via WeConfig.InterfaceEditor.Daemon.exe in order to edit routes and other IP properties.
Requirement 2: Creating firewall rules
In order to recieve certain information from the network, WeConfig needs certain ports to be open. WeConfig comes with the built-in ability to make these firewall adjustments at the users behest and with their confirmation, but needs authorization to actually execute these changes. Alternatively, if the required changes are deployed to the managing device ahead of time, this functionality becomes unnessecary. The rules that WeConfig may attempt to create are as follows:
| Rule name | Protocol | Port | Profiles |
|---|---|---|---|
| Snmp Trap WeConfig | UDP | 162 | Domain & Public & Private |
| IpConfig WeConfig | UDP | 5098 | Domain & Public & Private |
| Syslog WeConfig | UDP | 514 | Domain & Public & Private |
| Mdns WeConfig | UDP | 5353 | Domain & Public & Private |
Online activity
Some functionality of WeConfig relies on occassional internet activity in order to retrieve additional information and data.
The following functionality requires internet connectivity to function properly:
| Functionality | Explanation | Offline fallback |
|---|---|---|
| Device definitions | Model names, icons and port maps, used to render the network toplogy map | Keeps any previously retrieved entries |
| MAC OUIs | Organizational Unique Identifier database, used to help identify unknown devices | Keeps any previously retrieved entries |
| Firmware Rules | Rules specifying in what order firmwares must be installed | Keeps any previously retrieved entries |
| Licenses | Limits or enables extended functionality in WeConfig | Cached license will be kept until expiry |
| Firmwares | Download specific versions of firmware for devices | Previously downloaded firmware is kept |
| Application Usage | Gathers usage and performance statistics, see Statistics Gathering | Do not send |
Statistics Gathering
WeConfig will by default send usage statistics to a centralized database over the Internet. The information sent does not contain any identifying information, nor any sensitive network information. It is used to measure performance, how the application is used, and unanticipated problems.
Information will be sent unless the user opts out. Every time WeConfig starts, WeConfig will ask the user whether they consent to this or not until a choice is made. It is possible at any time to revert any choice in the Application Settings.