This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| ifconfig | |
|---|---|
| Name | ifconfig |
| Developer | Berkeley Software Distribution |
| Released | 1980s |
| Latest release | varies by implementation |
| Operating system | UNIX-like |
| Genre | Network configuration utility |
| License | BSD license |
ifconfig
ifconfig is a command-line network interface configuration utility historically provided in Berkeley Software Distribution and widely used in Unix and Linux environments. It configures and queries network interfaces in computer networking stacks implemented by operating systems such as FreeBSD, OpenBSD, NetBSD, SunOS, AIX, and early Linux distributions. as part of the BSD networking stack and legacy net-tools collections, it influenced tools in projects like NetworkManager, systemd, and network management suites used in enterprises such as Red Hat, Debian, Ubuntu, SUSE, and vendors like Cisco Systems and Juniper Networks.
ifconfig originated in the BSD 4.2 era as a userland tool to manage interfaces in the UNIX networking subsystem created by researchers at the University of California, Berkeley. Early development paralleled work by authors of TCP/IP implementations including Jon Postel and developers associated with the DARPA TCP/IP research community. The utility was distributed with BSD variants and later adopted into the net-tools package maintained by contributors from projects such as Red Hat and Debian. Over time, maintenance shifted as new stacks like the Linux kernel’s NETLINK subsystem emerged, and modern initiatives in systemd and distributions including Fedora and Arch Linux promoted tools like iproute2 as successors. Legal and project governance interactions involved entities such as the Free Software Foundation and open-source communities around OpenBSD and NetBSD.
ifconfig configures parameters of network interfaces defined by operating systems such as FreeBSD, NetBSD, OpenBSD, SunOS, and historical Linux distributions. It can assign IP addresses (both IPv4 and, via extensions in some ports, aspects of IPv6), control interface state (up/down), set MTUs and hardware addresses, and query statistics maintained by kernel networking stacks like the one in the Linux kernel or BSD kernel. Administrators at organizations such as Google, Facebook, Amazon (company), Microsoft, IBM and internet service providers historically used ifconfig in scripts and operational runbooks alongside services like DHCP servers from projects such as isc-dhcp and implementations like dhcpcd.
ifconfig syntax varies by implementation across BSD and System V derivatives and legacy Linux net-tools. Typical invocations include specifying an interface name such as eth0, em0, enp3s0 or lo and flags indicating actions. Common options for many ports include: - interface name and address specification: interface followed by an IPv4 address and netmask or prefix. - state control: commands or flags to bring an interface up or down, enable multicast or promisc modes, manage ARP behavior. - hardware configuration: set MAC address and MTU values. Different distributions and vendors add options unique to stacks maintained by teams at Cisco Systems, Juniper Networks, Oracle Corporation (for Solaris), and platform projects such as FreeBSD’s network stack. Compatibility differences appear when comparing behavior to tools used by systemd’s networking components or the iproute2 suite maintained by contributors affiliated with Alexey Kuznetzov and others in the Linux networking community.
Common examples historically used by administrators in organizations like MIT, Stanford University, NASA, CERN, and corporate infrastructures: - Bring interface up: specify interface name then the keyword up to activate the interface according to kernel routing tables and link state managed by drivers maintained by vendors such as Intel Corporation and Broadcom. - Assign address and netmask: supply an IPv4 address and mask; some BSD variants accept prefix notation native to that kernel networking implementation used at institutions like Bell Labs. - Set MTU and enable promiscuous mode useful in packet capture scenarios with tools from projects such as tcpdump or Wireshark during research conducted at labs like Los Alamos National Laboratory. Examples vary across AIX and Solaris where administrative guides from vendors like IBM and Oracle Corporation describe platform-specific flags and integration with services such as SMF or legacy init scripts used by Sun Microsystems.
ifconfig remains available and supported in many BSD projects including OpenBSD, NetBSD, and FreeBSD, where it is integrated into their respective kernels and userlands maintained by developer communities and organizations such as the OpenBSD Foundation and the NetBSD Foundation. On modern Linux distributions, iproute2 (the ip command) has superseded ifconfig for kernel interfaces using NETLINK; major distributions such as Debian, Ubuntu, Fedora, and Red Hat Enterprise Linux have deprecated net-tools in favor of iproute2. Vendors and projects like Canonical, SUSE, Red Hat, and enterprise teams at Google provide migration guidance, while some legacy network management scripts and embedded systems continue to use ifconfig provided by packages in repositories for backward compatibility.
Prominent alternatives and successors include: - ip (from iproute2), used broadly on Linux and developed by contributors in the Linux networking community including Alexey Kuznetzov. - ifconfig equivalents and wrappers in OpenBSD, FreeBSD, and NetBSD maintained by their respective developer communities. - Network management suites and daemons such as NetworkManager (used by GNOME Project and distributions like Fedora), systemd-networkd from the systemd project, and vendor tools by Cisco Systems and Juniper Networks. - Higher-level orchestration and cloud networking tools used by Amazon Web Services, Google Cloud Platform, and Microsoft Azure that programmatically manage interfaces via APIs rather than direct ifconfig calls. Category:Unix network administration