Network Interfaces, IP Addresses, and Host Identity

Learning Question

What is the relationship between a host, a network interface, a NIC, and an IP address?

A host does not participate in a network through an abstract identity alone. The operating system uses network interfaces. An IP address is assigned to an interface. A physical NIC may provide the hardware behind an interface, but the interface is the operating-system object used for network decisions.

Physical Hardware and OS Interface

A NIC is physical network hardware. It sends and receives link-layer frames and physical signals.

A network interface is the operating-system-managed networking object:

OS TCP/IP stack
-> network interface: Ethernet, Wi-Fi, loopback, VPN, bridge, veth
-> driver or virtual implementation
-> NIC hardware or virtual path

Some interfaces are backed by physical NICs. Others are virtual. This is why “the NIC’s IP address” is often imprecise. More accurately:

An IP address is assigned to a network interface.
The interface may be backed by a physical NIC.

IP Address and MAC Address

IP addresses and MAC addresses belong to different roles.

IP address  = network-layer logical address
MAC address = link-layer address on the current link

When a host sends traffic to a remote server, the IP packet keeps the final destination IP address. The local frame, however, is addressed to the next device on the current link.

For a remote destination, that next device is usually the gateway:

IP packet destination: final server IP
frame destination:    gateway MAC address

This distinction prevents a common confusion: IP identifies where the packet is meant to go across networks, while MAC addresses are used for local link delivery.

Multiple Interfaces

A host can have more than one interface:

Wi-Fi:    192.168.1.30/24
Ethernet: 10.0.0.20/24
VPN:      172.16.5.10/24
Loopback: 127.0.0.1

When the host sends traffic, the route lookup chooses an outgoing interface. The chosen interface determines the source address, local link, and next-hop resolution path.

Core Mental Model

Do not treat “the host’s IP” as a single permanent identity. A host can have multiple network interfaces, and each interface can have its own addresses and local reachability.

The practical model is:

host
-> operating system network stack
-> selected network interface
-> source IP and route context
-> link-layer delivery through hardware or a virtual path