IFMEDIA(4)

NAME
ifmedia - network interface media settings

SYNOPSIS
#include <sys/socket.h>
#include <net/if.h>
#include <net/if_media.h>

DESCRIPTION
The ifmedia interface provides a consistent method for querying and setting network inerface media and media options. The media is typically set using the ifconfig(8) command.

There are currently three link types supported by ifmedia:

IFM_ETHER
    Ethernet

IFM_TOKEN
    Token Ring

IFM_FDDI
    FDDI

The following sections describe the possible media settings for each link type. Not all of these are supported by every device; refer to your device's manual page for more information.

The lists below provide the possible names of each media type or option. The first name in the list is the canonical name of the media type or option. Additional names are acceptable aliases for the media type or option.

COMMON MEDIA TYPES AND OPTIONS
The followng media types are shared by all link types:

IFM_AUTO
    Autoselect the best media. [autoselect, auto]

IFM_MANUAL
    Jumper or switch on device selects media. [manual]

IFM_NONE
    Deselect all media. [none]

The following media options are shared by all link types:

IFM_FDX
    Place the device into full-duplex mode. This option only has meaning if the device is normally not full-duplex. [full-duplex, fdx]

IFM_HDX
    Place the device into half-duplex mode. This option only has meaning if the device is normally not half-duplex. [half-duplex, hdx]

IFM_FLAG0
    Driver-defined flag. [flag0]

IFM_FLAG1
    Driver-defined flag. [flag1]

IFM_FLAG2
    Driver-defined flag. [flag2]

IFM_LOOP
    Place the device into hardware loopback mode. [loopback, hw-loopback, loop]

MEDIA TYPES AND OPTIONS FOR ETHERNET
The following media types are defined for Ethernet:

IFM_10_T
    10baseT, 10Mb/s over unshielded twisted pair, RJ45 connector. [10baseT, UTP, 10UTP]

IFM_10_2
    10base2, 10Mb/s over coaxial cable, BNC connector, also called Thinnet. [10base2, BNC, 10BNC]

IFM_10_5
    10base5, 10Mb/s over 15-wire cables, DB15 connector, also called AUI. [10base5, AUI, 10AUI]

IFM_100_TX
    100baseTX, 100Mb/s over unshielded twisted pair, RJ45 connector. [100baseTX, 100TX]

IFM_100_FX
    100baseFX, 100Mb/s over fiber optic cables. [100baseFX, 100FX]

IFM_100_T4
    100baseT4, 100Mb/s over 4-wire (category 3) unshielded twisted pair, RJ45 connector. [100baseT4, 100T4]

IFM_100_VG
    100baseVG AnyLAN. [100baseVG, 100VG]

IFM_100_T2
    100baseT2. [100baseT2, 100T2]

IFM_1000_FX
    1000baseFX, 1Gb/s over fiber optic cables. [1000baseFX, 1000FX]

IFM_10_STP
    10baseSTP, 10Mb/s over shielded twisted pair, DB9 connector. [10baseSTP, STP, 10STP]

IFM_10_FL
    10baseFL, 10Mb/s over fiber optic cables. [10baseFL, FL, 10FL]

There are no link type-specific options defined for Ethernet.

MEDIA TYPES AND OPTIONS FOR TOKEN RING
The following media types are defined for Token Ring:

IFM_TOK_STP4
    4Mb/s, shielded twisted pair, DB9 connector. [DB9/4Mbit, 4STP]

IFM_TOK_STP16
    16Mb/s, shielded twisted pair, DB9 connector. [DB9/16Mbit, 16STP]

IFM_TOK_UTP4
    4Mb/s, unshielded twisted pair, RJ45 connector. [UTP/4Mbit, 4UTP]

IFM_TOK_UTP16
    16Mb/s, unshielded twisted pair, RJ45 connector. [UTP/16Mbit, 16UTP]

The following media options are defined for Token Ring:

IFM_TOK_ETR
    Early token release. [EarlyTokenRelease, ETR]

IFM_TOK_SRCRT
    Enable source routing features. [SourceRouting, SRCRT]

IFM_TOK_ALLR
    All routes vs. single route broadcast. [AllRoutes, ALLR]

MEDIA TYPES AND OPTIONS FOR FDDI
The following media types are defined for FDDI:

IFM_FDDI_SMF
    Single-mode fiber. [Single-mode, SMF]

IFM_FDDI_MMF
    Multi-mode fiber. [Multi-mode, MMF]

IFM_FDDI_UTP
    Unshielded twisted pair, RJ45 connector. [UTP, CDDI]

The following media options are defined for FDDI:

IFM_FDDI_DA
    Dual-attached station vs. Single-attached station. [dual-attach, das]

SEE ALSO
ifconfig(8), netintro(4)

HISTORY
The ifmedia interface first appeared in BSD/OS 3.0. The implementation that appeared in NetBSD 1.3 was written by Jonathan Stone and Jason R. Thorpe to be compatible with the BSDI API. It has since gone through several revisions which have extended the API while maintaining backwards compatibility with the original API.