MERIDIAN DATA SYSTEMS // TERMINAL

ip

DOCUMENT TYPE: SYSTEM REFERENCE NODE: ip 68 DOCUMENTS
MDS://KNOWLEDGE/TERMINAL/ip
Inspect and configure local network interfaces, IPv4 addresses, and routes.

Usage:
    ip link [show] [dev <interface>]
    ip addr [show] [dev <interface>]
    ip route [show]
    ip link set dev <interface> up|down
    ip addr add|del <IPv4/prefix> dev <interface>
    ip route add <network/prefix|default> via <gateway> dev <interface>
    ip route del <network/prefix|default>

ip link shows interface names, MAC addresses, and up/down states.
The network line identifies the attached virtual LAN. Game staff manage
network membership; local root manages addresses and interface state.
ip addr also shows assigned IPv4 addresses in CIDR notation.
ip route shows the configured default gateway and connected subnets.
Routes on a down interface are marked linkdown.

Root can configure Ethernet interfaces; all local users can inspect them.
Example configuration:
    ip link set dev eth0 up
    ip addr add 10.0.0.2/24 dev eth0
    ip route add default via 10.0.0.1 dev eth0

Addresses need a numeric CIDR prefix. Gateways must be another host on an
assigned subnet of the selected interface. Remove a dependent default
gateway before deleting its last supporting address. Interface-down state
preserves addresses and routes. Configuration survives logins and restarts.

The loopback interface lo starts up at 127.0.0.1/8. The Ethernet
interface eth0 starts down without an IPv4 address or a route.
Loopback configuration is fixed.
Static routes use a network address and numeric CIDR prefix. The longest
matching route wins, with connected routes preferred for equal prefixes.
Enable packet forwarding with sysctl -w net.ipv4.ip_forward=1.