IP Address Register Consistency Checker

Paste or open the IP address list of a substation or SCADA network (CSV or a copy from Excel). The checker finds duplicate addresses and MACs, network and broadcast addresses given to devices, gateways outside their subnet, mixed masks and gateways on one LAN, and overlapping subnets — with the line number of every problem. Nothing is uploaded; the check runs in your browser.

Register

First line = column headings. In Excel, select the table and copy — paste here directly (tab separated). Columns recognised: name, ip, mask, gw, mac, vlan, network.

Result
7 errors to correct
16 devices · 7 errors · 3 warnings · 2 notes

Subnets in the register

SubnetDevicesVLANGatewayNetwork
10.13.0.0/241 / 254110.13.0.1Station bus
10.13.0.0/258 / 126110.13.0.1, 10.13.1.1Station bus
10.13.0.128/262 / 6220—Process bus
10.13.0.192/261 / 629910.13.0.193Management
10.13.0.192/272 / 309910.13.0.193Management
10.13.1.0/281 / 143010.13.1.1SCADA DMZ
169.254.0.0/161 / 655341—Station bus

Findings

  • Errorline 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15Subnet 10.13.0.0/24 (BCU_J01) overlaps 10.13.0.0/25, 10.13.0.128/26, 10.13.0.192/26, 10.13.0.192/27. Devices in the overlapping range disagree about which addresses are local — usually the device on 10.13.0.0/24 has the wrong mask.
  • Errorline 5, 7IP address 10.13.0.14 is used 2 times: P132_Q01, P87T_T1.
  • Errorline 9BCU_J02: gateway 10.13.1.1 is outside the device's subnet 10.13.0.0/25 and can never be reached.
  • Errorline 10BCU_J03 10.13.0.127 is the broadcast address of 10.13.0.0/25 and cannot be assigned to a device.
  • Errorline 11, 12MAC address 00-21-C1-11-00-0A is used 2 times: MU_Q01, MU_T1.
  • Errorline 13, 14, 15Subnet 10.13.0.192/26 (ENG-PC) overlaps 10.13.0.192/27. Devices in the overlapping range disagree about which addresses are local — usually the device on 10.13.0.192/26 has the wrong mask.
  • Errorline 17LAPTOP 169.254.10.5: 169.254.x.x is a link-local (APIPA) address — the device was set to DHCP and found no DHCP server.
  • Warningline 8, 17VLAN 1: most devices use /25, but BCU_J01 uses /24, LAPTOP uses /16. Devices on one LAN must use the same mask, or some will not reach others.
  • Warningline 9VLAN 1: most devices use gateway 10.13.0.1, but BCU_J02 uses 10.13.1.1.
  • Warningline 15VLAN 99: most devices use /27, but ENG-PC uses /26. Devices on one LAN must use the same mask, or some will not reach others.
  • Infoline VLAN 1 carries 3 subnets (10.13.0.0/24, 10.13.0.0/25, 169.254.0.0/16). This works, but devices in different subnets need a router to talk.
  • Infoline VLAN 99 carries 2 subnets (10.13.0.192/26, 10.13.0.192/27). This works, but devices in different subnets need a router to talk.

What the IP register checker looks for

The IP address register is usually a spreadsheet: one line per device with its name, IP address, subnet mask, gateway, MAC address and VLAN. It is written early, copied between documents and edited by several people, so typing errors survive until commissioning. Checking the whole list at once is faster than finding the faults one by one on site.

Per device the checker verifies the format of the IP, mask and MAC, and flags addresses that cannot be assigned: the network or broadcast address of the subnet, loopback, multicast and 169.254.x.x link-local addresses. It checks that the gateway is inside the device's own subnet and is not the device itself.

Across the register it finds duplicate IP addresses, MAC addresses and device names; masks or gateways that differ inside one VLAN or network (the majority value is taken as intended); subnets that overlap, which means devices disagree about who is local; and one subnet spread over several VLANs, which cannot work without routing.

Paste the table directly from Excel (it is tab separated), or open a CSV file. The checker reads the column headings to find the columns, accepts IP/prefix notation such as 10.13.0.14/25, and gives the line number of every finding. The data stays in your browser.

Findings and their meaning

CodeSeverityMeaning
DUP-IPErrorThe same IP address on two or more devices
DUP-MACErrorThe same MAC address on two devices (often a copied line)
IP-NETBCErrorNetwork or broadcast address given to a device
IP-SPECIALErrorLoopback, link-local (169.254.x.x), multicast or reserved address
GW-OUTSIDEErrorGateway outside the device's own subnet
SUBNET-OVERLAPErrorTwo different subnets cover the same addresses
MASK-MIX / GW-MIXWarningMask or gateway differs from the rest of the VLAN or network
SUBNET-VLANSWarningOne subnet appears in more than one VLAN
VLAN-SUBNETSInfoA VLAN carries more than one subnet

Frequently asked questions

Which columns does the checker need?

At least an IP address column. A subnet mask column (or IP/prefix notation) enables the mask, gateway and subnet checks; gateway, MAC, VLAN and network columns enable the rest. Column names such as Device, IP address, Subnet mask, Gateway, MAC address, VLAN are recognised.

Is my register uploaded anywhere?

No. The file is read and checked in your browser; nothing is sent to a server.

Why is an overlap an error and not a warning?

When two subnets overlap, a device on the wider subnet treats addresses as local that the device on the narrower subnet sends to its gateway. The result is the one-way fault that the SCADA Connectivity Assistant explains — it nearly always means one mask is wrong.

For preliminary engineering use. Results must be checked by a qualified engineer against the project's standards. How results are checked · Terms & disclaimer · Build 93206b8 · 2026-11-11