This machine (routes, DHCP lease, interfaces)

What it does: how THIS computer is connected, in three tabs — Routes, DHCP lease and Interfaces (it was two tools — Routing table and DHCP lease).

Routes: the IP routing table — the rules the OS uses to decide where each packet goes. Each row is a destination (a network or host), the gateway / next-hop it's sent to, the interface it leaves by, and a metric (lower wins when two routes overlap); the "default" route is the catch-all, normally your gateway to the internet.

DHCP lease: whether DHCP is on, the DHCP server, and the assigned IP / gateway / DNS. Lease times: obtained and expires on Windows (ipconfig /all); renew and expiry, or the lifetime, on Linux (dhclient / systemd-networkd / NetworkManager lease files). The raw record is shown underneath.

Interfaces: the up interfaces at a glance — type, speed, IPv4, gateway, MAC (Field Kit ▸ Interfaces has the full side-by-side compare).

What you need: nothing — press Refresh on a tab. No admin rights needed, and nothing leaves your machine. Routes reads the live table (Windows: route print; Linux: /proc/net/route and /proc/net/ipv6_route). On some Linux setups the lease files need root to read; if so, the tab still shows the server and addresses.

Safe to run: yes — it only reads.

What to expect / reading results: Routes — look at the default route first: is its gateway the one you expect? A surprise default (or a second one with a lower metric) is a classic cause of traffic "going the wrong way" — e.g. a VPN or a second NIC quietly taking over; a MISSING route explains why a destination is unreachable even though the link is up. DHCP lease — check the DHCP server is the one you expect: a lease from a ROGUE or wrong server (a mis-plugged home router, a second server on the VLAN) is a common cause of "I got the wrong IP / gateway / DNS." A very short lease, or one that won't renew, points at an exhausted scope or a reachability problem to the server.