Nodes and Public IPs

简体中文 | English

Node Status

The node list provides a quick view of online Agents and each node's currently usable public IPs. A node is online when its Agent has reported within two minutes. Select any row to open node details. The list exposes only common immediate actions; full configuration is organized in tabs on the detail page.

Disabling a node stops polling work and local schedules after the Agent receives the configuration. Revoking credentials permanently disconnects that Agent. Deleting a node removes Center-managed node configuration and hidden discovery paths, but it does not uninstall the Agent or delete reports and address history already assigned to public IPs.

Automatic Public-Egress Discovery

The Agent discovers usable default routes and stable routable local sources, then confirms the actual egress through multiple public-IP discovery services. The product object is a public IP, not an interface, route, or local address:

• several interfaces, local addresses, or NAT mappings that produce one public IP are shown as one public IP;
• the same public IP found by several nodes or proxies reuses one IP identity and its existing reports;
• NAT relationships can show the local path to its public egress, while selectors and hidden paths remain internal;
• temporary IPv6 privacy addresses do not become independent durable objects; and
• a newly confirmed public IP is enabled for recurring complete probes by default.

Rediscovery runs every ten minutes by default. Only set entry, set exit, check failure, recovery, and queue-gap events are recorded. Unchanged checks do not continually create history.

Current and Historical Addresses

The Public IPs tab places active addresses first. A current address can be enabled or disabled for recurring complete probes, probed once immediately, and opened to view existing results.

Historical addresses are visually separated. They no longer have a usable execution path, so they cannot be probed again, but their past reports and address changes remain available. If the same IP reappears later, IPChronicle reconnects it to the existing IP identity and history rather than creating a parallel record.

It is expected for a dynamic connection to create separate identities and reports for different public IP values. Snapshot comparisons remain within one public IP and never treat two distinct addresses as the same probe subject.