Driver Atlas

Network Hub

A network branch for adapter identity, radio and firmware boundaries, interfaces, links, protocols, and lifecycle states.

Separate adapter, radio, and link

The network-adapter lifecycle page begins with the component that exposes a host-facing interface, then separates that component from the link it currently carries. A link is not an adapter. The Wi-Fi lifecycle page adds a radio and its relationship to firmware. These words can occur in one description without naming the same object.

“Network” might mean a physical adapter, a wireless radio, an interface, a protocol, or an application-facing connection. A clear statement identifies which one is meant. A visible link can tell us about transport state; it does not by itself prove that every higher-level protocol or application path is ready.

Read lifecycle as a sequence of records

The lifecycle pages use identity, matching, association, interface publication, power, link state, and runtime relationship as separate pieces of a timeline. A candidate adapter record can be known before an interface is published. Time matters here. Links change. A link can change while the adapter identity remains the same. This vocabulary describes relationships rather than prescribing changes to a computer.

The Wi-Fi route keeps radio firmware beside, rather than inside, host metadata. A wireless path can involve an adapter, radio, firmware element, interface, transport convention, and protocol. When a source says “the network is unavailable,” the useful next question is which of those layers the statement actually names.

Compare adjacent hardware paths

The computer guide provides broader context for network adapters, Wi-Fi, USB, and lifecycle records. The glossary supplies hardware ID, bus, endpoint, firmware, protocol, and driver. Together they make a chain from an identified component to the messages it carries without pretending that the chain is one object.

Printer wireless pages offer a related example: discovery, address, transport, queue, and renderer meet around a print path. That relationship resembles an adapter path but is not identical to it. Layers remain separate. Comparing them clarifies ownership. The adapter exposes a network interface; the printer queue uses a path for ordered output; each has its own state and capability vocabulary.