ip-address

title: ip-address(8)

summary: protocol address management

text:
# ip-address(8)

## NAME
ip-address - protocol address management

## SYNOPSIS

ip [ OPTIONS ] address { COMMAND | help }

ip address { add | change | replace } IFADDR dev IFNAME [ LIFETIME ] [ CONFFLAG-LIST ]

ip address del IFADDR dev IFNAME [ mngtmpaddr ]

ip address { save | flush } [ dev IFNAME ] [ scope SCOPE-ID ] [ metric METRIC ] [ to PREFIX ] [ FLAG-LIST ] [ label PATTERN ] [ up ]

ip address [ show [ dev IFNAME ] [ scope SCOPE-ID ] [ to PREFIX ] [ FLAG-LIST ] [ label PATTERN ] [ master DEVICE ] [ type TYPE ] [ vrf NAME ] [ up ] ]

ip address { showdump | restore }

IFADDR := PREFIX | ADDR peer PREFIX [ broadcast ADDR ] [ anycast ADDR ] [ label LABEL ] [ scope SCOPE-ID ]

SCOPE-ID := [ host | link | global | NUMBER ]

FLAG-LIST := [ FLAG-LIST ] FLAG

FLAG := [ [-]permanent | [-]dynamic | [-]secondary | [-]primary | [-]tentative | [-]deprecated | [-]dadfailed | [-]temporary | CONFFLAG-LIST ]

CONFFLAG-LIST := [ CONFFLAG-LIST ] CONFFLAG

CONFFLAG := [ home | mngtmpaddr | nodad | optimstic | noprefixroute | autojoin ]

LIFETIME := [ valid_lft LFT ] [ preferred_lft LFT ]

LFT := [ forever | SECONDS ]

TYPE := [ bridge | bridge_slave | bond | bond_slave | can | dummy | hsr | ifb | ipoib | macvlan | macvtap | vcan | veth | vlan | vxlan | ip6tnl | ipip | sit | gre | gretap | erspan | ip6gre | ip6gretap | ip6erspan | vti | vrf | nlmon | ipvlan | lowpan | geneve | macsec ]

## DESCRIPTION
The address is a protocol (IPv4 or IPv6) address attached to a network device. Each device must have at least one address to use the corresponding protocol. It is possible to have several different addresses attached to one device. These addresses are not discriminated, so that the term alias is not quite appropriate for them and we do not use it in this document.

The ip address command displays addresses and their properties, adds new addresses and deletes old ones.

### ip address add - add new protocol address.
dev IFNAME

the name of the device to add the address to.

local ADDRESS (default)

the address of the interface. The format of the address depends on the protocol. It is a dotted quad for IP and a sequence of hexadecimal halfwords separated by colons for IPv6. The ADDRESS may be followed by a slash and a decimal number which encodes the network prefix length.

peer ADDRESS

the address of the remote endpoint for pointopoint interfaces. Again, the ADDRESS may be followed by a slash and a decimal number, encoding the network prefix length. If a peer address is specified, the local address cannot have a prefix length. The network prefix is associated with the peer rather than with the local address.

broadcast ADDRESS

the broadcast address on the interface. It is possible to use the special symbols '+' and '-' instead of the broadcast address. In this case, the broadcast address is derived by setting/resetting the host bits of the interface prefix.

label LABEL

Each address may be tagged with a label string. In order to preserve compatibility with Linux-2.0 net aliases, this string must coincide with the name of the device or must be prefixed with the device name followed by colon. The maximum allowed total length of label is 15 characters.

scope SCOPE_VALUE

the scope of the area where this address is valid. The available scopes are listed in file /etc/iproute2/rt_scopes. Predefined scope values are:

global - the address is globally valid.

site - (IPv6 only, deprecated) the address is site local, i.e. it is valid inside this site.

link - the address is link local, i.e. it is valid only on this device.

host - the address is valid only inside this host.

metric NUMBER

priority of prefix route associated with address.

valid_lft LFT

the valid lifetime of this address; see section 5.5.4 of RFC 4862. When it expires, the address is removed by the kernel. Defaults to forever.

preferred_lft LFT

the preferred lifetime of this address; see section 5.5.4 of RFC 4862. When it expires, the address is no longer used for new outgoing connections. Defaults to forever.

home

(IPv6 only) designates this address the "home address" as defined in RFC 6275.

mngtmpaddr

(IPv6 only) make the kernel manage temporary addresses created from this one as template on behalf of Privacy Extensions (RFC3041). For this to become active, the use_tempaddr sysctl setting has to be set to a value greater than zero. The given address needs to have a prefix length of 64. This flag allows to use privacy extensions in a manually configured network, just like if stateless auto-configuration was active.

nodad

(IPv6 only) do not perform Duplicate Address Detection (RFC 4862) when adding this address.

optimistic

(IPv6 only) When performing Duplicate Address Detection, use the RFC 4429 optimistic variant.

noprefixroute

Do not automatically create a route for the network prefix of the added address, and don't search for one to delete when removing the address. Changing an address to add this flag will remove the automatically added prefix route, changing it to remove this flag will create the prefix route automatically.

autojoin

Joining multicast groups on Ethernet level via ip maddr command does not work if connected to an Ethernet switch that does IGMP snooping since the switch would not replicate multicast packets on ports that did not have IGMP reports for the multicast addresses. Linux VXLAN interfaces created via ip link add vxlan have the group option that enables them to do the required join.

Using the autojoin flag when adding a multicast address enables similar functionality for Openvswitch VXLAN interfaces as well as other tunneling mechanisms that need to receive multicast traffic.

### ip address delete - delete protocol address
Arguments: coincide with the arguments of ip addr add. The device name is a required argument. The rest are optional. If no arguments are given, the first address is deleted.

### ip address show - look at protocol addresses
dev IFNAME (default)

name of device.

scope SCOPE_VAL

only list addresses with this scope.

to PREFIX

only list addresses matching this prefix.

label PATTERN

only list addresses with labels matching the PATTERN. PATTERN is a usual shell style pattern.

master DEVICE

only list interfaces enslaved to this master device.

vrf NAME

only list interfaces enslaved to this vrf.

type TYPE

only list interfaces of the given type. Note that the type name is not checked against the list of supported types - instead it is sent as-is to the kernel. Later it is used to filter the returned interface list by comparing it with the relevant attribute in case the kernel didn't filter already. Therefore any string is accepted, but may lead to empty output.

up

only list running interfaces.

dynamic and permanent

(IPv6 only) only list addresses installed due to stateless address configuration or only list permanent (not dynamic) addresses. These two flags are inverses of each other, so -dynamic is equal to permanent and -permanent is equal to dynamic.

tentative

(IPv6 only) only list addresses which have not yet passed duplicate address detection.

-tentative

(IPv6 only) only list addresses which are not in the process of duplicate address detection currently.

deprecated

(IPv6 only) only list deprecated addresses.

-deprecated

(IPv6 only) only list addresses not being deprecated.

dadfailed

(IPv6 only) only list addresses which have failed duplicate address detection.

-dadfailed

(IPv6 only) only list addresses which have not failed duplicate address detection.

temporary or secondary

List temporary IPv6 or secondary IPv4 addresses only. The Linux kernel shares a single bit for those, so they are actually aliases for each other although the meaning differs depending on address family.

-temporary or -secondary

These flags are aliases for primary.

primary

List only primary addresses, in IPv6 exclude temporary ones. This flag is the inverse of temporary and secondary.

-primary

This is an alias for temporary or secondary.

### ip address flush - flush protocol addresses
This command flushes the protocol addresses selected by some criteria.

This command has the same arguments as show except that type and master selectors are not supported. Another difference is that it does not run when no arguments are given.

Warning: This command and other flush commands are unforgiving. They will cruelly purge all the addresses.

With the -statistics option, the command becomes verbose. It prints out the number of deleted addresses and the number of rounds made to flush the address list. If this option is given twice, ip address flush also dumps all the deleted addresses in the format described in the previous subsection.

## EXAMPLES
ip address show

Shows IPv4 and IPv6 addresses assigned to all network interfaces. The 'show' subcommand can be omitted.

ip address show up

Same as above except that only addresses assigned to active network interfaces are shown.

ip address show dev eth0

Shows IPv4 and IPv6 addresses assigned to network interface eth0.

ip address add 2001:0db8:85a3::0370:7334/64 dev eth1

Adds an IPv6 address to network interface eth1.

ip address delete 2001:0db8:85a3::0370:7334/64 dev eth1

Delete the IPv6 address added above.

ip address flush dev eth4 scope global

Removes all global IPv4 and IPv6 addresses from device eth4. Without 'scope global' it would remove all addresses including IPv6 link-local ones.

## SEE ALSO
ip(8)

## AUTHOR
Original Manpage by Michail Litvak <mci@owl.openwall.com>


ip-addrlabel

title: ip-addrlabel(8)

summary: protocol address label management

text:
# ip-addrlabel(8)

## NAME
ip-addrlabel - protocol address label management

## SYNOPSIS

ip addrlabel { COMMAND | help }

ip addrlabel { add | del } prefix PREFIX [ dev DEV ] [ label NUMBER ]

ip addrlabel { list | flush }

## DESCRIPTION
IPv6 address labels are used for address selection; they are described in RFC 3484. Precedence is managed by userspace, and only the label itself is stored in the kernel.

### ip addrlabel add - add an address label
add an address label entry to the kernel.

prefix PREFIX

dev DEV

the outgoing interface.

label NUMBER

the label for the prefix. 0xffffffff is reserved.

### ip addrlabel del - delete an address label
delete an address label entry from the kernel. Arguments: coincide with the arguments of ip addrlabel add but the label is not required.

### ip addrlabel list - list address labels
list the current address label entries in the kernel.

### ip addrlabel flush - flush address labels
flush all address labels in the kernel. This does not restore any default settings.

## SEE ALSO
ip(8)

## AUTHOR
Manpage by Yoshifuji Hideaki / 吉藤英明


ip-fou

title: ip-fou(8)

summary: Foo-over-UDP receive port configuration

text:
# ip-fou(8)

## NAME
ip-fou - Foo-over-UDP receive port configuration

ip-gue - Generic UDP Encapsulation receive port configuration

## SYNOPSIS

ip [ OPTIONS ] fou { COMMAND | help }

ip fou add port PORT { gue | ipproto PROTO } [ local IFADDR ] [ peer IFADDR ] [ peer_port PORT ] [ dev IFNAME ]

ip fou del port PORT [ local IFADDR ] [ peer IFADDR ] [ peer_port PORT ] [ dev IFNAME ]

ip fou show

## DESCRIPTION
The ip fou commands are used to create and delete receive ports for Foo-over-UDP (FOU) as well as Generic UDP Encapsulation (GUE).

Foo-over-UDP allows encapsulating packets of an IP protocol directly over UDP. The receiver infers the protocol of a packet received on a FOU UDP port to be the protocol configured for the port.

Generic UDP Encapsulation (GUE) encapsulates packets of an IP protocol within UDP and an encapsulation header. The encapsulation header contains the IP protocol number for the encapsulated packet.

When creating a FOU or GUE receive port, the port number is specified in PORT argument. If FOU is used, the IP protocol number associated with the port is specified in PROTO argument. You can bind a port to a local address/interface, by specifying the address in the local IFADDR argument or the device in the IFNAME argument. If you would like to connect the port, you can specify the peer address in the peer IFADDR argument and peer port in the peer_port PORT argument.

A FOU or GUE receive port is deleted by specifying PORT in the delete command, as well as local address/interface or peer address/port (if set).

## EXAMPLES

### Configure a FOU receive port for GRE bound to 7777

```
# ip fou add port 7777 ipproto 47
```

### Configure a FOU receive port for IPIP bound to 8888

```
# ip fou add port 8888 ipproto 4
```

### Configure a GUE receive port bound to 9999

```
# ip fou add port 9999 gue
```

### Delete the GUE receive port bound to 9999

```
# ip fou del port 9999
```

### Configure a FOU receive port for GRE bound to 1.2.3.4:7777

```
# ip fou add port 7777 ipproto 47 local 1.2.3.4
```

## SEE ALSO
ip(8)

## AUTHOR
Tom Herbert <therbert@google.com>


title: ip-l2tp(8)

text:
# ip-l2tp(8)

## NAME
ip-l2tp - L2TPv3 static unmanaged tunnel configuration

## SYNOPSIS

ip [ OPTIONS ] l2tp { COMMAND | help }

ip l2tp add tunnel

remote ADDR local ADDR

tunnel_id ID peer_tunnel_id ID

[ encap { ip | udp } ]

[ udp_sport PORT ] [ udp_dport PORT ]

[ udp_csum { on | off } ]

[ udp6_csum_tx { on | off } ]

[ udp6_csum_rx { on | off } ]

ip l2tp add session [ name NAME ]

tunnel_id ID session_id ID peer_session_id ID

[ cookie HEXSTR ] [ peer_cookie HEXSTR ]

[ l2spec_type { none | default } ]

[ seq { none | send | recv | both } ]

ip l2tp del tunnel tunnel_id ID

ip l2tp del session tunnel_id ID session_id ID

ip l2tp show tunnel [ tunnel_id ID ]

ip l2tp show session [ tunnel_id ID.B ] [ session_id ID ]

NAME := STRING ADDR := { IP_ADDRESS | any } PORT := { NUMBER } ID := { NUMBER } HEXSTR := { 8 or 16 hex digits (4 / 8 bytes) }

## DESCRIPTION
The ip l2tp commands are used to establish static, or so-called unmanaged L2TPv3 ethernet tunnels. For unmanaged tunnels, there is no L2TP control protocol so no userspace daemon is required - tunnels are manually created by issuing commands at a local system and at a remote peer.

L2TPv3 is suitable for Layer-2 tunneling. Static tunnels are useful to establish network links across IP networks when the tunnels are fixed. L2TPv3 tunnels can carry data of more than one session. Each session is identified by a session_id and its parent tunnel's tunnel_id. A tunnel must be created before a session can be created in the tunnel.

When creating an L2TP tunnel, the IP address of the remote peer is specified, which can be either an IPv4 or IPv6 address. The local IP address to be used to reach the peer must also be specified. This is the address on which the local system will listen for and accept received L2TP data packets from the peer.

L2TPv3 defines two packet encapsulation formats: UDP or IP. UDP encapsulation is most common. IP encapsulation uses a dedicated IP protocol value to carry L2TP data without the overhead of UDP. Use IP encapsulation only when there are no NAT devices or firewalls in the network path.

When an L2TPv3 ethernet session is created, a virtual network interface is created for the session, which must then be configured and brought up, just like any other network interface. When data is passed through the interface, it is carried over the L2TP tunnel to the peer. By configuring the system's routing tables or adding the interface to a bridge, the L2TP interface is like a virtual wire (pseudowire) connected to the peer.

Establishing an unmanaged L2TPv3 ethernet pseudowire involves manually creating L2TP contexts on the local system and at the peer. Parameters used at each site must correspond or no data will be passed. No consistency checks are possible since there is no control protocol used to establish unmanaged L2TP tunnels. Once the virtual network interface of a given L2TP session is configured and enabled, data can be transmitted, even if the peer isn't yet configured. If the peer isn't configured, the L2TP data packets will be discarded by the peer.

To establish an unmanaged L2TP tunnel, use l2tp add tunnel and l2tp add session commands described in this document. Then configure and enable the tunnel's virtual network interface, as required.

Note that unmanaged tunnels carry only ethernet frames. If you need to carry PPP traffic (L2TPv2) or your peer doesn't support unmanaged L2TPv3 tunnels, you will need an L2TP server which implements the L2TP control protocol. The L2TP control protocol allows dynamic L2TP tunnels and sessions to be established and provides for detecting and acting upon network failures.

### ip l2tp add tunnel - add a new tunnel
tunnel_id ID

set the tunnel id, which is a 32-bit integer value. Uniquely identifies the tunnel. The value used must match the peer_tunnel_id value being used at the peer.

peer_tunnel_id ID

set the peer tunnel id, which is a 32-bit integer value assigned to the tunnel by the peer. The value used must match the tunnel_id value being used at the peer.

remote ADDR

set the IP address of the remote peer. May be specified as an IPv4 address or an IPv6 address.

local ADDR

set the IP address of the local interface to be used for the tunnel. This address must be the address of a local interface. May be specified as an IPv4 address or an IPv6 address.

encap ENCAP

set the encapsulation type of the tunnel.

Valid values for encapsulation are: udp, ip.

udp_sport PORT

set the UDP source port to be used for the tunnel. Must be present when udp encapsulation is selected. Ignored when ip encapsulation is selected.

udp_dport PORT

set the UDP destination port to be used for the tunnel. Must be present when udp encapsulation is selected. Ignored when ip encapsulation is selected.

udp_csum STATE

(IPv4 only) control if IPv4 UDP checksums should be calculated and checked for the encapsulating UDP packets, when UDP encapsulating is selected. Default is off.

Valid values are: on, off.

udp6_csum_tx STATE

(IPv6 only) control if IPv6 UDP checksums should be calculated for encapsulating UDP packets, when UDP encapsulating is selected. Default is on.

Valid values are: on, off.

udp6_csum_rx STATE

(IPv6 only) control if IPv6 UDP checksums should be checked for the encapsulating UDP packets, when UDP encapsulating is selected. Default is on.

Valid values are: on, off.

### ip l2tp del tunnel - destroy a tunnel
tunnel_id ID

set the tunnel id of the tunnel to be deleted. All sessions within the tunnel must be deleted first.

### ip l2tp show tunnel - show information about tunnels
tunnel_id ID

set the tunnel id of the tunnel to be shown. If not specified, information about all tunnels is printed.

### ip l2tp add session - add a new session to a tunnel
name NAME

sets the session network interface name. Default is l2tpethN.

tunnel_id ID

set the tunnel id, which is a 32-bit integer value. Uniquely identifies the tunnel into which the session will be created. The tunnel must already exist.

session_id ID

set the session id, which is a 32-bit integer value. Uniquely identifies the session being created. The value used must match the peer_session_id value being used at the peer.

peer_session_id ID

set the peer session id, which is a 32-bit integer value assigned to the session by the peer. The value used must match the session_id value being used at the peer.

cookie HEXSTR

sets an optional cookie value to be assigned to the session. This is a 4 or 8 byte value, specified as 8 or 16 hex digits, e.g. 014d3636deadbeef. The value must match the peer_cookie value set at the peer. The cookie value is carried in L2TP data packets and is checked for expected value at the peer. Default is to use no cookie.

peer_cookie HEXSTR

sets an optional peer cookie value to be assigned to the session. This is a 4 or 8 byte value, specified as 8 or 16 hex digits, e.g. 014d3636deadbeef. The value must match the cookie value set at the peer. It tells the local system what cookie value to expect to find in received L2TP packets. Default is to use no cookie.

l2spec_type L2SPECTYPE

set the layer2specific header type of the session.

Valid values are: none, default.

seq SEQ

controls sequence numbering to prevent or detect out of order packets. send puts a sequence number in the default layer2specific header of each outgoing packet. recv reorder packets if they are received out of order. Default is none.

Valid values are: none, send, recv, both.

### ip l2tp del session - destroy a session
tunnel_id ID

set the tunnel id in which the session to be deleted is located.

session_id ID

set the session id of the session to be deleted.

### ip l2tp show session - show information about sessions
tunnel_id ID

set the tunnel id of the session(s) to be shown. If not specified, information about sessions in all tunnels is printed.

session_id ID

set the session id of the session to be shown. If not specified, information about all sessions is printed.

## EXAMPLES

### Setup L2TP tunnels and sessions

```
site-A:# ip l2tp add tunnel tunnel_id 3000 peer_tunnel_id 4000 \

           encap udp local 1.2.3.4 remote 5.6.7.8 \

           udp_sport 5000 udp_dport 6000
site-A:# ip l2tp add session tunnel_id 3000 session_id 1000 \

           peer_session_id 2000
site-B:# ip l2tp add tunnel tunnel_id 4000 peer_tunnel_id 3000 \

           encap udp local 5.6.7.8 remote 1.2.3.4 \

           udp_sport 6000 udp_dport 5000
site-B:# ip l2tp add session tunnel_id 4000 session_id 2000 \

           peer_session_id 1000
site-A:# ip link set l2tpeth0 up mtu 1488
site-B:# ip link set l2tpeth0 up mtu 1488
```

Notice that the IP addresses, UDP ports and tunnel / session ids are matched and reversed at each site.

### Configure as IP interfaces
The two interfaces can be configured with IP addresses if only IP data is to be carried. This is perhaps the simplest configuration.

```
site-A:# ip addr add 10.42.1.1 peer 10.42.1.2 dev l2tpeth0
site-B:# ip addr add 10.42.1.2 peer 10.42.1.1 dev l2tpeth0
site-A:# ping 10.42.1.2
```

Now the link should be usable. Add static routes as needed to have data sent over the new link.

### Configure as bridged interfaces
To carry non-IP data, the L2TP network interface is added to a bridge instead of being assigned its own IP address, using standard Linux utilities. Since raw ethernet frames are then carried inside the tunnel, the MTU of the L2TP interfaces must be set to allow space for those headers.

```
site-A:# ip link set l2tpeth0 up mtu 1446
site-A:# ip link add br0 type bridge
site-A:# ip link set l2tpeth0 master br0
site-A:# ip link set eth0 master br0
site-A:# ip link set br0 up
```

If you are using VLANs, setup a bridge per VLAN and bridge each VLAN over a separate L2TP session. For example, to bridge VLAN ID 5 on eth1 over an L2TP pseudowire:

```
site-A:# ip link set l2tpeth0 up mtu 1446
site-A:# ip link add brvlan5 type bridge
site-A:# ip link set l2tpeth0.5 master brvlan5
site-A:# ip link set eth1.5 master brvlan5
site-A:# ip link set brvlan5 up
```

Adding the L2TP interface to a bridge causes the bridge to forward traffic over the L2TP pseudowire just like it forwards over any other interface. The bridge learns MAC addresses of hosts attached to each interface and intelligently forwards frames from one bridge port to another. IP addresses are not assigned to the l2tpethN interfaces. If the bridge is correctly configured at both sides of the L2TP pseudowire, it should be possible to reach hosts in the peer's bridged network.

When raw ethernet frames are bridged across an L2TP tunnel, large frames may be fragmented and forwarded as individual IP fragments to the recipient, depending on the MTU of the physical interface used by the tunnel. When the ethernet frames carry protocols which are reassembled by the recipient, like IP, this isn't a problem. However, such fragmentation can cause problems for protocols like PPPoE where the recipient expects to receive ethernet frames exactly as transmitted. In such cases, it is important that frames leaving the tunnel are reassembled back into a single frame before being forwarded on. To do so, enable netfilter connection tracking (conntrack) or manually load the Linux netfilter defrag modules at each tunnel endpoint.

```
site-A:# modprobe nf_defrag_ipv4
site-B:# modprobe nf_defrag_ipv4
```

If L2TP is being used over IPv6, use the IPv6 defrag module.

## INTEROPERABILITY
Unmanaged (static) L2TPv3 tunnels are supported by some network equipment equipment vendors such as Cisco.

In Linux, L2TP Hello messages are not supported in unmanaged tunnels. Hello messages are used by L2TP clients and servers to detect link failures in order to automate tearing down and reestablishing dynamic tunnels. If a non-Linux peer supports Hello messages in unmanaged tunnels, it must be turned off to interoperate with Linux.

Linux defaults to use the Default Layer2SpecificHeader type as defined in the L2TPv3 protocol specification, RFC3931. This setting must be consistent with that configured at the peer. Some vendor implementations (e.g. Cisco) default to use a Layer2SpecificHeader type of None.

## SEE ALSO
ip(8)

## AUTHOR
James Chapman <jchapman@katalix.com>


ip-link

title: ip-link(8)

summary: network device configuration

text:
# ip-link(8)

## NAME
ip-link - network device configuration

## SYNOPSIS

ip link { COMMAND | help }

ip link add [ link DEVICE ] [ name ] NAME

[ txqueuelen PACKETS ]

[ address LLADDR ] [ broadcast LLADDR ]

[ mtu MTU ] [ index IDX ]

[ numtxqueues QUEUE_COUNT ] [ numrxqueues QUEUE_COUNT ]

[ gso_max_size BYTES ] [ gso_max_segs SEGMENTS ]

type TYPE [ ARGS ]

ip link delete { DEVICE | group GROUP } type TYPE [ ARGS ]

ip link set { DEVICE | group GROUP }

[ { up | down } ]

[ type ETYPE TYPE_ARGS ]

[ arp { on | off } ]

[ dynamic { on | off } ]

[ multicast { on | off } ]

[ allmulticast { on | off } ]

[ promisc { on | off } ]

[ protodown { on | off } ]

[ protodown_reason PREASON { on | off } ]

[ trailers { on | off } ]

[ txqueuelen PACKETS ]

[ name NEWNAME ]

[ address LLADDR ]

[ broadcast LLADDR ]

[ mtu MTU ]

[ netns { PID | NETNSNAME } ]

[ link-netnsid ID ]

[ alias NAME ]

[ vf NUM [ mac LLADDR ]

[ VFVLAN-LIST ]

[ rate TXRATE ]

[ max_tx_rate TXRATE ]

[ min_tx_rate TXRATE ]

[ spoofchk { on | off } ]

[ query_rss { on | off } ]

[ state { auto | enable | disable } ]

[ trust { on | off } ]

[ node_guid eui64 ]

[ port_guid eui64 ] ]

[ { xdp | xdpgeneric | xdpdrv | xdpoffload } { off |

object FILE [ section NAME ] [ verbose ] |

pinned FILE } ]

[ master DEVICE ]

[ nomaster ]

[ vrf NAME ]

[ addrgenmode { eui64 | none | stable_secret | random } ]

[ macaddr [ MACADDR ]

[ { flush | add | del } MACADDR ]

[ set MACADDR ] ]

ip link show [ DEVICE | group GROUP ] [ up ] [ master DEVICE ] [ type ETYPE ] [ vrf NAME ]

ip link xstats type TYPE [ ARGS ]

ip link afstats [ dev DEVICE ]

ip link help [ TYPE ]

TYPE := [ bridge | bond | can | dummy | hsr | ifb | ipoib | macvlan | macvtap | vcan | vxcan | veth | vlan | vxlan | ip6tnl | ipip | sit | gre | gretap | erspan | ip6gre | ip6gretap | ip6erspan | vti | nlmon | ipvlan | ipvtap | lowpan | geneve | bareudp | vrf | macsec | netdevsim | rmnet | xfrm ]

ETYPE := [ TYPE | bridge_slave | bond_slave ]

VFVLAN-LIST := [ VFVLAN-LIST ] VFVLAN

VFVLAN := [ vlan VLANID [ qos VLAN-QOS ] [ proto VLAN-PROTO ] ]

ip link property add dev DEVICE [ altname NAME .. ]

ip link property del dev DEVICE [ altname NAME .. ]

## DESCRIPTION

### ip link add - add virtual link
link DEVICE

specifies the physical device to act operate on. NAME specifies the name of the new virtual device.

TYPE specifies the type of the new device.

Link types:

bridge - Ethernet Bridge device

bond - Bonding device

dummy - Dummy network interface

hsr - High-availability Seamless Redundancy device

ifb - Intermediate Functional Block device

ipoib - IP over Infiniband device

macvlan - Virtual interface base on link layer address (MAC)

macvtap - Virtual interface based on link layer address (MAC) and TAP.

vcan - Virtual Controller Area Network interface

vxcan - Virtual Controller Area Network tunnel interface

veth - Virtual ethernet interface

vlan - 802.1q tagged virtual LAN interface

vxlan - Virtual eXtended LAN

ip6tnl - Virtual tunnel interface IPv4|IPv6 over IPv6

ipip - Virtual tunnel interface IPv4 over IPv4

sit - Virtual tunnel interface IPv6 over IPv4

gre - Virtual tunnel interface GRE over IPv4

gretap - Virtual L2 tunnel interface GRE over IPv4

erspan - Encapsulated Remote SPAN over GRE and IPv4

ip6gre - Virtual tunnel interface GRE over IPv6

ip6gretap - Virtual L2 tunnel interface GRE over IPv6

ip6erspan - Encapsulated Remote SPAN over GRE and IPv6

vti - Virtual tunnel interface

nlmon - Netlink monitoring device

ipvlan - Interface for L3 (IPv6/IPv4) based VLANs

ipvtap - Interface for L3 (IPv6/IPv4) based VLANs and TAP

lowpan - Interface for 6LoWPAN (IPv6) over IEEE 802.15.4 / Bluetooth

geneve - GEneric NEtwork Virtualization Encapsulation

bareudp - Bare UDP L3 encapsulation support

macsec - Interface for IEEE 802.1AE MAC Security (MACsec)

vrf - Interface for L3 VRF domains

netdevsim - Interface for netdev API tests

rmnet - Qualcomm rmnet device

xfrm - Virtual xfrm interface

numtxqueues QUEUE_COUNT

specifies the number of transmit queues for new device.

numrxqueues QUEUE_COUNT

specifies the number of receive queues for new device.

gso_max_size BYTES

specifies the recommended maximum size of a Generic Segment Offload packet the new device should accept.

gso_max_segs SEGMENTS

specifies the recommended maximum number of a Generic Segment Offload segments the new device should accept.

index IDX

specifies the desired index of the new virtual device. The link creation fails, if the index is busy.

VLAN Type Support

For a link of type VLAN the following additional arguments are supported: ip link add link DEVICE name NAME type vlan [ protocol VLAN_PROTO ] id VLANID [ reorder_hdr { on | off } ] [ gvrp { on | off } ] [ mvrp { on | off } ] [ loose_binding { on | off } ] [ bridge_binding { on | off } ] [ ingress-qos-map QOS-MAP ] [ egress-qos-map QOS-MAP ]

protocol VLAN_PROTO - either 802.1Q or 802.1ad.

id VLANID - specifies the VLAN Identifier to use. Note that numbers with a leading " 0 " or " 0x " are interpreted as octal or hexadecimal, respectively.

reorder_hdr { on | off } - specifies whether ethernet headers are reordered or not (default is on).

If reorder_hdr is on then VLAN header will be not inserted immediately but only before passing to the physical device (if this device does not support VLAN offloading), the similar on the RX direction - by default the packet will be untagged before being received by VLAN device. Reordering allows to accelerate tagging on egress and to hide VLAN header on ingress so the packet looks like regular Ethernet packet, at the same time it might be confusing for packet capture as the VLAN header does not exist within the packet.

VLAN offloading can be checked by ethtool(8):

ethtool -k <phy_dev> | grep tx-vlan-offload

where <phy_dev> is the physical device to which VLAN device is bound.

gvrp { on | off } - specifies whether this VLAN should be registered using GARP VLAN

Registration Protocol.

mvrp { on | off } - specifies whether this VLAN should be registered using Multiple VLAN

Registration Protocol.

loose_binding { on | off } - specifies whether the VLAN device state is bound to the physical device state.

bridge_binding { on | off } - specifies whether the VLAN device link state tracks the state of bridge ports that are members of the VLAN.

ingress-qos-map QOS-MAP - defines a mapping of VLAN header prio field to the Linux internal packet priority on incoming frames. The format is FROM:TO with multiple mappings separated by spaces.

egress-qos-map QOS-MAP - defines a mapping of Linux internal packet priority to VLAN header prio field but for outgoing frames. The format is the same as for ingress-qos-map.

Linux packet priority can be set by iptables(8):

iptables -t mangle -A POSTROUTING [...] -j CLASSIFY --set-class 0:4

and this "4" priority can be used in the egress qos mapping to set VLAN prio "5":

ip link set veth0.10 type vlan egress 4:5

VXLAN Type Support

For a link of type VXLAN the following additional arguments are supported: ip link add DEVICE type vxlan id VNI [ dev PHYS_DEV ] [ { group | remote } IPADDR ] [ local { IPADDR | any } ] [ ttl TTL ] [ tos TOS ] [ df DF ] [ flowlabel FLOWLABEL ] [ dstport PORT ] [ srcport MIN MAX ] [ [no]learning ] [ [no]proxy ] [ [no]rsc ] [ [no]l2miss ] [ [no]l3miss ] [ [no]udpcsum ] [ [no]udp6zerocsumtx ] [ [no]udp6zerocsumrx ] [ ageing SECONDS ] [ maxaddress NUMBER ] [ [no]external ] [ gbp ] [ gpe ]

id VNI - specifies the VXLAN Network Identifier (or VXLAN Segment Identifier) to use.

dev PHYS_DEV - specifies the physical device to use for tunnel endpoint communication.

group IPADDR - specifies the multicast IP address to join. This parameter cannot be specified with the remote parameter.

remote IPADDR - specifies the unicast destination IP address to use in outgoing packets when the destination link layer address is not known in the VXLAN device forwarding database. This parameter cannot be specified with the group parameter.

local IPADDR - specifies the source IP address to use in outgoing packets.

ttl TTL - specifies the TTL value to use in outgoing packets.

tos TOS - specifies the TOS value to use in outgoing packets.

df DF - specifies the usage of the Don't Fragment flag (DF) bit in outgoing packets with IPv4 headers. The value inherit causes the bit to be copied from the original IP header. The values unset and set cause the bit to be always unset or always set, respectively. By default, the bit is not set.

flowlabel FLOWLABEL - specifies the flow label to use in outgoing packets.

dstport PORT - specifies the UDP destination port to communicate to the remote

VXLAN tunnel endpoint.

srcport MIN MAX - specifies the range of port numbers to use as UDP source ports to communicate to the remote VXLAN tunnel endpoint.

[no]learning - specifies if unknown source link layer addresses and IP addresses are entered into the VXLAN device forwarding database.

[no]rsc - specifies if route short circuit is turned on.

[no]proxy - specifies ARP proxy is turned on.

[no]l2miss - specifies if netlink LLADDR miss notifications are generated.

[no]l3miss - specifies if netlink IP ADDR miss notifications are generated.

[no]udpcsum - specifies if UDP checksum is calculated for transmitted packets over IPv4.

[no]udp6zerocsumtx - skip UDP checksum calculation for transmitted packets over IPv6.

[no]udp6zerocsumrx - allow incoming UDP packets over IPv6 with zero checksum field.

ageing SECONDS - specifies the lifetime in seconds of FDB entries learnt by the kernel.

maxaddress NUMBER - specifies the maximum number of FDB entries.

[no]external - specifies whether an external control plane (e.g. ip route encap) or the internal FDB should be used.

gbp - enables the Group Policy extension (VXLAN-GBP).

Allows to transport group policy context across VXLAN network peers. If enabled, includes the mark of a packet in the VXLAN header for outgoing packets and fills the packet mark based on the information found in the VXLAN header for incoming packets.

Format of upper 16 bits of packet mark (flags);

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

|-|-|-|-|-|-|-|-|-|D|-|-|A|-|-|-|

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

D := Don't Learn bit. When set, this bit indicates that the egress VTEP MUST NOT learn the source address of the encapsulated frame.

A := Indicates that the group policy has already been applied to this packet. Policies MUST NOT be applied by devices when the A bit is set.

Format of lower 16 bits of packet mark (policy ID):

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| Group Policy ID |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Example:

iptables -A OUTPUT [...] -j MARK --set-mark 0x800FF

gpe - enables the Generic Protocol extension (VXLAN-GPE). Currently, this is only supported together with the external keyword.

VETH, VXCAN Type Support

For a link of types VETH/VXCAN the following additional arguments are supported: ip link add DEVICE type { veth | vxcan } [ peer name NAME ]

peer name NAME - specifies the virtual pair device name of the VETH/VXCAN tunnel.

IPIP, SIT Type Support

For a link of type IPIPorSIT the following additional arguments are supported: ip link add DEVICE type { ipip | sit } remote ADDR local ADDR [ encap { fou | gue | none } ] [ encap-sport { PORT | auto } ] [ encap-dport PORT ] [ [no]encap-csum ] [ [no]encap-remcsum ] [ mode { ip6ip | ipip | mplsip | any } ] [ external ]

remote ADDR - specifies the remote address of the tunnel.

local ADDR - specifies the fixed local address for tunneled packets. It must be an address on another interface on this host.

encap { fou | gue | none } - specifies type of secondary UDP encapsulation. "fou" indicates Foo-Over-UDP, "gue" indicates Generic UDP Encapsulation.

encap-sport { PORT | auto } - specifies the source port in UDP encapsulation. PORT indicates the port by number, "auto" indicates that the port number should be chosen automatically (the kernel picks a flow based on the flow hash of the encapsulated packet).

[no]encap-csum - specifies if UDP checksums are enabled in the secondary encapsulation.

[no]encap-remcsum - specifies if Remote Checksum Offload is enabled. This is only applicable for Generic UDP Encapsulation.

mode { ip6ip | ipip | mplsip | any } - specifies mode in which device should run. "ip6ip" indicates IPv6-Over-IPv4, "ipip" indicates "IPv4-Over-IPv4", "mplsip" indicates MPLS-Over-IPv4, "any" indicates IPv6, IPv4 or MPLS Over IPv4. Supported for SIT where the default is "ip6ip" and IPIP where the default is "ipip". IPv6-Over-IPv4 is not supported for IPIP.

external - make this tunnel externally controlled (e.g. ip route encap).

GRE Type Support

For a link of type GRE or GRETAP the following additional arguments are supported: ip link add DEVICE type { gre | gretap } remote ADDR local ADDR [ [no][i|o]seq ] [ [i|o]key KEY | no[i|o]key ] [ [no][i|o]csum ] [ ttl TTL ] [ tos TOS ] [ [no]pmtudisc ] [ [no]ignore-df ] [ dev PHYS_DEV ] [ encap { fou | gue | none } ] [ encap-sport { PORT | auto } ] [ encap-dport PORT ] [ [no]encap-csum ] [ [no]encap-remcsum ] [ external ]

remote ADDR - specifies the remote address of the tunnel.

local ADDR - specifies the fixed local address for tunneled packets. It must be an address on another interface on this host.

[no][i|o]seq - serialize packets. The oseq flag enables sequencing of outgoing packets. The iseq flag requires that all input packets are serialized.

[i|o]key KEY | no[i|o]key - use keyed GRE with key KEY. KEY is either a number or an IPv4 address-like dotted quad. The key parameter specifies the same key to use in both directions. The ikey and okey parameters specify different keys for input and output.

[no][i|o]csum - generate/require checksums for tunneled packets. The ocsum flag calculates checksums for outgoing packets. The icsum flag requires that all input packets have the correct checksum. The csum flag is equivalent to the combination icsum ocsum .

ttl TTL - specifies the TTL value to use in outgoing packets.

tos TOS - specifies the TOS value to use in outgoing packets.

[no]pmtudisc - enables/disables Path MTU Discovery on this tunnel. It is enabled by default. Note that a fixed ttl is incompatible with this option: tunneling with a fixed ttl always makes pmtu discovery.

[no]ignore-df - enables/disables IPv4 DF suppression on this tunnel. Normally datagrams that exceed the MTU will be fragmented; the presence of the DF flag inhibits this, resulting instead in an ICMP Unreachable (Fragmentation Required) message. Enabling this attribute causes the DF flag to be ignored.

dev PHYS_DEV - specifies the physical device to use for tunnel endpoint communication.

encap { fou | gue | none } - specifies type of secondary UDP encapsulation. "fou" indicates Foo-Over-UDP, "gue" indicates Generic UDP Encapsulation.

encap-sport { PORT | auto } - specifies the source port in UDP encapsulation. PORT indicates the port by number, "auto" indicates that the port number should be chosen automatically (the kernel picks a flow based on the flow hash of the encapsulated packet).

[no]encap-csum - specifies if UDP checksums are enabled in the secondary encapsulation.

[no]encap-remcsum - specifies if Remote Checksum Offload is enabled. This is only applicable for Generic UDP Encapsulation.

external - make this tunnel externally controlled (e.g. ip route encap).

IP6GRE/IP6GRETAP Type Support

For a link of type IP6GRE/IP6GRETAP the following additional arguments are supported: ip link add DEVICE type { ip6gre | ip6gretap } remote ADDR local ADDR [ [no][i|o]seq ] [ [i|o]key KEY | no[i|o]key ] [ [no][i|o]csum ] [ hoplimit TTL ] [ encaplimit ELIM ] [ tclass TCLASS ] [ flowlabel FLOWLABEL ] [ dscp inherit ] [ [no]allow-localremote ] [ dev PHYS_DEV ] [ external ]

remote ADDR - specifies the remote IPv6 address of the tunnel.

local ADDR - specifies the fixed local IPv6 address for tunneled packets. It must be an address on another interface on this host.

[no][i|o]seq - serialize packets. The oseq flag enables sequencing of outgoing packets. The iseq flag requires that all input packets are serialized.

[i|o]key KEY | no[i|o]key - use keyed GRE with key KEY. KEY is either a number or an IPv4 address-like dotted quad. The key parameter specifies the same key to use in both directions. The ikey and okey parameters specify different keys for input and output.

[no][i|o]csum - generate/require checksums for tunneled packets. The ocsum flag calculates checksums for outgoing packets. The icsum flag requires that all input packets have the correct checksum. The csum flag is equivalent to the combination icsum ocsum.

hoplimit TTL - specifies Hop Limit value to use in outgoing packets.

encaplimit ELIM - specifies a fixed encapsulation limit. Default is 4.

flowlabel FLOWLABEL - specifies a fixed flowlabel.

[no]allow-localremote - specifies whether to allow remote endpoint to have an address configured on local host.

tclass TCLASS - specifies the traffic class field on tunneled packets, which can be specified as either a two-digit hex value (e.g. c0) or a predefined string (e.g. internet). The value inherit causes the field to be copied from the original IP header. The values inherit/STRING or inherit/00..ff will set the field to STRING or 00..ff when tunneling non-IP packets. The default value is 00.

external - make this tunnel externally controlled (or not, which is the default). In the kernel, this is referred to as collect metadata mode. This flag is mutually exclusive with the remote, local, seq, key, csum, hoplimit, encaplimit, flowlabel and tclass options.

IPoIB Type Support

For a link of type IPoIB the following additional arguments are supported: ip link add DEVICE name NAME type ipoib [ pkey PKEY ] [ mode MODE ]

pkey PKEY - specifies the IB P-Key to use.

mode MODE - specifies the mode (datagram or connected) to use.

ERSPAN Type Support

For a link of type ERSPAN/IP6ERSPAN the following additional arguments are supported: ip link add DEVICE type { erspan | ip6erspan } remote ADDR local ADDR seq key KEY erspan_ver version [ erspan IDX ] [ erspan_dir { ingress | egress } ] [ erspan_hwid hwid ] [ [no]allow-localremote ] [ external ]

remote ADDR - specifies the remote address of the tunnel.

local ADDR - specifies the fixed local address for tunneled packets. It must be an address on another interface on this host.

erspan_ver version - specifies the ERSPAN version number. version indicates the ERSPAN version to be created: 0 for version 0 type I, 1 for version 1 (type II) or 2 for version 2 (type III).

erspan IDX - specifies the ERSPAN v1 index field. IDX indicates a 20 bit index/port number associated with the ERSPAN traffic's source port and direction.

erspan_dir { ingress | egress } - specifies the ERSPAN v2 mirrored traffic's direction.

erspan_hwid hwid - an unique identifier of an ERSPAN v2 engine within a system. hwid is a 6-bit value for users to configure.

[no]allow-localremote - specifies whether to allow remote endpoint to have an address configured on local host.

external - make this tunnel externally controlled (or not, which is the default). In the kernel, this is referred to as collect metadata mode. This flag is mutually exclusive with the remote, local, erspan_ver, erspan, erspan_dir and erspan_hwid options.

GENEVE Type Support

For a link of type GENEVE the following additional arguments are supported: ip link add DEVICE type geneve id VNI remote IPADDR [ ttl TTL ] [ tos TOS ] [ df DF ] [ flowlabel FLOWLABEL ] [ dstport PORT ] [ [no]external ] [ [no]udpcsum ] [ [no]udp6zerocsumtx ] [ [no]udp6zerocsumrx ]

id VNI - specifies the Virtual Network Identifier to use.

remote IPADDR - specifies the unicast destination IP address to use in outgoing packets.

ttl TTL - specifies the TTL value to use in outgoing packets. "0" or "auto" means use whatever default value, "inherit" means inherit the inner protocol's ttl. Default option is "0".

tos TOS - specifies the TOS value to use in outgoing packets.

df DF - specifies the usage of the Don't Fragment flag (DF) bit in outgoing packets with IPv4 headers. The value inherit causes the bit to be copied from the original IP header. The values unset and set cause the bit to be always unset or always set, respectively. By default, the bit is not set.

flowlabel FLOWLABEL - specifies the flow label to use in outgoing packets.

dstport PORT - select a destination port other than the default of 6081.

[no]external - make this tunnel externally controlled (or not, which is the default). This flag is mutually exclusive with the id, remote, ttl, tos and flowlabel options.

[no]udpcsum - specifies if UDP checksum is calculated for transmitted packets over IPv4.

[no]udp6zerocsumtx - skip UDP checksum calculation for transmitted packets over IPv6.

[no]udp6zerocsumrx - allow incoming UDP packets over IPv6 with zero checksum field.

Bareudp Type Support

For a link of type Bareudp the following additional arguments are supported: ip link add DEVICE type bareudp dstport PORT ethertype PROTO [ srcportmin PORT ] [ [no]multiproto ]

dstport PORT - specifies the destination port for the UDP tunnel.

ethertype PROTO - specifies the ethertype of the L3 protocol being tunnelled. ethertype can be given as plain Ethernet protocol number or using the protocol name ("ipv4", "ipv6", "mpls_uc", etc.).

srcportmin PORT - selects the lowest value of the UDP tunnel source port range.

[no]multiproto - activates support for protocols similar to the one specified by ethertype. When ethertype is "mpls_uc" (that is, unicast MPLS), this allows the tunnel to also handle multicast MPLS. When ethertype is "ipv4", this allows the tunnel to also handle IPv6. This option is disabled by default.

MACVLAN and MACVTAP Type Support

For a link of type MACVLAN or MACVTAP the following additional arguments are supported: ip link add link DEVICE name NAME type { macvlan | macvtap } mode { private | vepa | bridge | passthru [ nopromisc ] | source } [ bcqueuelen { LENGTH } ]

type { macvlan | macvtap } - specifies the link type to use. macvlan creates just a virtual interface, while macvtap in addition creates a character device /dev/tapX to be used just like a tuntap device.

mode private - Do not allow communication between macvlan instances on the same physical interface, even if the external switch supports hairpin mode.

mode vepa - Virtual Ethernet Port Aggregator mode. Data from one macvlan instance to the other on the same physical interface is transmitted over the physical interface. Either the attached switch needs to support hairpin mode, or there must be a TCP/IP router forwarding the packets in order to allow communication. This is the default mode.

mode bridge - In bridge mode, all endpoints are directly connected to each other, communication is not redirected through the physical interface's peer.

mode passthru [ nopromisc ] - This mode gives more power to a single endpoint, usually in macvtap mode. It is not allowed for more than one endpoint on the same physical interface. All traffic will be forwarded to this endpoint, allowing virtio guests to change MAC address or set promiscuous mode in order to bridge the interface or create vlan interfaces on top of it. By default, this mode forces the underlying interface into promiscuous mode. Passing the nopromisc flag prevents this, so the promisc flag may be controlled using standard tools.

mode source - allows one to set a list of allowed mac address, which is used to match against source mac address from received frames on underlying interface. This allows creating mac based VLAN associations, instead of standard port or tag based. The feature is useful to deploy 802.1x mac based behavior, where drivers of underlying interfaces doesn't allows that.

bcqueuelen { LENGTH } - Set the length of the RX queue used to process broadcast and multicast packets. LENGTH must be a positive integer in the range [0-4294967295]. Setting a length of 0 will effectively drop all broadcast/multicast traffic. If not specified the macvlan driver default (1000) is used. Note that all macvlans that share the same underlying device are using the same queue. The parameter here is a request, the actual queue length used will be the maximum length that any macvlan interface has requested. When listing device parameters both the bcqueuelen parameter as well as the actual used bcqueuelen are listed to better help the user understand the setting.

High-availability Seamless Redundancy (HSR) Support

For a link of type HSR the following additional arguments are supported: ip link add link DEVICE name NAME type hsr slave1 SLAVE1-IF slave2 SLAVE2-IF [ supervision ADDR-BYTE ] [ version { 0 | 1 } [ proto { 0 | 1 } ]

type hsr - specifies the link type to use, here HSR.

slave1 SLAVE1-IF - Specifies the physical device used for the first of the two ring ports.

slave2 SLAVE2-IF - Specifies the physical device used for the second of the two ring ports.

supervision ADDR-BYTE - The last byte of the multicast address used for HSR supervision frames. Default option is "0", possible values 0-255.

version { 0 | 1 } - Selects the protocol version of the interface. Default option is "0", which corresponds to the 2010 version of the HSR standard. Option "1" activates the 2012 version.

proto { 0 | 1 } - Selects the protocol at the interface. Default option is "0", which corresponds to the HSR standard. Option "1" activates the Parallel Redundancy Protocol (PRP).

BRIDGE Type Support

For a link of type BRIDGE the following additional arguments are supported: ip link add DEVICE type bridge [ ageing_time AGEING_TIME ] [ group_fwd_mask MASK ] [ group_address ADDRESS ] [ forward_delay FORWARD_DELAY ] [ hello_time HELLO_TIME ] [ max_age MAX_AGE ] [ stp_state STP_STATE ] [ priority PRIORITY ] [ vlan_filtering VLAN_FILTERING ] [ vlan_protocol VLAN_PROTOCOL ] [ vlan_default_pvid VLAN_DEFAULT_PVID ] [ vlan_stats_enabled VLAN_STATS_ENABLED ] [ vlan_stats_per_port VLAN_STATS_PER_PORT ] [ mcast_snooping MULTICAST_SNOOPING ] [ mcast_router MULTICAST_ROUTER ] [ mcast_query_use_ifaddr MCAST_QUERY_USE_IFADDR ] [ mcast_querier MULTICAST_QUERIER ] [ mcast_hash_elasticity HASH_ELASTICITY ] [ mcast_hash_max HASH_MAX ] [ mcast_last_member_count LAST_MEMBER_COUNT ] [ mcast_startup_query_count STARTUP_QUERY_COUNT ] [ mcast_last_member_interval LAST_MEMBER_INTERVAL ] [ mcast_membership_interval MEMBERSHIP_INTERVAL ] [ mcast_querier_interval QUERIER_INTERVAL ] [ mcast_query_interval QUERY_INTERVAL ] [ mcast_query_response_interval QUERY_RESPONSE_INTERVAL ] [ mcast_startup_query_interval STARTUP_QUERY_INTERVAL ] [ mcast_stats_enabled MCAST_STATS_ENABLED ] [ mcast_igmp_version IGMP_VERSION ] [ mcast_mld_version MLD_VERSION ] [ nf_call_iptables NF_CALL_IPTABLES ] [ nf_call_ip6tables NF_CALL_IP6TABLES ] [ nf_call_arptables NF_CALL_ARPTABLES ]

ageing_time AGEING_TIME - configure the bridge's FDB entries ageing time, ie the number of seconds a MAC address will be kept in the FDB after a packet has been received from that address. after this time has passed, entries are cleaned up.

group_fwd_mask MASK - set the group forward mask. This is the bitmask that is applied to decide whether to forward incoming frames destined to link-local addresses, ie addresses of the form 01:80:C2:00:00:0X (defaults to 0, ie the bridge does not forward any link-local frames).

group_address ADDRESS - set the MAC address of the multicast group this bridge uses for STP. The address must be a link-local address in standard Ethernet MAC address format, ie an address of the form 01:80:C2:00:00:0X, with X

in [0, 4..f].

forward_delay FORWARD_DELAY - set the forwarding delay in seconds, ie the time spent in LISTENING state (before moving to LEARNING) and in LEARNING state (before moving to FORWARDING). Only relevant if STP is enabled. Valid values are between 2 and 30.

hello_time HELLO_TIME - set the time in seconds between hello packets sent by the bridge, when it is a root bridge or a designated bridges. Only relevant if STP is enabled. Valid values are between 1 and 10.

max_age MAX_AGE - set the hello packet timeout, ie the time in seconds until another bridge in the spanning tree is assumed to be dead, after reception of its last hello message. Only relevant if STP is enabled. Valid values are between 6 and 40.

stp_state STP_STATE - turn spanning tree protocol on (STP_STATE > 0) or off (STP_STATE == 0). for this bridge.

priority PRIORITY - set this bridge's spanning tree priority, used during STP root bridge election. PRIORITY is a 16bit unsigned integer.

vlan_filtering VLAN_FILTERING - turn VLAN filtering on (VLAN_FILTERING > 0) or off (VLAN_FILTERING == 0). When disabled, the bridge will not consider the VLAN tag when handling packets.

vlan_protocol { 802.1Q | 802.1ad } - set the protocol used for VLAN filtering.

vlan_default_pvid VLAN_DEFAULT_PVID - set the default PVID (native/untagged VLAN ID) for this bridge.

vlan_stats_enabled VLAN_STATS_ENABLED - enable (VLAN_STATS_ENABLED == 1) or disable (VLAN_STATS_ENABLED == 0) per-VLAN stats accounting.

vlan_stats_per_port VLAN_STATS_PER_PORT - enable (VLAN_STATS_PER_PORT == 1) or disable (VLAN_STATS_PER_PORT == 0) per-VLAN per-port stats accounting. Can be changed only when there are no port VLANs configured.

mcast_snooping MULTICAST_SNOOPING - turn multicast snooping on (MULTICAST_SNOOPING > 0) or off (MULTICAST_SNOOPING == 0).

mcast_router MULTICAST_ROUTER - set bridge's multicast router if IGMP snooping is enabled. MULTICAST_ROUTER is an integer value having the following meaning:

0 - disabled.

1 - automatic (queried).

2 - permanently enabled.

mcast_query_use_ifaddr MCAST_QUERY_USE_IFADDR - whether to use the bridge's own IP address as source address for IGMP queries (MCAST_QUERY_USE_IFADDR > 0) or the default of 0.0.0.0 (MCAST_QUERY_USE_IFADDR == 0).

mcast_querier MULTICAST_QUERIER - enable (MULTICAST_QUERIER > 0) or disable (MULTICAST_QUERIER == 0) IGMP querier, ie sending of multicast queries by the bridge (default: disabled).

mcast_querier_interval QUERIER_INTERVAL - interval between queries sent by other routers. if no queries are seen after this delay has passed, the bridge will start to send its own queries (as if mcast_querier was enabled).

mcast_hash_elasticity HASH_ELASTICITY - set multicast database hash elasticity, ie the maximum chain length in the multicast hash table (defaults to 4).

mcast_hash_max HASH_MAX - set maximum size of multicast hash table (defaults to 512, value must be a power of 2).

mcast_last_member_count LAST_MEMBER_COUNT - set multicast last member count, ie the number of queries the bridge will send before stopping forwarding a multicast group after a "leave" message has been received (defaults to 2).

mcast_last_member_interval LAST_MEMBER_INTERVAL - interval between queries to find remaining members of a group, after a "leave" message is received.

mcast_startup_query_count STARTUP_QUERY_COUNT - set the number of IGMP queries to send during startup phase (defaults to 2).

mcast_startup_query_interval STARTUP_QUERY_INTERVAL - interval between queries in the startup phase.

mcast_query_interval QUERY_INTERVAL - interval between queries sent by the bridge after the end of the startup phase.

mcast_query_response_interval QUERY_RESPONSE_INTERVAL - set the Max Response Time/Maximum Response Delay for IGMP/MLD queries sent by the bridge.

mcast_membership_interval MEMBERSHIP_INTERVAL - delay after which the bridge will leave a group, if no membership reports for this group are received.

mcast_stats_enabled MCAST_STATS_ENABLED - enable (MCAST_STATS_ENABLED > 0) or disable (MCAST_STATS_ENABLED == 0) multicast (IGMP/MLD) stats accounting.

mcast_igmp_version IGMP_VERSION - set the IGMP version.

mcast_mld_version MLD_VERSION - set the MLD version.

nf_call_iptables NF_CALL_IPTABLES - enable (NF_CALL_IPTABLES > 0) or disable (NF_CALL_IPTABLES == 0) iptables hooks on the bridge.

nf_call_ip6tables NF_CALL_IP6TABLES - enable (NF_CALL_IP6TABLES > 0) or disable (NF_CALL_IP6TABLES == 0) ip6tables hooks on the bridge.

nf_call_arptables NF_CALL_ARPTABLES - enable (NF_CALL_ARPTABLES > 0) or disable (NF_CALL_ARPTABLES == 0) arptables hooks on the bridge.

MACsec Type Support

For a link of type MACsec the following additional arguments are supported: ip link add link DEVICE name NAME type macsec [ [ address <lladdr> ] port PORT | sci SCI ] [ cipher CIPHER_SUITE ] [ icvlen { 8..16 } ] [ encrypt { on | off } ] [ send_sci { on | off } ] [ end_station { on | off } ] [ scb { on | off } ] [ protect { on | off } ] [ replay { on | off } window { 0..2^32-1 } ] [ validate { strict | check | disabled } ] [ encodingsa { 0..3 } ]

address <lladdr> - sets the system identifier component of secure channel for this MACsec device.

port PORT - sets the port number component of secure channel for this MACsec device, in a range from 1 to 65535 inclusive. Numbers with a leading " 0 " or " 0x " are interpreted as octal and hexadecimal, respectively.

sci SCI - sets the secure channel identifier for this MACsec device. SCI is a 64bit wide number in hexadecimal format.

cipher CIPHER_SUITE - defines the cipher suite to use.

icvlen LENGTH - sets the length of the Integrity Check Value (ICV).

encrypt on or encrypt off - switches between authenticated encryption, or authenticity mode only.

send_sci on or send_sci off - specifies whether the SCI is included in every packet, or only when it is necessary.

end_station on or end_station off - sets the End Station bit.

scb on or scb off - sets the Single Copy Broadcast bit.

protect on or protect off - enables MACsec protection on the device.

replay on or replay off - enables replay protection on the device.

window SIZE - sets the size of the replay window.

validate strict or validate check or validate disabled - sets the validation mode on the device.

encodingsa AN - sets the active secure association for transmission.

VRF Type Support

For a link of type VRF the following additional arguments are supported: ip link add DEVICE type vrf table TABLE

table table id associated with VRF device

RMNET Type Support

For a link of type RMNET the following additional arguments are supported: ip link add link DEVICE name NAME type rmnet mux_id MUXID

mux_id MUXID - specifies the mux identifier for the rmnet device, possible values 1-254.

XFRM Type Support

For a link of type XFRM the following additional arguments are supported: ip link add DEVICE type xfrm dev PHYS_DEV [ if_id IF_ID ]

dev PHYS_DEV - specifies the underlying physical interface from which transform traffic is sent and received.

if_id IF-ID - specifies the hexadecimal lookup key used to send traffic to and from specific xfrm policies. Policies must be configured with the same key. If not set, the key defaults to 0 and will match any policies which similarly do not have a lookup key configuration.

### ip link delete - delete virtual link
dev DEVICE

specifies the virtual device to act operate on.

group GROUP

specifies the group of virtual links to delete. Group 0 is not allowed to be deleted since it is the default group.

type TYPE

specifies the type of the device.

### ip link set - change device attributes
Warning: If multiple parameter changes are requested, ip aborts immediately after any of the changes have failed. This is the only case when ip can move the system to an unpredictable state. The solution is to avoid changing several parameters with one ip link set call. The modifier change is equivalent to set.

dev DEVICE

DEVICE specifies network device to operate on. When configuring SR-IOV Virtual Function (VF) devices, this keyword should specify the associated Physical Function (PF) device.

group GROUP

GROUP has a dual role: If both group and dev are present, then move the device to the specified group. If only a group is specified, then the command operates on all devices in that group.

up and down

change the state of the device to UP or DOWN.

arp on or arp off

change the NOARP flag on the device.

multicast on or multicast off

change the MULTICAST flag on the device.

allmulticast on or allmulticast off

change the ALLMULTI flag on the device. When enabled, instructs network driver to retrieve all multicast packets from the network to the kernel for further processing.

promisc on or promisc off

change the PROMISC flag on the device. When enabled, activates promiscuous operation of the network device.

trailers on or trailers off

change the NOTRAILERS flag on the device, NOT used by the Linux and exists for BSD compatibility.

protodown on or protodown off

change the PROTODOWN state on the device. Indicates that a protocol error has been detected on the port. Switch drivers can react to this error by doing a phys down on the switch port.

protodown_reason PREASON on or off

set PROTODOWN reasons on the device. protodown reason bit names can be enumerated under /etc/iproute2/protodown_reasons.d/. possible reasons bits 0-31

dynamic on or dynamic off

change the DYNAMIC flag on the device. Indicates that address can change when interface goes down (currently NOT used by the Linux).

name NAME

change the name of the device. This operation is not recommended if the device is running or has some addresses already configured.

txqueuelen NUMBER

txqlen NUMBER

change the transmit queue length of the device.

mtu NUMBER

change the MTU of the device.

address LLADDRESS

change the station address of the interface.

broadcast LLADDRESS

brd LLADDRESS

peer LLADDRESS

change the link layer broadcast address or the peer address when the interface is POINTOPOINT.

netns NETNSNAME | PID

move the device to the network namespace associated with name NETNSNAME or process PID. Some devices are not allowed to change network namespace: loopback, bridge, wireless. These are network namespace local devices. In such case ip tool will return "Invalid argument" error. It is possible to find out if device is local to a single network namespace by checking netns-local flag in the output of the ethtool:

ethtool -k DEVICE

To change network namespace for wireless devices the iw tool can be used. But it allows to change network namespace only for physical devices and by process PID.

alias NAME

give the device a symbolic name for easy reference.

group GROUP

specify the group the device belongs to. The available groups are listed in file /etc/iproute2/group.

vf NUM

specify a Virtual Function device to be configured. The associated PF device must be specified using the dev parameter.

mac LLADDRESS - change the station address for the specified VF. The vf parameter must be specified.

vlan VLANID - change the assigned VLAN for the specified VF. When specified, all traffic sent from the VF will be tagged with the specified VLAN ID. Incoming traffic will be filtered for the specified VLAN ID, and will have all VLAN tags stripped before being passed to the VF. Setting this parameter to 0 disables VLAN tagging and filtering. The vf parameter must be specified.

qos VLAN-QOS - assign VLAN QOS (priority) bits for the VLAN tag. When specified, all VLAN tags transmitted by the VF will include the specified priority bits in the VLAN tag. If not specified, the value is assumed to be 0. Both the vf and vlan parameters must be specified. Setting both vlan and qos as 0 disables VLAN tagging and filtering for the VF.

proto VLAN-PROTO - assign VLAN PROTOCOL for the VLAN tag, either 802.1Q or 802.1ad. Setting to 802.1ad, all traffic sent from the VF will be tagged with VLAN S-Tag. Incoming traffic will have VLAN S-Tags stripped before being passed to the VF. Setting to 802.1ad also enables an option to concatenate another VLAN tag, so both S-TAG and C-TAG will be inserted/stripped for outgoing/incoming traffic, respectively. If not specified, the value is assumed to be 802.1Q. Both the vf and vlan parameters must be specified.

rate TXRATE -- change the allowed transmit bandwidth, in Mbps, for the specified VF. Setting this parameter to 0 disables rate limiting. vf parameter must be specified. Please use new API max_tx_rate option instead.

max_tx_rate TXRATE - change the allowed maximum transmit bandwidth, in Mbps, for the specified VF. Setting this parameter to 0 disables rate limiting. vf parameter must be specified.

min_tx_rate TXRATE - change the allowed minimum transmit bandwidth, in Mbps, for the specified VF. Minimum TXRATE should be always <= Maximum TXRATE. Setting this parameter to 0 disables rate limiting. vf parameter must be specified.

spoofchk on|off - turn packet spoof checking on or off for the specified VF.

query_rss on|off - toggle the ability of querying the RSS configuration of a specific

VF. VF RSS information like RSS hash key may be considered sensitive

on some devices where this information is shared between VF and PF

and thus its querying may be prohibited by default.

state auto|enable|disable - set the virtual link state as seen by the specified VF. Setting to auto means a reflection of the PF link state, enable lets the VF to communicate with other VFs on this host even if the PF link state is down, disable causes the HW to drop any packets sent by the VF.

trust on|off - trust the specified VF user. This enables that VF user can set a specific feature which may impact security and/or performance. (e.g. VF multicast promiscuous mode)

node_guid eui64 - configure node GUID for Infiniband VFs.

port_guid eui64 - configure port GUID for Infiniband VFs.

xdp object | pinned | off

set (or unset) a XDP ("eXpress Data Path") BPF program to run on every packet at driver level. ip link output will indicate a xdp flag for the networking device. If the driver does not have native XDP support, the kernel will fall back to a slower, driver-independent "generic" XDP variant. The ip link output will in that case indicate xdpgeneric instead of xdp only. If the driver does have native XDP support, but the program is loaded under xdpgeneric object | pinned then the kernel will use the generic XDP variant instead of the native one. xdpdrv has the opposite effect of requestsing that the automatic fallback to the generic XDP variant be disabled and in case driver is not XDP-capable error should be returned. xdpdrv also disables hardware offloads. xdpoffload in ip link output indicates that the program has been offloaded to hardware and can also be used to request the "offload" mode, much like xdpgeneric it forces program to be installed specifically in HW/FW of the apater. off (or none ) - Detaches any currently attached XDP/BPF program from the given device.

object FILE - Attaches a XDP/BPF program to the given device. The FILE points to a BPF ELF file (f.e. generated by LLVM) that contains the BPF program code, map specifications, etc. If a XDP/BPF program is already attached to the given device, an error will be thrown. If no XDP/BPF program is currently attached, the device supports XDP and the program from the BPF ELF file passes the kernel verifier, then it will be attached to the device. If the option -force is passed to ip then any prior attached XDP/BPF program will be atomically overridden and no error will be thrown in this case. If no section option is passed, then the default section name ("prog") will be assumed, otherwise the provided section name will be used. If no verbose option is passed, then a verifier log will only be dumped on load error. See also EXAMPLES section for usage examples.

section NAME - Specifies a section name that contains the BPF program code. If no section name is specified, the default one ("prog") will be used. This option is to be passed with the object option.

verbose - Act in verbose mode. For example, even in case of success, this will print the verifier log in case a program was loaded from a BPF ELF file.

pinned FILE - Attaches a XDP/BPF program to the given device. The FILE points to an already pinned BPF program in the BPF file system. The option section doesn't apply here, but otherwise semantics are the same as with the option object described already.

master DEVICE

set master device of the device (enslave device).

nomaster

unset master device of the device (release device).

addrgenmode eui64|none|stable_secret|random

set the IPv6 address generation mode eui64 - use a Modified EUI-64 format interface identifier

none - disable automatic address generation

stable_secret - generate the interface identifier based on a preset

/proc/sys/net/ipv6/conf/{default,DEVICE}/stable_secret

random - like stable_secret, but auto-generate a new random secret if none is set

link-netnsid

set peer netnsid for a cross-netns interface

type ETYPE TYPE_ARGS

Change type-specific settings. For a list of supported types and arguments refer to the description of ip link add above. In addition to that, it is possible to manipulate settings to slave devices:

Bridge Slave Support

For a link with master bridge the following additional arguments are supported: ip link set type bridge_slave [ fdb_flush ] [ state STATE ] [ priority PRIO ] [ cost COST ] [ guard { on | off } ] [ hairpin { on | off } ] [ fastleave { on | off } ] [ root_block { on | off } ] [ learning { on | off } ] [ flood { on | off } ] [ proxy_arp { on | off } ] [ proxy_arp_wifi { on | off } ] [ mcast_router MULTICAST_ROUTER ] [ mcast_fast_leave { on | off} ] [ mcast_flood { on | off } ] [ mcast_to_unicast { on | off } ] [ group_fwd_mask MASK ] [ neigh_suppress { on | off } ] [ vlan_tunnel { on | off } ] [ isolated { on | off } ] [ backup_port DEVICE ] [ nobackup_port ]

fdb_flush - flush bridge slave's fdb dynamic entries.

state STATE - Set port state. STATE is a number representing the following states: 0 (disabled), 1 (listening), 2 (learning), 3 (forwarding), 4 (blocking).

priority PRIO - set port priority (allowed values are between 0 and 63, inclusively).

cost COST - set port cost (allowed values are between 1 and 65535, inclusively).

guard { on | off } - block incoming BPDU packets on this port.

hairpin { on | off } - enable hairpin mode on this port. This will allow incoming packets on this port to be reflected back.

fastleave { on | off } - enable multicast fast leave on this port.

root_block { on | off } - block this port from becoming the bridge's root port.

learning { on | off } - allow MAC address learning on this port.

flood { on | off } - open the flood gates on this port, i.e. forward all unicast frames to this port also. Requires proxy_arp and proxy_arp_wifi to be turned off.

proxy_arp { on | off } - enable proxy ARP on this port.

proxy_arp_wifi { on | off } - enable proxy ARP on this port which meets extended requirements by IEEE 802.11 and Hotspot 2.0 specifications.

mcast_router MULTICAST_ROUTER - configure this port for having multicast routers attached. A port with a multicast router will receive all multicast traffic. MULTICAST_ROUTER may be either 0 to disable multicast routers on this port, 1 to let the system detect the presence of of routers (this is the default), 2 to permanently enable multicast traffic forwarding on this port or 3 to enable multicast routers temporarily on this port, not depending on incoming queries.

mcast_fast_leave { on | off } - this is a synonym to the fastleave option above.

mcast_flood { on | off } - controls whether a given port will flood multicast traffic for which

there is no MDB entry.

mcast_to_unicast { on | off } - controls whether a given port will replicate packets using unicast

instead of multicast. By default this flag is off.

group_fwd_mask MASK - set the group forward mask. This is the bitmask that is applied to decide whether to forward incoming frames destined to link-local addresses, ie addresses of the form 01:80:C2:00:00:0X (defaults to 0, ie the bridge does not forward any link-local frames coming on this port).

neigh_suppress { on | off } - controls whether neigh discovery (arp and nd) proxy and suppression is enabled on the port. By default this flag is off.

vlan_tunnel { on | off } - controls whether vlan to tunnel mapping is enabled on the port. By default this flag is off.

backup_port DEVICE - if the port loses carrier all traffic will be redirected to the configured backup port

nobackup_port - removes the currently configured backup port

Bonding Slave Support

For a link with master bond the following additional arguments are supported: ip link set type bond_slave [ queue_id ID ]

queue_id ID - set the slave's queue ID (a 16bit unsigned value).

MACVLAN and MACVTAP Support

Modify list of allowed macaddr for link in source mode. ip link set type { macvlan | macvap } [ macaddr COMMAND MACADDR ... ]

Commands:

add - add MACADDR to allowed list

set - replace allowed list

del - remove MACADDR from allowed list

flush - flush whole allowed list

Update the broadcast/multicast queue length.

ip link set type { macvlan | macvap } [ bcqueuelen LENGTH ]

bcqueuelen LENGTH - Set the length of the RX queue used to process broadcast and multicast packets. LENGTH must be a positive integer in the range [0-4294967295]. Setting a length of 0 will effectively drop all broadcast/multicast traffic. If not specified the macvlan driver default (1000) is used. Note that all macvlans that share the same underlying device are using the same queue. The parameter here is a request, the actual queue length used will be the maximum length that any macvlan interface has requested. When listing device parameters both the bcqueuelen parameter as well as the actual used bcqueuelen are listed to better help the user understand the setting.

### ip link show - display device attributes
dev NAME (default)

NAME specifies the network device to show.

group GROUP

GROUP specifies what group of devices to show.

up

only display running interfaces.

master DEVICE

DEVICE specifies the master device which enslaves devices to show.

vrf NAME

NAME speficies the VRF which enslaves devices to show.

type TYPE

TYPE specifies the type of devices to show. Note that the type name is not checked against the list of supported types - instead it is sent as-is to the kernel. Later it is used to filter the returned interface list by comparing it with the relevant attribute in case the kernel didn't filter already. Therefore any string is accepted, but may lead to empty output.

### ip link xstats - display extended statistics
type TYPE

TYPE specifies the type of devices to display extended statistics for.

### ip link afstats - display address-family specific statistics
dev DEVICE

DEVICE specifies the device to display address-family statistics for.

### ip link help - display help
TYPE specifies which help of link type to display.

### GROUP
may be a number or a string from the file /etc/iproute2/group which can be manually filled.

## EXAMPLES
ip link show

Shows the state of all network interfaces on the system.

ip link show type bridge

Shows the bridge devices.

ip link show type vlan

Shows the vlan devices.

ip link show master br0

Shows devices enslaved by br0

ip link set dev ppp0 mtu 1400

Change the MTU the ppp0 device.

ip link add link eth0 name eth0.10 type vlan id 10

Creates a new vlan device eth0.10 on device eth0.

ip link delete dev eth0.10

Removes vlan device.

ip link help gre

Display help for the gre link type.

ip link add name tun1 type ipip remote 192.168.1.1 local 192.168.1.2 ttl 225 encap gue encap-sport auto encap-dport 5555 encap-csum encap-remcsum

Creates an IPIP that is encapsulated with Generic UDP Encapsulation, and the outer UDP checksum and remote checksum offload are enabled.

ip link set dev eth0 xdp obj prog.o

Attaches a XDP/BPF program to device eth0, where the program is located in prog.o, section "prog" (default section). In case a XDP/BPF program is already attached, throw an error.

ip -force link set dev eth0 xdp obj prog.o sec foo

Attaches a XDP/BPF program to device eth0, where the program is located in prog.o, section "foo". In case a XDP/BPF program is already attached, it will be overridden by the new one.

ip -force link set dev eth0 xdp pinned /sys/fs/bpf/foo

Attaches a XDP/BPF program to device eth0, where the program was previously pinned as an object node into BPF file system under name foo.

ip link set dev eth0 xdp off

If a XDP/BPF program is attached on device eth0, detach it and effectively turn off XDP for device eth0.

ip link add link wpan0 lowpan0 type lowpan

Creates a 6LoWPAN interface named lowpan0 on the underlying IEEE 802.15.4 device wpan0.

ip link add dev ip6erspan11 type ip6erspan seq key 102 local fc00:100::2 remote fc00:100::1 erspan_ver 2 erspan_dir ingress erspan_hwid 17

Creates a IP6ERSPAN version 2 interface named ip6erspan00.

## SEE ALSO
ip(8), ip-netns(8), ethtool(8), iptables(8)

## AUTHOR
Original Manpage by Michail Litvak <mci@owl.openwall.com>


ip-macsec

title: ip-macsec(8)

summary: MACsec device configuration

text:
# ip-macsec(8)

## NAME
ip-macsec - MACsec device configuration

## SYNOPSIS
ip link add link DEVICE name NAME type macsec [ [ address <lladdr> ] port PORT | sci <u64> ] [ cipher { default | gcm-aes-128 | gcm-aes-256"}][" icvlen ICVLEN ] [ encrypt { on | off } ] [ send_sci { on | off } ] [ end_station { on | off } ] [ scb { on | off } ] [ protect { on | off } ] [ replay { on | off } ] [ window WINDOW ] [ validate { strict | check | disabled } ] [ encodingsa SA ] [ offload { off | phy | mac } ]

ip macsec add DEV tx sa { 0..3 } [ OPTS ] key ID KEY

ip macsec set DEV tx sa { 0..3 } [ OPTS ]

ip macsec del DEV tx sa { 0..3 }

ip macsec add DEV rx SCI [ on | off ]

ip macsec set DEV rx SCI [ on | off ]

ip macsec del DEV rx SCI

ip macsec add DEV rx SCI sa { 0..3 } [ OPTS ] key ID KEY

ip macsec set DEV rx SCI sa { 0..3 } [ OPTS ]

ip macsec del DEV rx SCI sa { 0..3 }

ip macsec offload DEV { off | phy | mac }

ip macsec show [ DEV ]

OPTS := [ pn { 1..2^32-1 } ] [ on | off ]

SCI := { sci <u64> | port PORT address <lladdr> }

PORT := { 1..2^16-1 }

## DESCRIPTION
The ip macsec commands are used to configure transmit secure associations and receive secure channels and their secure associations on a MACsec device created with the ip link add command using the macsec type.

## EXAMPLES

### Create a MACsec device on link eth0 (offload is disabled by default)

```
# ip link add link eth0 macsec0 type macsec port 11 encrypt on
```

### Configure a secure association on that device

```
# ip macsec add macsec0 tx sa 0 pn 1024 on key 01 81818181818181818181818181818181
```

### Configure a receive channel

```
# ip macsec add macsec0 rx port 1234 address c6:19:52:8f:e6:a0
```

### Configure a receive association

```
# ip macsec add macsec0 rx port 1234 address c6:19:52:8f:e6:a0 sa 0 pn 1 on key 00 82828282828282828282828282828282
```

### Display MACsec configuration

```
# ip macsec show
```

### Configure offloading on an interface

```
# ip macsec offload macsec0 phy
```

### Configure offloading upon MACsec device creation

```
# ip link add link eth0 macsec0 type macsec port 11 encrypt on offload mac
```

## NOTES
This tool can be used to configure the 802.1AE keys of the interface. Note that 802.1AE uses GCM-AES with a initialization vector (IV) derived from the packet number. The same key must not be used with the same IV more than once. Instead, keys must be frequently regenerated and distributed. This tool is thus mostly for debugging and testing, or in combination with a user-space application that reconfigures the keys. It is wrong to just configure the keys statically and assume them to work indefinitely. The suggested and standardized way for key management is 802.1X-2010, which is implemented by wpa_supplicant.

## SEE ALSO
ip-link(8) wpa_supplicant(8)

## AUTHOR
Sabrina Dubroca <sd@queasysnail.net>


ip-maddress

title: ip-maddress(8)

summary: multicast addresses management

text:
# ip-maddress(8)

## NAME
ip-maddress - multicast addresses management

## SYNOPSIS

ip [ OPTIONS ] maddress { COMMAND | help }

ip maddress [ add | del ] MULTIADDR dev NAME

ip maddress show [ dev NAME ]

## DESCRIPTION
maddress objects are multicast addresses.

### ip maddress show - list multicast addresses
dev NAME (default)

the device name.

ip maddress add - add a multicast address

ip maddress delete - delete a multicast address

These commands attach/detach a static link-layer multicast address to listen on the interface. Note that it is impossible to join protocol multicast groups statically. This command only manages link-layer addresses.

address LLADDRESS (default)

the link-layer multicast address.

dev NAME

the device to join/leave this multicast address.

## SEE ALSO
ip(8)

## AUTHOR
Original Manpage by Michail Litvak <mci@owl.openwall.com>


ip-monitor

title: ip-monitor(8)

summary: state monitoring

text:
# ip-monitor(8)

## NAME
ip-monitor, rtmon - state monitoring

## SYNOPSIS

ip monitor [ all | OBJECT-LIST ] [ file FILENAME ] [ label ] [ all-nsid ] [ dev DEVICE ]

## OPTIONS
-t, -timestamp

Prints timestamp before the event message on the separated line in format:

Timestamp: <Day> <Month> <DD> <hh:mm:ss> <YYYY> <usecs> usec

<EVENT>

-ts, -tshort

Prints short timestamp before the event message on the same line in format:

[<YYYY>-<MM>-<DD>T<hh:mm:ss>.<ms>] <EVENT>

## DESCRIPTION
The ip utility can monitor the state of devices, addresses and routes continuously. This option has a slightly different format. Namely, the monitor command is the first in the command line and then the object list follows:

ip monitor [ all | OBJECT-LIST ] [ file FILENAME ] [ label ] [ all-nsid ] [ dev DEVICE ]

OBJECT-LIST is the list of object types that we want to monitor. It may contain link, address, route, mroute, prefix, neigh, netconf, rule, nsid and nexthop. If no file argument is given, ip opens RTNETLINK, listens on it and dumps state changes in the format described in previous sections.

If the label option is set, a prefix is displayed before each message to show the family of the message. For example:

[NEIGH]10.16.0.112 dev eth0 lladdr 00:04:23:df:2f:d0 REACHABLE [LINK]3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default

link/ether 52:54:00:12:34:57 brd ff:ff:ff:ff:ff:ff

If the all-nsid option is set, the program listens to all network namespaces that have a nsid assigned into the network namespace were the program is running. A prefix is displayed to show the network namespace where the message originates. Example:

[nsid 0]10.16.0.112 dev eth0 lladdr 00:04:23:df:2f:d0 REACHABLE

If the file option is given, the program does not listen on RTNETLINK, but opens the given file, and dumps its contents. The file should contain RTNETLINK messages saved in binary format. Such a file can be generated with the rtmon utility. This utility has a command line syntax similar to ip monitor. Ideally, rtmon should be started before the first network configuration command is issued. F.e. if you insert:

rtmon file /var/log/rtmon.log

in a startup script, you will be able to view the full history later.

Nevertheless, it is possible to start rtmon at any time. It prepends the history with the state snapshot dumped at the moment of starting.

If the dev option is given, the program prints only events related to this device.

## SEE ALSO
ip(8)

## AUTHOR
Original Manpage by Michail Litvak <mci@owl.openwall.com>

Manpage revised by Nicolas Dichtel <nicolas.dichtel@6wind.com>


ip-mptcp

title: ip-mptcp(8)

summary: MPTCP path manager configuration

text:
# ip-mptcp(8)

## NAME
ip-mptcp - MPTCP path manager configuration

## SYNOPSIS

ip [ OPTIONS ] mptcp { endpoint | limits | help }

ip mptcp endpoint add IFADDR [ port PORT ] [ dev IFNAME ] [ id ID ] [ FLAG-LIST ]

ip mptcp endpoint del id ID

ip mptcp endpoint show [ id ID ]

ip mptcp endpoint flush

FLAG-LIST := [ FLAG-LIST ] FLAG

FLAG := [ signal | subflow | backup ]

ip mptcp limits set [ subflow SUBFLOW_NR ] [ add_addr_accepted ADD_ADDR_ACCEPTED_NR ]

ip mptcp limits show

ip mptcp monitor

## DESCRIPTION
MPTCP is a transport protocol built on top of TCP that allows TCP connections to use multiple paths to maximize resource usage and increase redundancy. The ip-mptcp sub-commands allow configuring several aspects of the MPTCP path manager, which is in charge of subflows creation:

The endpoint object specifies the IP addresses that will be used and/or announced for additional subflows:

ip mptcp endpoint add

add new MPTCP endpoint

ip mptcp endpoint delete

delete existing MPTCP endpoint

ip mptcp endpoint show

get existing MPTCP endpoint

ip mptcp endpoint flush

flush all existing MPTCP endpoints

PORT

When a port number is specified, incoming MPTCP subflows for already established MPTCP sockets will be accepted on the specified port, regardless the original listener port accepting the first MPTCP subflow and/or this peer being actually on the client side. ID is a unique numeric identifier for the given endpoint

signal

the endpoint will be announced/signalled to each peer via an ADD_ADDR MPTCP sub-option

subflow

if additional subflow creation is allowed by MPTCP limits, the endpoint will be used as the source address to create an additional subflow after that the MPTCP connection is established.

backup

the endpoint will be announced as a backup address, if this is a signal endpoint, or the subflow will be created as a backup one if this is a subflow endpoint

The limits object specifies the constraints for subflow creations:

ip mptcp limits show

get current MPTCP subflow creation limits

ip mptcp limits set

change the MPTCP subflow creation limits

SUBFLOW_NR

specifies the maximum number of additional subflows allowed for each MPTCP connection. Additional subflows can be created due to: incoming accepted ADD_ADDR option, local subflow endpoints, additional subflows started by the peer.

ADD_ADDR_ACCEPTED_NR

specifies the maximum number of ADD_ADDR suboptions accepted for each MPTCP connection. The MPTCP path manager will try to create a new subflow for each accepted ADD_ADDR option, respecting the SUBFLOW_NR limit.

monitor displays creation and deletion of MPTCP connections as well as addition or removal of remote addresses and subflows.

## AUTHOR
Original Manpage by Paolo Abeni <pabeni@redhat.com>


ip-mroute

title: ip-mroute(8)

summary: multicast routing cache management

text:
# ip-mroute(8)

## NAME
ip-mroute - multicast routing cache management

## SYNOPSIS

ip mroute show [ [ to ] PREFIX ] [ from PREFIX ] [ iif DEVICE ] [ table TABLE_ID ]

## DESCRIPTION
mroute objects are multicast routing cache entries created by a user-level mrouting daemon (f.e. pimd or mrouted ).

Due to the limitations of the current interface to the multicast routing engine, it is impossible to change mroute objects administratively, so we can only display them. This limitation will be removed in the future.

### ip mroute show - list mroute cache entries
to PREFIX (default)

the prefix selecting the destination multicast addresses to list.

iif NAME

the interface on which multicast packets are received.

from PREFIX

the prefix selecting the IP source addresses of the multicast route.

table TABLE_ID

the table id selecting the multicast table. It can be local, main, default, all or a number.

## SEE ALSO
ip(8)

## AUTHOR
Original Manpage by Michail Litvak <mci@owl.openwall.com>


ip-neighbour

title: ip-neighbour(8)

summary: neighbour/arp tables management.

text:
# ip-neighbour(8)

## NAME
ip-neighbour - neighbour/arp tables management.

## SYNOPSIS

ip [ OPTIONS ] neigh { COMMAND | help }

ip neigh { add | del | change | replace } { ADDR [ lladdr LLADDR ] [ nud STATE ] | proxy ADDR } [ dev DEV ] [ router ] [ extern_learn ]

ip neigh { show | flush } [ proxy ] [ to PREFIX ] [ dev DEV ] [ nud STATE ] [ vrf NAME ]

ip neigh get ADDR dev DEV

STATE := { permanent | noarp | stale | reachable | none | incomplete | delay | probe | failed }

## DESCRIPTION
The ip neigh command manipulates neighbour objects that establish bindings between protocol addresses and link layer addresses for hosts sharing the same link. Neighbour entries are organized into tables. The IPv4 neighbour table is also known by another name - the ARP table.

The corresponding commands display neighbour bindings and their properties, add new neighbour entries and delete old ones.

ip neighbour add

add a new neighbour entry

ip neighbour change

change an existing entry

ip neighbour replace

add a new entry or change an existing one

These commands create new neighbour records or update existing ones.

to ADDRESS (default)

the protocol address of the neighbour. It is either an IPv4 or IPv6 address.

dev NAME

the interface to which this neighbour is attached.

proxy

indicates whether we are proxying for this neighbour entry

router

indicates whether neighbour is a router

extern_learn

this neigh entry was learned externally. This option can be used to indicate to the kernel that this is a controller learnt dynamic entry. Kernel will not gc such an entry.

lladdr LLADDRESS

the link layer address of the neighbour. LLADDRESS can also be null.

nud STATE

the state of the neighbour entry. nud is an abbreviation for 'Neighbour Unreachability Detection'. The state can take one of the following values:

permanent

the neighbour entry is valid forever and can be only be removed administratively.

noarp

the neighbour entry is valid. No attempts to validate this entry will be made but it can be removed when its lifetime expires.

reachable

the neighbour entry is valid until the reachability timeout expires.

stale

the neighbour entry is valid but suspicious. This option to ip neigh does not change the neighbour state if it was valid and the address is not changed by this command.

none

this is a pseudo state used when initially creating a neighbour entry or after trying to remove it before it becomes free to do so.

incomplete

the neighbour entry has not (yet) been validated/resolved.

delay

neighbor entry validation is currently delayed.

probe

neighbor is being probed.

failed

max number of probes exceeded without success, neighbor validation has ultimately failed.

ip neighbour delete

delete a neighbour entry

The arguments are the same as with ip neigh add, except that lladdr and nud are ignored.

Warning: Attempts to delete or manually change a noarp entry created by the kernel may result in unpredictable behaviour. Particularly, the kernel may try to resolve this address even on a NOARP interface or if the address is multicast or broadcast.

ip neighbour show

list neighbour entries

to ADDRESS (default)

the prefix selecting the neighbours to list.

dev NAME

only list the neighbours attached to this device.

vrf NAME

only list the neighbours for given VRF.

proxy

list neighbour proxies.

unused

only list neighbours which are not currently in use.

nud STATE

only list neighbour entries in this state. NUD_STATE takes values listed below or the special value all which means all states. This option may occur more than once. If this option is absent, ip lists all entries except for none and noarp.

ip neighbour flush

flush neighbour entries

This command has the same arguments as show. The differences are that it does not run when no arguments are given, and that the default neighbour states to be flushed do not include permanent and noarp.

With the -statistics option, the command becomes verbose. It prints out the number of deleted neighbours and the number of rounds made to flush the neighbour table. If the option is given twice, ip neigh flush also dumps all the deleted neighbours.

ip neigh get

lookup a neighbour entry to a destination given a device

proxy

indicates whether we should lookup a proxy neighbour entry

to ADDRESS (default)

the prefix selecting the neighbour to query.

dev NAME

get neighbour entry attached to this device.

## EXAMPLES
ip neighbour

Shows the current neighbour table in kernel.

ip neigh flush dev eth0

Removes entries in the neighbour table on device eth0.

ip neigh get 10.0.1.10 dev eth0

Performs a neighbour lookup in the kernel and returns a neighbour entry.

## SEE ALSO
ip(8)

## AUTHOR
Original Manpage by Michail Litvak <mci@owl.openwall.com>


ip-netconf

title: ip-netconf(8)

summary: network configuration monitoring

text:
# ip-netconf(8)

## NAME
ip-netconf - network configuration monitoring

## SYNOPSIS

ip [ ip-OPTIONS ] netconf show [ dev NAME ]

## DESCRIPTION
The ip netconf utility can monitor IPv4 and IPv6 parameters (see /proc/sys/net/ipv[4|6]/conf/[all|DEV]/) like forwarding, rp_filter, proxy_neigh, ignore_routes_with_linkdown or mc_forwarding status.

If no interface is specified, the entry all is displayed.

### ip netconf show - display network parameters
dev NAME

the name of the device to display network parameters for.

## SEE ALSO
ip(8)

## AUTHOR
Original Manpage by Nicolas Dichtel <nicolas.dichtel@6wind.com>