Assigning IP addresses¶

There are two ways to put an IP address on an interface, and you can do both without leaving the device or interface page. Each interface row on the device's Interfaces tab has two buttons, and the interface detail page has the same two on its IP addresses tab:

• + Add IP - create a brand-new IP address and attach it here.
• Assign IP - attach an IP that already exists in Danbyte.

Add a new IP¶

Click + Add IP. The IP form opens already knowing which device and interface you're working on, so you only fill in the address itself.

Why you pick a subnet first¶

Every IP address belongs to a subnet (prefix), and the subnet is what tells Danbyte the VRF and site the address lives in. Typing just 1.1.1.1/24 isn't enough - nothing in that string says which VRF or which site it belongs to.

So the form opens with a Subnet picker. To find the right one quickly:

1. (Optional) narrow by Site and/or VRF.
2. Pick the Subnet - the list filters to subnets in that site/VRF.
3. The network part of the address is filled in for you; just type the host part. A subnet that holds IP ranges offers a Range field - pick one to get its free addresses as one-click picks and a Next free button. On a subnet that allocates only from its ranges the pick is required and an address outside every range is refused.
4. Set status, role, DNS name, etc., and save.

Tunnel and transit networks between sites¶

A point-to-point network - a WireGuard, GRE or IPsec tunnel, a WAN link, a router-to-router transit /30 - has ends at two sites, so it belongs to neither. Leave the prefix's site empty: it then sits in the shared space, and the subnet pickers list it for a device at any site alongside that site's own subnets. A prefix that was given a site still works from the other end - pick Any site in the picker's site filter and it appears; the API never refused it.

Assign an existing IP¶

Click Assign IP to open the picker. Because a large network can hold millions of addresses, the picker never lists them all - you narrow it down:

1. Filter by Site, VRF, and/or Subnet.
2. Or type part of an address or DNS name in the search box.
3. Pick the address from the (capped) results list and click Assign.

If the IP was attached somewhere else, the picker shows you where - assigning it here moves it.

Seeing what's attached¶

Wherever interfaces are listed, the IP addresses column shows the addresses on each port, so it's obvious which interfaces are in use. The interface detail page's IP addresses tab lists that port's addresses in the full IP table - the same columns, designation menu and buttons as the device's IPs tab. See The interface detail page.

Switch / switch-port link (L2 edge)¶

Separately from the interface an IP is configured on (above), you can record which access switch and physical port a host is reached through - the L2 edge. Two columns, Switch and Switch port, appear on the IP table (on a device's or an interface's IP tab they start hidden - turn them on in the Columns menu), and the IP form has a Switch device picker with a dependent Switch port dropdown (pick the switch - or a stack member - then its port). Setting the port keeps the switch in sync with the port's device; a virtual chassis is shown alongside the port when the device is a stack member. Set it manually, or via the API (switch_id / switch_interface_id on /api/ips/).

Discovering it from SNMP (accept manually)¶

Danbyte can suggest the switch/port from a switch's SNMP data - it never writes it automatically (Danbyte is your source of truth). Polling a switch collects its ARP table (IP → MAC) and its MAC-address / bridge-forwarding table (MAC → port); joining them yields "IP 10.0.0.5 is behind SW1 · Gi0/1". These appear as switch link suggestions in the switch device's SNMP drift inbox (Device → SNMP), where you Accept each one (or Sync all) exactly like other discovered facts. Accepting sets the IP's Switch + Switch port. This runs through the normal SNMP path, so it works both locally and via Outposts.