Every IP is stored on the gear itself.
A networked device is rarely one address. A console carries a primary line, a Dante line and a control port, and each of those has its own IP, subnet, VLAN and switch port. GigPal PRO keeps all of them on the item record — so the address travels with the asset instead of with a spreadsheet. Scan the rack, read the addresses. Know the IP but not which box it is? Search for it and the gear comes back.
The addresses are stuck in a spreadsheet nobody trusts.
There's a sheet somewhere, and it was accurate the week it was written. Since then a switch got swapped, the Dante line moved onto a different VLAN, and an access point came back from a rental with somebody else's static address still burned into it. Nobody updated the tab, because the tab isn't where anyone actually works.
So the real answer ends up in three places at once — a strip of gaff tape inside a rack door, a photo on one tech's phone, and the head of the guy who built the rig. At 6am on load-in, the person standing in front of the rack is usually the one with none of those, and the fix is a phone call to somebody still asleep.
With GigPal PRO: the address is a field on the item, the item is the thing with a barcode on the side of it, and the person at the rack is the one holding the answer.
From a stale spreadsheet to an address on every piece of gear.
One row per network the device is on.
Open a piece of gear and add an interface. Each one carries a label — Primary, Dante, Control, AP-1 — plus IP address, subnet, gateway, MAC, VLAN and port. Add as many as the device has. Nothing is mandatory, either: an interface starts counting as real the moment it holds an IP, a label or a MAC, so half-known gear goes in half-known and gets finished later. Rows left completely blank are dropped when you save, so a stray + ADD INTERFACE never leaves a ghost behind.
Add a device without going to find it.
On the NETWORK screen, ＋ ADD DEVICE opens a search across your inventory — type a name, a tag or a category, pick the item, and its interface editor opens right there. Anything that already has an address wears a HAS IP badge, so you can see at a glance what's left to do. SAVE & ADD ANOTHER drops you straight back into the picker, which is how a whole rack gets entered in one sitting instead of one round trip through Inventory per device.
Bring the whole sheet in at once.
Export your device tab as CSV and upload it. Columns are matched by header name, and the matching is forgiving — "IP Address", "netmask", "gw", "asset tag" and "switch port" all land where they belong. Anything guessed wrong you fix from a dropdown. Before a single row is written you see the first ten with a green tick or a red cross against each, plus a live count of exactly how many will match and how many will be skipped. Prefer to start from the right shape? Download the template.
Read it where you're standing.
Scan the tag on a rack and the item's details open with a NETWORK block on them: the interface label, the address in full, then mask, gateway, VLAN, switch port and MAC underneath. No second lookup, no second app, no asking anybody. Working backwards is just as quick — search by IP, VLAN, MAC, tag, location or category and the device it belongs to comes back. Inventory rows carry the address as a badge too, or "3 IPs" when there's more than one. In the browser, tapping an address copies it.
Then find out what's actually answering.
An address on a record tells you what should be true. On the Tech Table, GigPal PRO goes and checks what is: every interface with an IP gets a real TCP connection attempt from Pal Player on the house LAN — up to fifty at a time, roughly 800ms each — and the list regroups by what responded, not by which case the gear is packed in. Devices at your table get a TABLE mark. Silent ones fold into their own collapsed group so the working list stays short, and the screen distinguishes "we tried and got nothing" from "we haven't tried that one yet."
The parts that keep the list honest.
One console, three addresses
Devices and IPs are counted separately at the top of the screen — 14 devices, 22 addresses — because those are genuinely different numbers. Each interface is listed on its own line with the label and the address as the headline, and VLAN, mask, MAC and switch port in small type underneath.
One tag, five access points
A bulk line is a single inventory row standing in for many identical units. The convention here is one interface per unit — AP-1, AP-2, AP-3 — with distinct labels, which is also what makes a re-import land on the right one instead of piling up new rows.
The import never invents gear
Rows are matched to inventory by tag, case- and whitespace-insensitive. A row whose tag matches nothing is skipped and listed straight back to you — never silently dropped — so you can fix the sheet and re-run just those rows. Add the gear through Inventory's own import first, then wire it up here.
A second row can't overwrite the first
Within one file, an interface the import has already written is off-limits to every later row. That rule exists for a reason: five units all labelled "AP" once collapsed into a single row and four addresses vanished. Now every row is kept, and reused labels get named back to you.
Three different ways to not import
A tag that matched nothing. A tag that matched, but whose columns produced no usable data — almost always an IP column that never got mapped. A label reused on the same item. Each is reported separately with the tags named, because "matched but empty" used to be invisible and looked exactly like success.
It won't quietly overwrite a colleague
While you have an item's addresses open, another tab or a running import can land on that same item. If you haven't typed anything, your editor picks their change up silently. If you have, saving stops and asks — naming the item and the conflict. Overwriting somebody is a decision here, never a side effect.
Addresses don't travel with the model
Edit one of a batch of identical units and the model-level details — name, category, value, weight, photo, manual link — push across the whole batch. Network profiles never do; they belong to the individual unit. Creating a run of units at once doesn't copy an address onto the copies either.
The PORT field is not a TCP port
PORT holds whatever you write in it — "SW1/12", or just "12". The reachability probe deliberately ignores it and dials the default instead, because a bare "12" read as TCP port 12 would report a perfectly healthy device as dead. Where something is patched and whether it answers are different questions, and the field means what it says on the label.
- An interface holds
- Label, IP address, subnet, gateway, MAC, VLAN, port — all free text, all optional. It counts as a real interface the moment it carries an IP, a label or a MAC; anything blanker than that is discarded on save.
- Search matches
- Device name, tag, location and category, plus every interface's IP, label, MAC and VLAN. Inventory's own search matches IP and interface label too, and an inventory row shows the address as a badge — or "3 IPs" when there's more than one.
- CSV columns
- Tag (required), Label, IP, Subnet, Gateway, MAC, VLAN, Port — one row per interface. Headers auto-detect from common synonyms; the preview shows the first 10 rows and a live matched/skipped count. Re-running the same file updates in place rather than duplicating.
- How it writes
- Matched items save in chunks of 100 through the same save path the rest of the app uses — no parallel write path. If a chunk fails, the error tells you exactly how many items made it through before it stopped.
- LAN status
- Needs a Pal Player address set in Settings. Up to 50 targets per request, about 800ms allowed per target, re-checked every 45 seconds while the Tech Table is open. Unset or unreachable, it shows a plain note and blocks nothing.
- Who can do what
- Looking up an address needs lead access; adding, editing and importing are owner/manager. CSV import is a web-app job — open it on a phone and it points you at the browser rather than half-working.
The whole network, stored on the gear it belongs to.
Put the addresses where the gear is.
Upload your device sheet, check the column mapping in the preview, and every address lands on the item it belongs to — ready to read off a scan.
Get Started → All features →