1994-05-26 06:35:07 +00:00
|
|
|
.\" Copyright (c) 1983, 1991, 1993
|
|
|
|
.\" The Regents of the University of California. All rights reserved.
|
|
|
|
.\"
|
|
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
|
|
.\" modification, are permitted provided that the following conditions
|
|
|
|
.\" are met:
|
|
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
|
|
.\" documentation and/or other materials provided with the distribution.
|
2017-02-28 23:42:47 +00:00
|
|
|
.\" 3. Neither the name of the University nor the names of its contributors
|
1994-05-26 06:35:07 +00:00
|
|
|
.\" may be used to endorse or promote products derived from this software
|
|
|
|
.\" without specific prior written permission.
|
|
|
|
.\"
|
|
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
.\" SUCH DAMAGE.
|
|
|
|
.\"
|
1996-02-06 20:36:15 +00:00
|
|
|
.\" From: @(#)ifconfig.8 8.3 (Berkeley) 1/5/94
|
1999-08-28 00:22:10 +00:00
|
|
|
.\" $FreeBSD$
|
1994-05-26 06:35:07 +00:00
|
|
|
.\"
|
2020-06-04 13:06:49 +00:00
|
|
|
.Dd June 4, 2020
|
1994-05-26 06:35:07 +00:00
|
|
|
.Dt IFCONFIG 8
|
2001-07-05 12:37:08 +00:00
|
|
|
.Os
|
1994-05-26 06:35:07 +00:00
|
|
|
.Sh NAME
|
|
|
|
.Nm ifconfig
|
|
|
|
.Nd configure network interface parameters
|
|
|
|
.Sh SYNOPSIS
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
2016-05-31 17:30:08 +00:00
|
|
|
.Op Fl f Ar type:format Ns Op Ar ,type:format
|
2000-07-19 17:24:53 +00:00
|
|
|
.Op Fl L
|
2005-07-14 18:33:21 +00:00
|
|
|
.Op Fl k
|
2001-05-29 09:13:44 +00:00
|
|
|
.Op Fl m
|
2007-05-22 17:41:09 +00:00
|
|
|
.Op Fl n
|
2000-07-19 17:24:53 +00:00
|
|
|
.Ar interface
|
2001-07-02 20:52:34 +00:00
|
|
|
.Op Cm create
|
2011-05-31 14:40:21 +00:00
|
|
|
.Ar address_family
|
1994-05-26 06:35:07 +00:00
|
|
|
.Oo
|
2002-01-07 06:51:19 +00:00
|
|
|
.Ar address
|
1994-05-26 06:35:07 +00:00
|
|
|
.Op Ar dest_address
|
|
|
|
.Oc
|
|
|
|
.Op Ar parameters
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
2001-07-02 20:52:34 +00:00
|
|
|
.Ar interface
|
|
|
|
.Cm destroy
|
|
|
|
.Nm
|
1997-05-03 23:03:56 +00:00
|
|
|
.Fl a
|
2000-07-19 17:24:53 +00:00
|
|
|
.Op Fl L
|
1997-05-03 23:03:56 +00:00
|
|
|
.Op Fl d
|
2020-06-04 14:44:44 +00:00
|
|
|
.Op Fl [gG] Ar groupname
|
2001-05-29 09:13:44 +00:00
|
|
|
.Op Fl m
|
1997-05-03 23:03:56 +00:00
|
|
|
.Op Fl u
|
2004-12-08 19:18:07 +00:00
|
|
|
.Op Fl v
|
1998-07-06 06:53:43 +00:00
|
|
|
.Op Ar address_family
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
1997-05-03 23:03:56 +00:00
|
|
|
.Fl l
|
|
|
|
.Op Fl d
|
|
|
|
.Op Fl u
|
2001-07-05 12:37:08 +00:00
|
|
|
.Op Ar address_family
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
2000-07-19 17:24:53 +00:00
|
|
|
.Op Fl L
|
|
|
|
.Op Fl d
|
2005-07-14 18:33:21 +00:00
|
|
|
.Op Fl k
|
2001-05-29 09:13:44 +00:00
|
|
|
.Op Fl m
|
2000-07-19 17:24:53 +00:00
|
|
|
.Op Fl u
|
2004-12-08 19:18:07 +00:00
|
|
|
.Op Fl v
|
2001-07-02 20:52:34 +00:00
|
|
|
.Op Fl C
|
2006-06-19 22:20:45 +00:00
|
|
|
.Nm
|
|
|
|
.Op Fl g Ar groupname
|
1994-05-26 06:35:07 +00:00
|
|
|
.Sh DESCRIPTION
|
2002-07-06 19:34:18 +00:00
|
|
|
The
|
|
|
|
.Nm
|
|
|
|
utility is used to assign an address
|
1994-05-26 06:35:07 +00:00
|
|
|
to a network interface and/or configure
|
|
|
|
network interface parameters.
|
2002-07-06 19:34:18 +00:00
|
|
|
The
|
|
|
|
.Nm
|
|
|
|
utility must be used at boot time to define the network address
|
1994-05-26 06:35:07 +00:00
|
|
|
of each interface present on a machine; it may also be used at
|
|
|
|
a later time to redefine an interface's address
|
|
|
|
or other operating parameters.
|
|
|
|
.Pp
|
1998-07-06 06:53:43 +00:00
|
|
|
The following options are available:
|
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Ar address
|
1994-05-26 06:35:07 +00:00
|
|
|
For the
|
1998-07-06 06:53:43 +00:00
|
|
|
.Tn DARPA Ns -Internet
|
1994-05-26 06:35:07 +00:00
|
|
|
family,
|
|
|
|
the address is either a host name present in the host name data
|
2001-07-05 12:37:08 +00:00
|
|
|
base,
|
1994-05-26 06:35:07 +00:00
|
|
|
.Xr hosts 5 ,
|
|
|
|
or a
|
|
|
|
.Tn DARPA
|
|
|
|
Internet address expressed in the Internet standard
|
|
|
|
.Dq dot notation .
|
2001-05-05 19:53:20 +00:00
|
|
|
.Pp
|
|
|
|
It is also possible to use the CIDR notation (also known as the
|
|
|
|
slash notation) to include the netmask.
|
|
|
|
That is, one can specify an address like
|
2001-05-07 07:42:56 +00:00
|
|
|
.Li 192.168.0.1/16 .
|
2002-01-09 15:10:31 +00:00
|
|
|
.Pp
|
2008-10-19 09:45:29 +00:00
|
|
|
For the
|
2002-01-09 15:10:31 +00:00
|
|
|
.Dq inet6
|
|
|
|
family, it is also possible to specify the prefix length using the slash
|
|
|
|
notation, like
|
|
|
|
.Li ::1/128 .
|
|
|
|
See the
|
|
|
|
.Cm prefixlen
|
|
|
|
parameter below for more information.
|
1996-02-13 17:30:37 +00:00
|
|
|
.\" For the Xerox Network Systems(tm) family,
|
2001-07-05 12:37:08 +00:00
|
|
|
.\" addresses are
|
1996-02-13 17:30:37 +00:00
|
|
|
.\" .Ar net:a.b.c.d.e.f ,
|
|
|
|
.\" where
|
|
|
|
.\" .Ar net
|
|
|
|
.\" is the assigned network number (in decimal),
|
|
|
|
.\" and each of the six bytes of the host number,
|
|
|
|
.\" .Ar a
|
|
|
|
.\" through
|
|
|
|
.\" .Ar f ,
|
|
|
|
.\" are specified in hexadecimal.
|
2001-07-05 12:37:08 +00:00
|
|
|
.\" The host number may be omitted on IEEE 802 protocol
|
2001-06-02 04:09:53 +00:00
|
|
|
.\" (Ethernet, FDDI, and Token Ring) interfaces,
|
1996-02-13 17:30:37 +00:00
|
|
|
.\" which use the hardware physical address,
|
|
|
|
.\" and on interfaces other than the first.
|
1996-02-06 20:36:15 +00:00
|
|
|
.\" For the
|
|
|
|
.\" .Tn ISO
|
|
|
|
.\" family, addresses are specified as a long hexadecimal string,
|
2001-07-05 12:37:08 +00:00
|
|
|
.\" as in the Xerox family.
|
|
|
|
.\" However, two consecutive dots imply a zero
|
1996-02-06 20:36:15 +00:00
|
|
|
.\" byte, and the dots are optional, if the user wishes to (carefully)
|
|
|
|
.\" count out long strings of digits in network byte order.
|
2002-03-27 14:29:23 +00:00
|
|
|
.Pp
|
|
|
|
The link-level
|
|
|
|
.Pq Dq link
|
|
|
|
address
|
|
|
|
is specified as a series of colon-separated hex digits.
|
2014-06-06 00:22:19 +00:00
|
|
|
This can be used to, for example,
|
|
|
|
set a new MAC address on an Ethernet interface, though the
|
|
|
|
mechanism used is not Ethernet specific.
|
2016-09-16 04:22:21 +00:00
|
|
|
Use the
|
|
|
|
.Pq Dq random
|
|
|
|
keyword to set a randomly generated MAC address.
|
|
|
|
A randomly-generated MAC address might be the same as one already in use
|
|
|
|
in the network.
|
|
|
|
Such duplications are extremely unlikely.
|
2002-03-27 14:29:23 +00:00
|
|
|
If the interface is already
|
|
|
|
up when this option is used, it will be briefly brought down and
|
|
|
|
then brought back up again in order to ensure that the receive
|
2014-06-06 00:22:19 +00:00
|
|
|
filter in the underlying Ethernet hardware is properly reprogrammed.
|
1994-05-26 06:35:07 +00:00
|
|
|
.It Ar address_family
|
1998-07-06 06:53:43 +00:00
|
|
|
Specify the
|
2001-07-05 12:37:08 +00:00
|
|
|
address family
|
1994-05-26 06:35:07 +00:00
|
|
|
which affects interpretation of the remaining parameters.
|
|
|
|
Since an interface can receive transmissions in differing protocols
|
1996-01-29 23:52:43 +00:00
|
|
|
with different naming schemes, specifying the address family is recommended.
|
1994-05-26 06:35:07 +00:00
|
|
|
The address or protocol families currently
|
|
|
|
supported are
|
1996-07-09 02:38:13 +00:00
|
|
|
.Dq inet ,
|
1999-12-07 17:39:16 +00:00
|
|
|
.Dq inet6 ,
|
1994-05-26 06:35:07 +00:00
|
|
|
and
|
2002-03-27 14:29:23 +00:00
|
|
|
.Dq link .
|
2011-05-31 14:40:21 +00:00
|
|
|
The default if available is
|
|
|
|
.Dq inet
|
|
|
|
or otherwise
|
|
|
|
.Dq link .
|
2002-03-27 14:29:23 +00:00
|
|
|
.Dq ether
|
|
|
|
and
|
|
|
|
.Dq lladdr
|
|
|
|
are synonyms for
|
|
|
|
.Dq link .
|
2014-05-27 20:45:15 +00:00
|
|
|
When using the
|
|
|
|
.Fl l
|
|
|
|
flag, the
|
|
|
|
.Dq ether
|
|
|
|
address family has special meaning and is no longer synonymous with
|
|
|
|
.Dq link
|
|
|
|
or
|
|
|
|
.Dq lladdr .
|
|
|
|
Specifying
|
|
|
|
.Fl l Dq ether
|
2014-06-06 00:22:19 +00:00
|
|
|
will list only Ethernet interfaces, excluding all other interface types,
|
2014-05-27 20:45:15 +00:00
|
|
|
including the loopback interface.
|
1998-07-06 06:53:43 +00:00
|
|
|
.It Ar dest_address
|
|
|
|
Specify the address of the correspondent on the other end
|
|
|
|
of a point to point link.
|
|
|
|
.It Ar interface
|
|
|
|
This
|
1994-05-26 06:35:07 +00:00
|
|
|
parameter is a string of the form
|
|
|
|
.Dq name unit ,
|
|
|
|
for example,
|
2019-05-18 21:01:36 +00:00
|
|
|
.Dq Li em0 .
|
2006-06-19 22:20:45 +00:00
|
|
|
.It Ar groupname
|
|
|
|
List the interfaces in the given group.
|
1994-05-26 06:35:07 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
2016-05-31 17:30:08 +00:00
|
|
|
The output format of
|
|
|
|
.Nm
|
|
|
|
can be controlled using the
|
|
|
|
.Fl f
|
|
|
|
flag or the
|
|
|
|
.Ev IFCONFIG_FORMAT
|
|
|
|
environment variable.
|
|
|
|
The format is specified as a comma separated list of
|
|
|
|
.Sy type:format
|
|
|
|
pairs.
|
|
|
|
See the
|
|
|
|
.Sx EXAMPLES
|
|
|
|
section for more information.
|
|
|
|
The
|
|
|
|
.Sy types
|
|
|
|
and their associated
|
|
|
|
.Sy format
|
|
|
|
strings are:
|
2016-06-02 03:16:02 +00:00
|
|
|
.Bl -tag -width ether
|
2016-05-31 17:30:08 +00:00
|
|
|
.It Sy addr
|
|
|
|
Adjust the display of inet and inet6 addresses
|
|
|
|
.Bl -tag -width default
|
|
|
|
.It Sy default
|
|
|
|
Display inet and inet6 addresses in the default format,
|
|
|
|
.Sy numeric
|
|
|
|
.It Sy fqdn
|
|
|
|
Display inet and inet6 addresses as fully qualified domain names
|
|
|
|
.Pq FQDN
|
|
|
|
.It Sy host
|
|
|
|
Display inet and inet6 addresses as unqualified hostnames
|
|
|
|
.It Sy numeric
|
|
|
|
Display inet and inet6 addresses in numeric format
|
|
|
|
.El
|
|
|
|
.It Sy ether
|
|
|
|
Adjust the display of link-level ethernet (MAC) addresses
|
|
|
|
.Bl -tag -width default
|
|
|
|
.It Sy colon
|
|
|
|
Separate address segments with a colon
|
|
|
|
.It Sy dash
|
|
|
|
Separate address segments with a dash
|
|
|
|
.It Sy default
|
|
|
|
Display ethernet addresses in the default format,
|
|
|
|
.Sy colon
|
|
|
|
.El
|
|
|
|
.It Sy inet
|
|
|
|
Adjust the display of inet address subnet masks:
|
|
|
|
.Bl -tag -width default
|
|
|
|
.It Sy cidr
|
|
|
|
Display subnet masks in CIDR notation, for example:
|
|
|
|
.br
|
|
|
|
10.0.0.0/8 or 203.0.113.224/26
|
|
|
|
.It Sy default
|
|
|
|
Display subnet masks in the default format,
|
|
|
|
.Sy hex
|
|
|
|
.It Sy dotted
|
|
|
|
Display subnet masks in dotted quad notation, for example:
|
|
|
|
.br
|
|
|
|
255.255.0.0 or 255.255.255.192
|
|
|
|
.It Sy hex
|
2016-09-16 04:22:21 +00:00
|
|
|
Display subnet masks in hexadecimal, for example:
|
2016-05-31 17:30:08 +00:00
|
|
|
.br
|
|
|
|
0xffff0000 or 0xffffffc0
|
|
|
|
.El
|
|
|
|
.It Sy inet6
|
|
|
|
Adjust the display of inet6 address prefixes (subnet masks):
|
|
|
|
.Bl -tag -width default
|
|
|
|
.It Sy cidr
|
|
|
|
Display subnet prefix in CIDR notation, for example:
|
|
|
|
.br
|
|
|
|
::1/128 or fe80::1%lo0/64
|
|
|
|
.It Sy default
|
|
|
|
Display subnet prefix in the default format
|
|
|
|
.Sy numeric
|
|
|
|
.It Sy numeric
|
|
|
|
Display subnet prefix in integer format, for example:
|
|
|
|
.br
|
|
|
|
prefixlen 64
|
|
|
|
.El
|
|
|
|
.El
|
|
|
|
.Pp
|
2001-07-05 12:37:08 +00:00
|
|
|
The following parameters may be set with
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm :
|
1998-07-06 06:53:43 +00:00
|
|
|
.Bl -tag -width indent
|
2000-02-26 18:55:39 +00:00
|
|
|
.It Cm add
|
2001-02-01 16:38:02 +00:00
|
|
|
Another name for the
|
|
|
|
.Cm alias
|
|
|
|
parameter.
|
|
|
|
Introduced for compatibility
|
2001-07-05 12:37:08 +00:00
|
|
|
with
|
|
|
|
.Bsx .
|
1994-05-26 06:35:07 +00:00
|
|
|
.It Cm alias
|
|
|
|
Establish an additional network address for this interface.
|
|
|
|
This is sometimes useful when changing network numbers, and
|
|
|
|
one wishes to accept packets addressed to the old interface.
|
2000-02-26 18:59:34 +00:00
|
|
|
If the address is on the same subnet as the first network address
|
2002-05-11 11:35:35 +00:00
|
|
|
for this interface, a non-conflicting netmask must be given.
|
|
|
|
Usually
|
2001-07-05 12:37:08 +00:00
|
|
|
.Li 0xffffffff
|
2002-05-11 11:35:35 +00:00
|
|
|
is most appropriate.
|
2000-05-20 18:05:24 +00:00
|
|
|
.It Fl alias
|
|
|
|
Remove the network address specified.
|
|
|
|
This would be used if you incorrectly specified an alias, or it
|
|
|
|
was no longer needed.
|
|
|
|
If you have incorrectly set an NS address having the side effect
|
|
|
|
of specifying the host portion, removing all NS addresses will
|
|
|
|
allow you to respecify the host portion.
|
1999-12-07 17:39:16 +00:00
|
|
|
.It Cm anycast
|
2001-07-05 12:37:08 +00:00
|
|
|
(Inet6 only.)
|
1999-12-07 17:39:16 +00:00
|
|
|
Specify that the address configured is an anycast address.
|
|
|
|
Based on the current specification,
|
|
|
|
only routers may configure anycast addresses.
|
|
|
|
Anycast address will not be used as source address of any of outgoing
|
|
|
|
IPv6 packets.
|
1994-05-26 06:35:07 +00:00
|
|
|
.It Cm arp
|
2001-07-05 12:37:08 +00:00
|
|
|
Enable the use of the Address Resolution Protocol
|
|
|
|
.Pq Xr arp 4
|
|
|
|
in mapping
|
1994-05-26 06:35:07 +00:00
|
|
|
between network level addresses and link level addresses (default).
|
|
|
|
This is currently implemented for mapping between
|
|
|
|
.Tn DARPA
|
|
|
|
Internet
|
2001-06-02 04:09:53 +00:00
|
|
|
addresses and
|
|
|
|
.Tn IEEE
|
|
|
|
802 48-bit MAC addresses (Ethernet, FDDI, and Token Ring addresses).
|
1994-05-26 06:35:07 +00:00
|
|
|
.It Fl arp
|
2001-07-05 12:37:08 +00:00
|
|
|
Disable the use of the Address Resolution Protocol
|
|
|
|
.Pq Xr arp 4 .
|
2003-10-01 08:32:37 +00:00
|
|
|
.It Cm staticarp
|
|
|
|
If the Address Resolution Protocol is enabled,
|
|
|
|
the host will only reply to requests for its addresses,
|
|
|
|
and will never send any requests.
|
|
|
|
.It Fl staticarp
|
|
|
|
If the Address Resolution Protocol is enabled,
|
|
|
|
the host will perform normally,
|
|
|
|
sending out requests and listening for replies.
|
1994-05-26 06:35:07 +00:00
|
|
|
.It Cm broadcast
|
2001-07-05 12:37:08 +00:00
|
|
|
(Inet only.)
|
1994-05-26 06:35:07 +00:00
|
|
|
Specify the address to use to represent broadcasts to the
|
|
|
|
network.
|
|
|
|
The default broadcast address is the address with a host part of all 1's.
|
|
|
|
.It Cm debug
|
|
|
|
Enable driver dependent debugging code; usually, this turns on
|
|
|
|
extra console error logging.
|
|
|
|
.It Fl debug
|
|
|
|
Disable driver dependent debugging code.
|
2002-08-19 15:16:38 +00:00
|
|
|
.It Cm promisc
|
|
|
|
Put interface into permanently promiscuous mode.
|
|
|
|
.It Fl promisc
|
|
|
|
Disable permanently promiscuous mode.
|
1994-05-26 06:35:07 +00:00
|
|
|
.It Cm delete
|
2001-02-01 16:38:02 +00:00
|
|
|
Another name for the
|
|
|
|
.Fl alias
|
|
|
|
parameter.
|
2010-01-27 00:30:07 +00:00
|
|
|
.It Cm description Ar value , Cm descr Ar value
|
|
|
|
Specify a description of the interface.
|
|
|
|
This can be used to label interfaces in situations where they may
|
|
|
|
otherwise be difficult to distinguish.
|
|
|
|
.It Cm -description , Cm -descr
|
|
|
|
Clear the interface description.
|
1994-05-26 06:35:07 +00:00
|
|
|
.It Cm down
|
2001-02-01 16:38:02 +00:00
|
|
|
Mark an interface
|
|
|
|
.Dq down .
|
|
|
|
When an interface is marked
|
|
|
|
.Dq down ,
|
|
|
|
the system will not attempt to
|
2001-07-05 12:37:08 +00:00
|
|
|
transmit messages through that interface.
|
1994-05-26 06:35:07 +00:00
|
|
|
If possible, the interface will be reset to disable reception as well.
|
|
|
|
This action does not automatically disable routes using the interface.
|
2020-05-27 08:16:17 +00:00
|
|
|
.It Cm group Ar groupname
|
2006-06-19 22:20:45 +00:00
|
|
|
Assign the interface to a
|
|
|
|
.Dq group .
|
|
|
|
Any interface can be in multiple groups.
|
|
|
|
.Pp
|
|
|
|
Cloned interfaces are members of their interface family group by default.
|
|
|
|
For example, a PPP interface such as
|
|
|
|
.Em ppp0
|
|
|
|
is a member of the PPP interface family group,
|
|
|
|
.Em ppp .
|
|
|
|
.\" The interface(s) the default route(s) point to are members of the
|
|
|
|
.\" .Em egress
|
|
|
|
.\" interface group.
|
2020-05-27 08:16:17 +00:00
|
|
|
.It Cm -group Ar groupname
|
2006-06-19 22:20:45 +00:00
|
|
|
Remove the interface from the given
|
|
|
|
.Dq group .
|
2002-06-15 15:35:24 +00:00
|
|
|
.It Cm eui64
|
|
|
|
(Inet6 only.)
|
|
|
|
Fill interface index
|
2002-08-13 11:51:03 +00:00
|
|
|
(lowermost 64bit of an IPv6 address)
|
2002-06-15 15:35:24 +00:00
|
|
|
automatically.
|
2011-07-03 12:22:02 +00:00
|
|
|
.It Cm fib Ar fib_number
|
|
|
|
Specify interface FIB.
|
|
|
|
A FIB
|
|
|
|
.Ar fib_number
|
|
|
|
is assigned to all frames or packets received on that interface.
|
2012-11-07 19:26:32 +00:00
|
|
|
The FIB is not inherited, e.g., vlans or other sub-interfaces will use
|
2011-07-03 12:22:02 +00:00
|
|
|
the default FIB (0) irrespective of the parent interface's FIB.
|
|
|
|
The kernel needs to be tuned to support more than the default FIB
|
|
|
|
using the
|
|
|
|
.Va ROUTETABLES
|
|
|
|
kernel configuration option, or the
|
|
|
|
.Va net.fibs
|
|
|
|
tunable.
|
2015-05-12 07:37:27 +00:00
|
|
|
.It Cm tunnelfib Ar fib_number
|
|
|
|
Specify tunnel FIB.
|
|
|
|
A FIB
|
|
|
|
.Ar fib_number
|
|
|
|
is assigned to all packets encapsulated by tunnel interface, e.g.,
|
|
|
|
.Xr gif 4
|
|
|
|
and
|
|
|
|
.Xr gre 4 .
|
2002-10-25 22:40:37 +00:00
|
|
|
.It Cm maclabel Ar label
|
|
|
|
If Mandatory Access Control support is enabled in the kernel,
|
|
|
|
set the MAC label to
|
|
|
|
.Ar label .
|
|
|
|
.\" (see
|
|
|
|
.\" .Xr maclabel 7 ) .
|
1997-05-03 23:03:56 +00:00
|
|
|
.It Cm media Ar type
|
1997-09-27 02:55:39 +00:00
|
|
|
If the driver supports the media selection system, set the media type
|
|
|
|
of the interface to
|
1997-05-03 23:03:56 +00:00
|
|
|
.Ar type .
|
|
|
|
Some interfaces support the mutually exclusive use of one of several
|
2001-07-05 12:37:08 +00:00
|
|
|
different physical media connectors.
|
2005-11-18 10:36:29 +00:00
|
|
|
For example, a 10Mbit/s Ethernet
|
1997-05-03 23:03:56 +00:00
|
|
|
interface might support the use of either
|
|
|
|
.Tn AUI
|
2001-07-05 12:37:08 +00:00
|
|
|
or twisted pair connectors.
|
|
|
|
Setting the media type to
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm 10base5/AUI
|
1997-05-03 23:03:56 +00:00
|
|
|
would change the currently active connector to the AUI port.
|
|
|
|
Setting it to
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm 10baseT/UTP
|
2001-07-05 12:37:08 +00:00
|
|
|
would activate twisted pair.
|
|
|
|
Refer to the interfaces' driver
|
1997-09-27 02:55:39 +00:00
|
|
|
specific documentation or man page for a complete list of the
|
|
|
|
available types.
|
1997-05-03 23:03:56 +00:00
|
|
|
.It Cm mediaopt Ar opts
|
1997-09-27 02:55:39 +00:00
|
|
|
If the driver supports the media selection system, set the specified
|
|
|
|
media options on the interface.
|
2001-07-05 12:37:08 +00:00
|
|
|
The
|
|
|
|
.Ar opts
|
|
|
|
argument
|
1997-05-03 23:03:56 +00:00
|
|
|
is a comma delimited list of options to apply to the interface.
|
|
|
|
Refer to the interfaces' driver specific man page for a complete
|
|
|
|
list of available options.
|
|
|
|
.It Fl mediaopt Ar opts
|
1997-09-27 02:55:39 +00:00
|
|
|
If the driver supports the media selection system, disable the
|
|
|
|
specified media options on the interface.
|
2003-04-28 16:47:40 +00:00
|
|
|
.It Cm mode Ar mode
|
|
|
|
If the driver supports the media selection system, set the specified
|
|
|
|
operating mode on the interface to
|
|
|
|
.Ar mode .
|
|
|
|
For IEEE 802.11 wireless interfaces that support multiple operating modes
|
2003-05-14 16:22:16 +00:00
|
|
|
this directive is used to select between 802.11a
|
2005-11-18 10:36:29 +00:00
|
|
|
.Pq Cm 11a ,
|
2003-05-14 16:22:16 +00:00
|
|
|
802.11b
|
2005-11-18 10:36:29 +00:00
|
|
|
.Pq Cm 11b ,
|
2003-05-14 16:22:16 +00:00
|
|
|
and 802.11g
|
2005-11-18 10:36:29 +00:00
|
|
|
.Pq Cm 11g
|
2003-04-28 16:47:40 +00:00
|
|
|
operating modes.
|
Implement kernel support for hardware rate limited sockets.
- Add RATELIMIT kernel configuration keyword which must be set to
enable the new functionality.
- Add support for hardware driven, Receive Side Scaling, RSS aware, rate
limited sendqueues and expose the functionality through the already
established SO_MAX_PACING_RATE setsockopt(). The API support rates in
the range from 1 to 4Gbytes/s which are suitable for regular TCP and
UDP streams. The setsockopt(2) manual page has been updated.
- Add rate limit function callback API to "struct ifnet" which supports
the following operations: if_snd_tag_alloc(), if_snd_tag_modify(),
if_snd_tag_query() and if_snd_tag_free().
- Add support to ifconfig to view, set and clear the IFCAP_TXRTLMT
flag, which tells if a network driver supports rate limiting or not.
- This patch also adds support for rate limiting through VLAN and LAGG
intermediate network devices.
- How rate limiting works:
1) The userspace application calls setsockopt() after accepting or
making a new connection to set the rate which is then stored in the
socket structure in the kernel. Later on when packets are transmitted
a check is made in the transmit path for rate changes. A rate change
implies a non-blocking ifp->if_snd_tag_alloc() call will be made to the
destination network interface, which then sets up a custom sendqueue
with the given rate limitation parameter. A "struct m_snd_tag" pointer is
returned which serves as a "snd_tag" hint in the m_pkthdr for the
subsequently transmitted mbufs.
2) When the network driver sees the "m->m_pkthdr.snd_tag" different
from NULL, it will move the packets into a designated rate limited sendqueue
given by the snd_tag pointer. It is up to the individual drivers how the rate
limited traffic will be rate limited.
3) Route changes are detected by the NIC drivers in the ifp->if_transmit()
routine when the ifnet pointer in the incoming snd_tag mismatches the
one of the network interface. The network adapter frees the mbuf and
returns EAGAIN which causes the ip_output() to release and clear the send
tag. Upon next ip_output() a new "snd_tag" will be tried allocated.
4) When the PCB is detached the custom sendqueue will be released by a
non-blocking ifp->if_snd_tag_free() call to the currently bound network
interface.
Reviewed by: wblock (manpages), adrian, gallatin, scottl (network)
Differential Revision: https://reviews.freebsd.org/D3687
Sponsored by: Mellanox Technologies
MFC after: 3 months
2017-01-18 13:31:17 +00:00
|
|
|
.It Cm txrtlmt
|
|
|
|
Set if the driver supports TX rate limiting.
|
2007-01-20 00:56:49 +00:00
|
|
|
.It Cm inst Ar minst , Cm instance Ar minst
|
|
|
|
Set the media instance to
|
|
|
|
.Ar minst .
|
|
|
|
This is useful for devices which have multiple physical layer interfaces
|
|
|
|
.Pq PHYs .
|
2004-02-04 02:55:46 +00:00
|
|
|
.It Cm name Ar name
|
|
|
|
Set the interface name to
|
|
|
|
.Ar name .
|
It turns out that too many drivers are not only parsing the L2/3/4
headers for TSO but also for generic checksum offloading. Ideally we
would only have one common function shared amongst all drivers, and
perhaps when updating them for IPv6 we should introduce that.
Eventually we should provide the meta information along with mbufs to
avoid (re-)parsing entirely.
To not break IPv6 (checksums and offload) and to be able to MFC the
changes without risking to hurt 3rd party drivers, duplicate the v4
framework, as other OSes have done as well.
Introduce interface capability flags for TX/RX checksum offload with
IPv6, to allow independent toggling (where possible). Add CSUM_*_IPV6
flags for UDP/TCP over IPv6, and reserve further for SCTP, and IPv6
fragmentation. Define CSUM_DELAY_DATA_IPV6 as we do for legacy IP and
add an alias for CSUM_DATA_VALID_IPV6.
This pretty much brings IPv6 handling in line with IPv4.
TSO is still handled in a different way and not via if_hwassist.
Update ifconfig to allow (un)setting of the new capability flags.
Update loopback to announce the new capabilities and if_hwassist flags.
Individual driver updates will have to follow, as will SCTP.
Reported by: gallatin, dim, ..
Reviewed by: gallatin (glanced at?)
MFC after: 3 days
X-MFC with: r235961,235959,235958
2012-05-28 09:30:13 +00:00
|
|
|
.It Cm rxcsum , txcsum , rxcsum6 , txcsum6
|
2003-02-27 22:59:13 +00:00
|
|
|
If the driver supports user-configurable checksum offloading,
|
|
|
|
enable receive (or transmit) checksum offloading on the interface.
|
It turns out that too many drivers are not only parsing the L2/3/4
headers for TSO but also for generic checksum offloading. Ideally we
would only have one common function shared amongst all drivers, and
perhaps when updating them for IPv6 we should introduce that.
Eventually we should provide the meta information along with mbufs to
avoid (re-)parsing entirely.
To not break IPv6 (checksums and offload) and to be able to MFC the
changes without risking to hurt 3rd party drivers, duplicate the v4
framework, as other OSes have done as well.
Introduce interface capability flags for TX/RX checksum offload with
IPv6, to allow independent toggling (where possible). Add CSUM_*_IPV6
flags for UDP/TCP over IPv6, and reserve further for SCTP, and IPv6
fragmentation. Define CSUM_DELAY_DATA_IPV6 as we do for legacy IP and
add an alias for CSUM_DATA_VALID_IPV6.
This pretty much brings IPv6 handling in line with IPv4.
TSO is still handled in a different way and not via if_hwassist.
Update ifconfig to allow (un)setting of the new capability flags.
Update loopback to announce the new capabilities and if_hwassist flags.
Individual driver updates will have to follow, as will SCTP.
Reported by: gallatin, dim, ..
Reviewed by: gallatin (glanced at?)
MFC after: 3 days
X-MFC with: r235961,235959,235958
2012-05-28 09:30:13 +00:00
|
|
|
The feature can be turned on selectively per protocol family.
|
|
|
|
Use
|
|
|
|
.Cm rxcsum6 , txcsum6
|
|
|
|
for
|
|
|
|
.Xr ip6 4
|
|
|
|
or
|
|
|
|
.Cm rxcsum , txcsum
|
|
|
|
otherwise.
|
2003-02-27 22:59:13 +00:00
|
|
|
Some drivers may not be able to enable these flags independently
|
|
|
|
of each other, so setting one may also set the other.
|
|
|
|
The driver will offload as much checksum work as it can reliably
|
|
|
|
support, the exact level of offloading varies between drivers.
|
It turns out that too many drivers are not only parsing the L2/3/4
headers for TSO but also for generic checksum offloading. Ideally we
would only have one common function shared amongst all drivers, and
perhaps when updating them for IPv6 we should introduce that.
Eventually we should provide the meta information along with mbufs to
avoid (re-)parsing entirely.
To not break IPv6 (checksums and offload) and to be able to MFC the
changes without risking to hurt 3rd party drivers, duplicate the v4
framework, as other OSes have done as well.
Introduce interface capability flags for TX/RX checksum offload with
IPv6, to allow independent toggling (where possible). Add CSUM_*_IPV6
flags for UDP/TCP over IPv6, and reserve further for SCTP, and IPv6
fragmentation. Define CSUM_DELAY_DATA_IPV6 as we do for legacy IP and
add an alias for CSUM_DATA_VALID_IPV6.
This pretty much brings IPv6 handling in line with IPv4.
TSO is still handled in a different way and not via if_hwassist.
Update ifconfig to allow (un)setting of the new capability flags.
Update loopback to announce the new capabilities and if_hwassist flags.
Individual driver updates will have to follow, as will SCTP.
Reported by: gallatin, dim, ..
Reviewed by: gallatin (glanced at?)
MFC after: 3 days
X-MFC with: r235961,235959,235958
2012-05-28 09:30:13 +00:00
|
|
|
.It Fl rxcsum , txcsum , rxcsum6 , txcsum6
|
2003-02-27 22:59:13 +00:00
|
|
|
If the driver supports user-configurable checksum offloading,
|
|
|
|
disable receive (or transmit) checksum offloading on the interface.
|
It turns out that too many drivers are not only parsing the L2/3/4
headers for TSO but also for generic checksum offloading. Ideally we
would only have one common function shared amongst all drivers, and
perhaps when updating them for IPv6 we should introduce that.
Eventually we should provide the meta information along with mbufs to
avoid (re-)parsing entirely.
To not break IPv6 (checksums and offload) and to be able to MFC the
changes without risking to hurt 3rd party drivers, duplicate the v4
framework, as other OSes have done as well.
Introduce interface capability flags for TX/RX checksum offload with
IPv6, to allow independent toggling (where possible). Add CSUM_*_IPV6
flags for UDP/TCP over IPv6, and reserve further for SCTP, and IPv6
fragmentation. Define CSUM_DELAY_DATA_IPV6 as we do for legacy IP and
add an alias for CSUM_DATA_VALID_IPV6.
This pretty much brings IPv6 handling in line with IPv4.
TSO is still handled in a different way and not via if_hwassist.
Update ifconfig to allow (un)setting of the new capability flags.
Update loopback to announce the new capabilities and if_hwassist flags.
Individual driver updates will have to follow, as will SCTP.
Reported by: gallatin, dim, ..
Reviewed by: gallatin (glanced at?)
MFC after: 3 days
X-MFC with: r235961,235959,235958
2012-05-28 09:30:13 +00:00
|
|
|
The feature can be turned off selectively per protocol family.
|
|
|
|
Use
|
|
|
|
.Fl rxcsum6 , txcsum6
|
|
|
|
for
|
|
|
|
.Xr ip6 4
|
|
|
|
or
|
|
|
|
.Fl rxcsum , txcsum
|
|
|
|
otherwise.
|
2003-02-27 22:59:13 +00:00
|
|
|
These settings may not always be independent of each other.
|
2006-09-06 22:07:14 +00:00
|
|
|
.It Cm tso
|
|
|
|
If the driver supports
|
|
|
|
.Xr tcp 4
|
|
|
|
segmentation offloading, enable TSO on the interface.
|
|
|
|
Some drivers may not be able to support TSO for
|
|
|
|
.Xr ip 4
|
|
|
|
and
|
|
|
|
.Xr ip6 4
|
|
|
|
packets, so they may enable only one of them.
|
|
|
|
.It Fl tso
|
|
|
|
If the driver supports
|
|
|
|
.Xr tcp 4
|
|
|
|
segmentation offloading, disable TSO on the interface.
|
|
|
|
It will always disable TSO for
|
|
|
|
.Xr ip 4
|
|
|
|
and
|
|
|
|
.Xr ip6 4 .
|
2012-05-19 23:25:57 +00:00
|
|
|
.It Cm tso6 , tso4
|
|
|
|
If the driver supports
|
|
|
|
.Xr tcp 4
|
|
|
|
segmentation offloading for
|
|
|
|
.Xr ip6 4
|
|
|
|
or
|
|
|
|
.Xr ip 4
|
|
|
|
use one of these to selectively enabled it only for one protocol family.
|
|
|
|
.It Fl tso6 , tso4
|
|
|
|
If the driver supports
|
|
|
|
.Xr tcp 4
|
|
|
|
segmentation offloading for
|
|
|
|
.Xr ip6 4
|
|
|
|
or
|
|
|
|
.Xr ip 4
|
|
|
|
use one of these to selectively disable it only for one protocol family.
|
2007-06-11 20:15:20 +00:00
|
|
|
.It Cm lro
|
|
|
|
If the driver supports
|
|
|
|
.Xr tcp 4
|
|
|
|
large receive offloading, enable LRO on the interface.
|
|
|
|
.It Fl lro
|
|
|
|
If the driver supports
|
|
|
|
.Xr tcp 4
|
|
|
|
large receive offloading, disable LRO on the interface.
|
Add kernel-side support for in-kernel TLS.
KTLS adds support for in-kernel framing and encryption of Transport
Layer Security (1.0-1.2) data on TCP sockets. KTLS only supports
offload of TLS for transmitted data. Key negotation must still be
performed in userland. Once completed, transmit session keys for a
connection are provided to the kernel via a new TCP_TXTLS_ENABLE
socket option. All subsequent data transmitted on the socket is
placed into TLS frames and encrypted using the supplied keys.
Any data written to a KTLS-enabled socket via write(2), aio_write(2),
or sendfile(2) is assumed to be application data and is encoded in TLS
frames with an application data type. Individual records can be sent
with a custom type (e.g. handshake messages) via sendmsg(2) with a new
control message (TLS_SET_RECORD_TYPE) specifying the record type.
At present, rekeying is not supported though the in-kernel framework
should support rekeying.
KTLS makes use of the recently added unmapped mbufs to store TLS
frames in the socket buffer. Each TLS frame is described by a single
ext_pgs mbuf. The ext_pgs structure contains the header of the TLS
record (and trailer for encrypted records) as well as references to
the associated TLS session.
KTLS supports two primary methods of encrypting TLS frames: software
TLS and ifnet TLS.
Software TLS marks mbufs holding socket data as not ready via
M_NOTREADY similar to sendfile(2) when TLS framing information is
added to an unmapped mbuf in ktls_frame(). ktls_enqueue() is then
called to schedule TLS frames for encryption. In the case of
sendfile_iodone() calls ktls_enqueue() instead of pru_ready() leaving
the mbufs marked M_NOTREADY until encryption is completed. For other
writes (vn_sendfile when pages are available, write(2), etc.), the
PRUS_NOTREADY is set when invoking pru_send() along with invoking
ktls_enqueue().
A pool of worker threads (the "KTLS" kernel process) encrypts TLS
frames queued via ktls_enqueue(). Each TLS frame is temporarily
mapped using the direct map and passed to a software encryption
backend to perform the actual encryption.
(Note: The use of PHYS_TO_DMAP could be replaced with sf_bufs if
someone wished to make this work on architectures without a direct
map.)
KTLS supports pluggable software encryption backends. Internally,
Netflix uses proprietary pure-software backends. This commit includes
a simple backend in a new ktls_ocf.ko module that uses the kernel's
OpenCrypto framework to provide AES-GCM encryption of TLS frames. As
a result, software TLS is now a bit of a misnomer as it can make use
of hardware crypto accelerators.
Once software encryption has finished, the TLS frame mbufs are marked
ready via pru_ready(). At this point, the encrypted data appears as
regular payload to the TCP stack stored in unmapped mbufs.
ifnet TLS permits a NIC to offload the TLS encryption and TCP
segmentation. In this mode, a new send tag type (IF_SND_TAG_TYPE_TLS)
is allocated on the interface a socket is routed over and associated
with a TLS session. TLS records for a TLS session using ifnet TLS are
not marked M_NOTREADY but are passed down the stack unencrypted. The
ip_output_send() and ip6_output_send() helper functions that apply
send tags to outbound IP packets verify that the send tag of the TLS
record matches the outbound interface. If so, the packet is tagged
with the TLS send tag and sent to the interface. The NIC device
driver must recognize packets with the TLS send tag and schedule them
for TLS encryption and TCP segmentation. If the the outbound
interface does not match the interface in the TLS send tag, the packet
is dropped. In addition, a task is scheduled to refresh the TLS send
tag for the TLS session. If a new TLS send tag cannot be allocated,
the connection is dropped. If a new TLS send tag is allocated,
however, subsequent packets will be tagged with the correct TLS send
tag. (This latter case has been tested by configuring both ports of a
Chelsio T6 in a lagg and failing over from one port to another. As
the connections migrated to the new port, new TLS send tags were
allocated for the new port and connections resumed without being
dropped.)
ifnet TLS can be enabled and disabled on supported network interfaces
via new '[-]txtls[46]' options to ifconfig(8). ifnet TLS is supported
across both vlan devices and lagg interfaces using failover, lacp with
flowid enabled, or lacp with flowid enabled.
Applications may request the current KTLS mode of a connection via a
new TCP_TXTLS_MODE socket option. They can also use this socket
option to toggle between software and ifnet TLS modes.
In addition, a testing tool is available in tools/tools/switch_tls.
This is modeled on tcpdrop and uses similar syntax. However, instead
of dropping connections, -s is used to force KTLS connections to
switch to software TLS and -i is used to switch to ifnet TLS.
Various sysctls and counters are available under the kern.ipc.tls
sysctl node. The kern.ipc.tls.enable node must be set to true to
enable KTLS (it is off by default). The use of unmapped mbufs must
also be enabled via kern.ipc.mb_use_ext_pgs to enable KTLS.
KTLS is enabled via the KERN_TLS kernel option.
This patch is the culmination of years of work by several folks
including Scott Long and Randall Stewart for the original design and
implementation; Drew Gallatin for several optimizations including the
use of ext_pgs mbufs, the M_NOTREADY mechanism for TLS records
awaiting software encryption, and pluggable software crypto backends;
and John Baldwin for modifications to support hardware TLS offload.
Reviewed by: gallatin, hselasky, rrs
Obtained from: Netflix
Sponsored by: Netflix, Chelsio Communications
Differential Revision: https://reviews.freebsd.org/D21277
2019-08-27 00:01:56 +00:00
|
|
|
.It Cm txtls
|
|
|
|
Transmit TLS offload encrypts Transport Layer Security (TLS) records and
|
|
|
|
segments the encrypted record into one or more
|
|
|
|
.Xr tcp 4
|
|
|
|
segments over either
|
|
|
|
.Xr ip 4
|
|
|
|
or
|
|
|
|
.Xr ip6 4 .
|
|
|
|
If the driver supports transmit TLS offload,
|
|
|
|
enable transmit TLS offload on the interface.
|
|
|
|
Some drivers may not be able to support transmit TLS offload for
|
|
|
|
.Xr ip 4
|
|
|
|
and
|
|
|
|
.Xr ip6 4
|
|
|
|
packets, so they may enable only one of them.
|
|
|
|
.It Fl txtls
|
|
|
|
If the driver supports transmit TLS offload,
|
|
|
|
disable transmit TLS offload on the interface.
|
|
|
|
It will always disable TLS for
|
|
|
|
.Xr ip 4
|
|
|
|
and
|
|
|
|
.Xr ip6 4 .
|
Add an external mbuf buffer type that holds multiple unmapped pages.
Unmapped mbufs allow sendfile to carry multiple pages of data in a
single mbuf, without mapping those pages. It is a requirement for
Netflix's in-kernel TLS, and provides a 5-10% CPU savings on heavy web
serving workloads when used by sendfile, due to effectively
compressing socket buffers by an order of magnitude, and hence
reducing cache misses.
For this new external mbuf buffer type (EXT_PGS), the ext_buf pointer
now points to a struct mbuf_ext_pgs structure instead of a data
buffer. This structure contains an array of physical addresses (this
reduces cache misses compared to an earlier version that stored an
array of vm_page_t pointers). It also stores additional fields needed
for in-kernel TLS such as the TLS header and trailer data that are
currently unused. To more easily detect these mbufs, the M_NOMAP flag
is set in m_flags in addition to M_EXT.
Various functions like m_copydata() have been updated to safely access
packet contents (using uiomove_fromphys()), to make things like BPF
safe.
NIC drivers advertise support for unmapped mbufs on transmit via a new
IFCAP_NOMAP capability. This capability can be toggled via the new
'nomap' and '-nomap' ifconfig(8) commands. For NIC drivers that only
transmit packet contents via DMA and use bus_dma, adding the
capability to if_capabilities and if_capenable should be all that is
required.
If a NIC does not support unmapped mbufs, they are converted to a
chain of mapped mbufs (using sf_bufs to provide the mapping) in
ip_output or ip6_output. If an unmapped mbuf requires software
checksums, it is also converted to a chain of mapped mbufs before
computing the checksum.
Submitted by: gallatin (earlier version)
Reviewed by: gallatin, hselasky, rrs
Discussed with: ae, kp (firewalls)
Relnotes: yes
Sponsored by: Netflix
Differential Revision: https://reviews.freebsd.org/D20616
2019-06-29 00:48:33 +00:00
|
|
|
.It Cm nomap
|
|
|
|
If the driver supports unmapped network buffers,
|
|
|
|
enable them on the interface.
|
|
|
|
.It Fl nomap
|
|
|
|
If the driver supports unmapped network buffers,
|
|
|
|
disable them on the interface.
|
2007-12-10 02:31:00 +00:00
|
|
|
.It Cm wol , wol_ucast , wol_mcast , wol_magic
|
|
|
|
Enable Wake On Lan (WOL) support, if available.
|
|
|
|
WOL is a facility whereby a machine in a low power state may be woken
|
|
|
|
in response to a received packet.
|
|
|
|
There are three types of packets that may wake a system:
|
|
|
|
ucast (directed solely to the machine's mac address),
|
|
|
|
mcast (directed to a broadcast or multicast address),
|
|
|
|
or
|
|
|
|
magic (unicast or multicast frames with a ``magic contents'').
|
|
|
|
Not all devices support WOL, those that do indicate the mechanisms
|
|
|
|
they support in their capabilities.
|
|
|
|
.Cm wol
|
|
|
|
is a synonym for enabling all available WOL mechanisms.
|
|
|
|
To disable WOL use
|
|
|
|
.Fl wol .
|
2011-12-17 15:44:34 +00:00
|
|
|
.It Cm vlanmtu , vlanhwtag, vlanhwfilter, vlanhwcsum, vlanhwtso
|
2005-09-22 11:49:52 +00:00
|
|
|
If the driver offers user-configurable VLAN support, enable
|
2010-02-20 23:01:09 +00:00
|
|
|
reception of extended frames, tag processing in hardware,
|
2011-12-17 15:44:34 +00:00
|
|
|
frame filtering in hardware, checksum offloading, or TSO on VLAN,
|
2005-09-22 11:49:52 +00:00
|
|
|
respectively.
|
|
|
|
Note that this must be issued on a physical interface associated with
|
|
|
|
.Xr vlan 4 ,
|
|
|
|
not on a
|
|
|
|
.Xr vlan 4
|
|
|
|
interface itself.
|
2010-02-20 23:01:09 +00:00
|
|
|
.It Fl vlanmtu , vlanhwtag, vlanhwfilter, vlanhwtso
|
2005-09-22 11:49:52 +00:00
|
|
|
If the driver offers user-configurable VLAN support, disable
|
2010-02-20 23:01:09 +00:00
|
|
|
reception of extended frames, tag processing in hardware,
|
|
|
|
frame filtering in hardware, or TSO on VLAN,
|
2005-09-22 11:49:52 +00:00
|
|
|
respectively.
|
2009-06-24 18:21:37 +00:00
|
|
|
.It Cm vnet Ar jail
|
|
|
|
Move the interface to the
|
|
|
|
.Xr jail 8 ,
|
|
|
|
specified by name or JID.
|
|
|
|
If the jail has a virtual network stack, the interface will disappear
|
|
|
|
from the current environment and become visible to the jail.
|
|
|
|
.It Fl vnet Ar jail
|
|
|
|
Reclaim the interface from the
|
|
|
|
.Xr jail 8 ,
|
|
|
|
specified by name or JID.
|
|
|
|
If the jail has a virtual network stack, the interface will disappear
|
|
|
|
from the jail, and become visible to the current network environment.
|
2004-04-11 13:36:52 +00:00
|
|
|
.It Cm polling
|
2005-10-01 19:14:34 +00:00
|
|
|
Turn on
|
2004-04-11 13:36:52 +00:00
|
|
|
.Xr polling 4
|
2005-10-01 19:14:34 +00:00
|
|
|
feature and disable interrupts on the interface, if driver supports
|
|
|
|
this mode.
|
2004-04-11 13:36:52 +00:00
|
|
|
.It Fl polling
|
2005-10-01 19:14:34 +00:00
|
|
|
Turn off
|
2004-04-11 13:36:52 +00:00
|
|
|
.Xr polling 4
|
2005-10-01 19:14:34 +00:00
|
|
|
feature and enable interrupt mode on the interface.
|
2001-07-02 20:52:34 +00:00
|
|
|
.It Cm create
|
|
|
|
Create the specified network pseudo-device.
|
|
|
|
If the interface is given without a unit number, try to create a new
|
|
|
|
device with an arbitrary unit number.
|
2001-11-24 23:38:17 +00:00
|
|
|
If creation of an arbitrary device is successful, the new device name is
|
2004-02-04 02:55:46 +00:00
|
|
|
printed to standard output unless the interface is renamed or destroyed
|
|
|
|
in the same
|
|
|
|
.Nm
|
|
|
|
invocation.
|
2001-07-02 20:52:34 +00:00
|
|
|
.It Cm destroy
|
|
|
|
Destroy the specified network pseudo-device.
|
|
|
|
.It Cm plumb
|
|
|
|
Another name for the
|
2001-08-22 18:37:47 +00:00
|
|
|
.Cm create
|
2001-07-02 20:52:34 +00:00
|
|
|
parameter.
|
2001-07-05 12:37:08 +00:00
|
|
|
Included for
|
|
|
|
.Tn Solaris
|
|
|
|
compatibility.
|
2001-07-02 20:52:34 +00:00
|
|
|
.It Cm unplumb
|
|
|
|
Another name for the
|
2001-08-22 18:37:47 +00:00
|
|
|
.Cm destroy
|
2001-07-02 20:52:34 +00:00
|
|
|
parameter.
|
2001-07-05 12:37:08 +00:00
|
|
|
Included for
|
|
|
|
.Tn Solaris
|
|
|
|
compatibility.
|
1994-05-26 06:35:07 +00:00
|
|
|
.It Cm metric Ar n
|
|
|
|
Set the routing metric of the interface to
|
|
|
|
.Ar n ,
|
|
|
|
default 0.
|
|
|
|
The routing metric is used by the routing protocol
|
|
|
|
.Pq Xr routed 8 .
|
|
|
|
Higher metrics have the effect of making a route
|
2006-10-02 08:55:54 +00:00
|
|
|
less favorable; metrics are counted as additional hops
|
1994-05-26 06:35:07 +00:00
|
|
|
to the destination network or host.
|
1994-08-08 10:45:06 +00:00
|
|
|
.It Cm mtu Ar n
|
|
|
|
Set the maximum transmission unit of the interface to
|
|
|
|
.Ar n ,
|
|
|
|
default is interface specific.
|
2001-07-05 12:37:08 +00:00
|
|
|
The MTU is used to limit the size of packets that are transmitted on an
|
1994-08-08 10:45:06 +00:00
|
|
|
interface.
|
2001-07-05 12:37:08 +00:00
|
|
|
Not all interfaces support setting the MTU, and some interfaces have
|
1994-08-08 10:45:06 +00:00
|
|
|
range restrictions.
|
1994-05-26 06:35:07 +00:00
|
|
|
.It Cm netmask Ar mask
|
2001-07-05 12:37:08 +00:00
|
|
|
.\" (Inet and ISO.)
|
|
|
|
(Inet only.)
|
1994-05-26 06:35:07 +00:00
|
|
|
Specify how much of the address to reserve for subdividing
|
|
|
|
networks into sub-networks.
|
|
|
|
The mask includes the network part of the local address
|
|
|
|
and the subnet part, which is taken from the host field of the address.
|
|
|
|
The mask can be specified as a single hexadecimal number
|
2001-07-05 12:37:08 +00:00
|
|
|
with a leading
|
|
|
|
.Ql 0x ,
|
|
|
|
with a dot-notation Internet address,
|
1994-05-26 06:35:07 +00:00
|
|
|
or with a pseudo-network name listed in the network table
|
|
|
|
.Xr networks 5 .
|
|
|
|
The mask contains 1's for the bit positions in the 32-bit address
|
|
|
|
which are to be used for the network and subnet parts,
|
|
|
|
and 0's for the host part.
|
|
|
|
The mask should contain at least the standard network portion,
|
|
|
|
and the subnet field should be contiguous with the network
|
|
|
|
portion.
|
2001-05-05 19:53:20 +00:00
|
|
|
.Pp
|
|
|
|
The netmask can also be specified in CIDR notation after the address.
|
|
|
|
See the
|
|
|
|
.Ar address
|
|
|
|
option above for more information.
|
1999-12-07 17:39:16 +00:00
|
|
|
.It Cm prefixlen Ar len
|
2001-07-05 12:37:08 +00:00
|
|
|
(Inet6 only.)
|
1999-12-07 17:39:16 +00:00
|
|
|
Specify that
|
|
|
|
.Ar len
|
|
|
|
bits are reserved for subdividing networks into sub-networks.
|
|
|
|
The
|
|
|
|
.Ar len
|
|
|
|
must be integer, and for syntactical reason it must be between 0 to 128.
|
|
|
|
It is almost always 64 under the current IPv6 assignment rule.
|
2001-08-07 11:09:17 +00:00
|
|
|
If the parameter is omitted, 64 is used.
|
2002-01-09 15:10:31 +00:00
|
|
|
.Pp
|
|
|
|
The prefix can also be specified using the slash notation after the address.
|
|
|
|
See the
|
|
|
|
.Ar address
|
|
|
|
option above for more information.
|
2000-02-26 18:55:39 +00:00
|
|
|
.It Cm remove
|
2001-02-01 16:38:02 +00:00
|
|
|
Another name for the
|
|
|
|
.Fl alias
|
|
|
|
parameter.
|
|
|
|
Introduced for compatibility
|
2001-07-05 12:37:08 +00:00
|
|
|
with
|
|
|
|
.Bsx .
|
|
|
|
.Sm off
|
|
|
|
.It Cm link Op Cm 0 No - Cm 2
|
|
|
|
.Sm on
|
1994-05-26 06:35:07 +00:00
|
|
|
Enable special processing of the link level of the interface.
|
|
|
|
These three options are interface specific in actual effect, however,
|
2000-03-01 11:27:47 +00:00
|
|
|
they are in general used to select special modes of operation.
|
|
|
|
An example
|
1997-05-03 23:03:56 +00:00
|
|
|
of this is to enable SLIP compression, or to select the connector type
|
2001-07-05 12:37:08 +00:00
|
|
|
for some Ethernet cards.
|
|
|
|
Refer to the man page for the specific driver
|
1997-05-03 23:03:56 +00:00
|
|
|
for more information.
|
2001-07-05 12:37:08 +00:00
|
|
|
.Sm off
|
|
|
|
.It Fl link Op Cm 0 No - Cm 2
|
|
|
|
.Sm on
|
1994-05-26 06:35:07 +00:00
|
|
|
Disable special processing at the link level with the specified interface.
|
2002-09-27 18:57:47 +00:00
|
|
|
.It Cm monitor
|
|
|
|
Put the interface in monitor mode.
|
2002-11-25 16:01:28 +00:00
|
|
|
No packets are transmitted, and received packets are discarded after
|
2002-09-27 18:57:47 +00:00
|
|
|
.Xr bpf 4
|
|
|
|
processing.
|
|
|
|
.It Fl monitor
|
|
|
|
Take the interface out of monitor mode.
|
2019-08-15 16:58:00 +00:00
|
|
|
.It Cm pcp Ar priority_code_point
|
|
|
|
Priority code point
|
|
|
|
.Pq Dv PCP
|
|
|
|
is an 3-bit field which refers to the IEEE 802.1p
|
|
|
|
class of service and maps to the frame priority level.
|
|
|
|
.It Fl pcp
|
|
|
|
Stop tagging packets on the interface w/ the priority code point.
|
1994-05-26 06:35:07 +00:00
|
|
|
.It Cm up
|
1998-07-06 06:53:43 +00:00
|
|
|
Mark an interface
|
2001-07-05 12:37:08 +00:00
|
|
|
.Dq up .
|
1998-07-06 06:53:43 +00:00
|
|
|
This may be used to enable an interface after an
|
2001-07-05 12:37:08 +00:00
|
|
|
.Dq Nm Cm down .
|
1994-05-26 06:35:07 +00:00
|
|
|
It happens automatically when setting the first address on an interface.
|
|
|
|
If the interface was reset when previously marked down,
|
|
|
|
the hardware will be re-initialized.
|
2004-12-08 19:18:07 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
2010-08-06 14:33:42 +00:00
|
|
|
The following parameters are for ICMPv6 Neighbor Discovery Protocol.
|
2009-09-26 18:59:00 +00:00
|
|
|
Note that the address family keyword
|
|
|
|
.Dq Li inet6
|
|
|
|
is needed for them:
|
2009-09-12 22:08:20 +00:00
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm accept_rtadv
|
|
|
|
Set a flag to enable accepting ICMPv6 Router Advertisement messages.
|
2011-09-19 16:01:53 +00:00
|
|
|
The
|
|
|
|
.Xr sysctl 8
|
|
|
|
variable
|
|
|
|
.Va net.inet6.ip6.accept_rtadv
|
|
|
|
controls whether this flag is set by default or not.
|
2009-09-12 22:08:20 +00:00
|
|
|
.It Cm -accept_rtadv
|
|
|
|
Clear a flag
|
|
|
|
.Cm accept_rtadv .
|
2011-09-19 16:01:53 +00:00
|
|
|
.It Cm no_radr
|
|
|
|
Set a flag to control whether routers from which the system accepts
|
|
|
|
Router Advertisement messages will be added to the Default Router List
|
|
|
|
or not.
|
|
|
|
When the
|
|
|
|
.Cm accept_rtadv
|
|
|
|
flag is disabled, this flag has no effect.
|
|
|
|
The
|
|
|
|
.Xr sysctl 8
|
|
|
|
variable
|
|
|
|
.Va net.inet6.ip6.no_radr
|
|
|
|
controls whether this flag is set by default or not.
|
|
|
|
.It Cm -no_radr
|
|
|
|
Clear a flag
|
|
|
|
.Cm no_radr .
|
2009-09-12 22:08:20 +00:00
|
|
|
.It Cm auto_linklocal
|
|
|
|
Set a flag to perform automatic link-local address configuration when
|
2010-07-31 21:09:49 +00:00
|
|
|
the interface becomes available.
|
2011-09-19 16:01:53 +00:00
|
|
|
The
|
|
|
|
.Xr sysctl 8
|
|
|
|
variable
|
|
|
|
.Va net.inet6.ip6.auto_linklocal
|
|
|
|
controls whether this flag is set by default or not.
|
2009-09-12 22:08:20 +00:00
|
|
|
.It Cm -auto_linklocal
|
|
|
|
Clear a flag
|
|
|
|
.Cm auto_linklocal .
|
|
|
|
.It Cm defaultif
|
|
|
|
Set the specified interface as the default route when there is no
|
|
|
|
default router.
|
|
|
|
.It Cm -defaultif
|
|
|
|
Clear a flag
|
|
|
|
.Cm defaultif .
|
|
|
|
.It Cm ifdisabled
|
|
|
|
Set a flag to disable all of IPv6 network communications on the
|
2014-06-06 00:22:19 +00:00
|
|
|
specified interface.
|
|
|
|
Note that if there are already configured IPv6
|
2009-09-26 18:59:00 +00:00
|
|
|
addresses on that interface, all of them are marked as
|
|
|
|
.Dq tentative
|
|
|
|
and DAD will be performed when this flag is cleared.
|
2009-09-12 22:08:20 +00:00
|
|
|
.It Cm -ifdisabled
|
|
|
|
Clear a flag
|
|
|
|
.Cm ifdisabled .
|
2012-03-29 05:02:12 +00:00
|
|
|
When this flag is cleared and
|
2009-09-12 22:08:20 +00:00
|
|
|
.Cm auto_linklocal
|
|
|
|
flag is enabled, automatic configuration of a link-local address is
|
|
|
|
performed.
|
|
|
|
.It Cm nud
|
|
|
|
Set a flag to enable Neighbor Unreachability Detection.
|
|
|
|
.It Cm -nud
|
|
|
|
Clear a flag
|
|
|
|
.Cm nud .
|
2013-01-09 18:18:08 +00:00
|
|
|
.It Cm no_prefer_iface
|
2014-10-01 21:37:32 +00:00
|
|
|
Set a flag to not honor rule 5 of source address selection in RFC 3484.
|
2014-07-12 10:18:33 +00:00
|
|
|
In practice this means the address on the outgoing interface will not be
|
|
|
|
preferred, effectively yielding the decision to the address selection
|
|
|
|
policy table, configurable with
|
|
|
|
.Xr ip6addrctl 8 .
|
2013-01-09 18:18:08 +00:00
|
|
|
.It Cm -no_prefer_iface
|
|
|
|
Clear a flag
|
|
|
|
.Cm no_prefer_iface .
|
2015-03-05 21:27:49 +00:00
|
|
|
.It Cm no_dad
|
|
|
|
Set a flag to disable Duplicate Address Detection.
|
|
|
|
.It Cm -no_dad
|
|
|
|
Clear a flag
|
|
|
|
.Cm no_dad .
|
2009-09-12 22:08:20 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
2014-09-09 10:52:50 +00:00
|
|
|
The following parameters are specific for IPv6 addresses.
|
|
|
|
Note that the address family keyword
|
|
|
|
.Dq Li inet6
|
|
|
|
is needed for them:
|
|
|
|
.Bl -tag -width indent
|
2018-06-27 19:28:37 +00:00
|
|
|
.It Cm autoconf
|
|
|
|
Set the IPv6 autoconfigured address bit.
|
|
|
|
.It Fl autoconf
|
|
|
|
Clear the IPv6 autoconfigured address bit.
|
2016-05-29 03:44:37 +00:00
|
|
|
.It Cm deprecated
|
|
|
|
Set the IPv6 deprecated address bit.
|
|
|
|
.It Fl deprecated
|
|
|
|
Clear the IPv6 deprecated address bit.
|
|
|
|
.It Cm pltime Ar n
|
|
|
|
Set preferred lifetime for the address.
|
2014-09-09 10:52:50 +00:00
|
|
|
.It Cm prefer_source
|
|
|
|
Set a flag to prefer address as a candidate of the source address for
|
|
|
|
outgoing packets.
|
|
|
|
.It Cm -prefer_source
|
|
|
|
Clear a flag
|
|
|
|
.Cm prefer_source .
|
2016-05-29 03:44:37 +00:00
|
|
|
.It Cm vltime Ar n
|
|
|
|
Set valid lifetime for the address.
|
2014-09-09 10:52:50 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
2008-04-20 20:35:46 +00:00
|
|
|
The following parameters are specific to cloning
|
|
|
|
IEEE 802.11 wireless interfaces with the
|
|
|
|
.Cm create
|
|
|
|
request:
|
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm wlandev Ar device
|
|
|
|
Use
|
|
|
|
.Ar device
|
|
|
|
as the parent for the cloned device.
|
|
|
|
.It Cm wlanmode Ar mode
|
|
|
|
Specify the operating mode for this cloned device.
|
|
|
|
.Ar mode
|
|
|
|
is one of
|
|
|
|
.Cm sta ,
|
2012-03-29 05:02:12 +00:00
|
|
|
.Cm ahdemo
|
2008-04-20 20:35:46 +00:00
|
|
|
(or
|
2017-03-21 13:01:08 +00:00
|
|
|
.Cm adhoc-demo ) ,
|
2008-04-20 20:35:46 +00:00
|
|
|
.Cm ibss ,
|
|
|
|
(or
|
2017-03-21 13:01:08 +00:00
|
|
|
.Cm adhoc ) ,
|
2008-04-20 20:35:46 +00:00
|
|
|
.Cm ap ,
|
|
|
|
(or
|
2017-03-21 13:01:08 +00:00
|
|
|
.Cm hostap ) ,
|
2008-04-20 20:35:46 +00:00
|
|
|
.Cm wds ,
|
2009-01-08 17:12:47 +00:00
|
|
|
.Cm tdma ,
|
Implementation of the upcoming Wireless Mesh standard, 802.11s, on the
net80211 wireless stack. This work is based on the March 2009 D3.0 draft
standard. This standard is expected to become final next year.
This includes two main net80211 modules, ieee80211_mesh.c
which deals with peer link management, link metric calculation,
routing table control and mesh configuration and ieee80211_hwmp.c
which deals with the actually routing process on the mesh network.
HWMP is the mandatory routing protocol on by the mesh standard, but
others, such as RA-OLSR, can be implemented.
Authentication and encryption are not implemented.
There are several scripts under tools/tools/net80211/scripts that can be
used to test different mesh network topologies and they also teach you
how to setup a mesh vap (for the impatient: ifconfig wlan0 create
wlandev ... wlanmode mesh).
A new build option is available: IEEE80211_SUPPORT_MESH and it's enabled
by default on GENERIC kernels for i386, amd64, sparc64 and pc98.
Drivers that support mesh networks right now are: ath, ral and mwl.
More information at: http://wiki.freebsd.org/WifiMesh
Please note that this work is experimental. Also, please note that
bridging a mesh vap with another network interface is not yet supported.
Many thanks to the FreeBSD Foundation for sponsoring this project and to
Sam Leffler for his support.
Also, I would like to thank Gateworks Corporation for sending me a
Cambria board which was used during the development of this project.
Reviewed by: sam
Approved by: re (kensmith)
Obtained from: projects/mesh11s
2009-07-11 15:02:45 +00:00
|
|
|
.Cm mesh ,
|
2008-04-20 20:35:46 +00:00
|
|
|
and
|
|
|
|
.Cm monitor .
|
|
|
|
The operating mode of a cloned interface cannot be changed.
|
2009-01-08 17:12:47 +00:00
|
|
|
The
|
|
|
|
.Cm tdma
|
|
|
|
mode is actually implemented as an
|
|
|
|
.Cm adhoc-demo
|
|
|
|
interface with special properties.
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm wlanbssid Ar bssid
|
|
|
|
The 802.11 mac address to use for the bssid.
|
|
|
|
This must be specified at create time for a legacy
|
|
|
|
.Cm wds
|
|
|
|
device.
|
|
|
|
.It Cm wlanaddr Ar address
|
|
|
|
The local mac address.
|
|
|
|
If this is not specified then a mac address will automatically be assigned
|
|
|
|
to the cloned device.
|
|
|
|
Typically this address is the same as the address of the parent device
|
|
|
|
but if the
|
|
|
|
.Cm bssid
|
|
|
|
parameter is specified then the driver will craft a unique address for
|
|
|
|
the device (if supported).
|
|
|
|
.It Cm wdslegacy
|
|
|
|
Mark a
|
|
|
|
.Cm wds
|
|
|
|
device as operating in ``legacy mode''.
|
2012-03-29 05:02:12 +00:00
|
|
|
Legacy
|
2008-04-20 20:35:46 +00:00
|
|
|
.Cm wds
|
|
|
|
devices have a fixed peer relationship and do not, for example, roam
|
|
|
|
if their peer stops communicating.
|
|
|
|
For completeness a Dynamic WDS (DWDS) interface may marked as
|
|
|
|
.Fl wdslegacy .
|
|
|
|
.It Cm bssid
|
|
|
|
Request a unique local mac address for the cloned device.
|
|
|
|
This is only possible if the device supports multiple mac addresses.
|
|
|
|
To force use of the parent's mac address use
|
|
|
|
.Fl bssid .
|
|
|
|
.It Cm beacons
|
|
|
|
Mark the cloned interface as depending on hardware support to
|
|
|
|
track received beacons.
|
|
|
|
To have beacons tracked in software use
|
|
|
|
.Fl beacons .
|
2012-03-29 05:02:12 +00:00
|
|
|
For
|
2008-04-20 20:35:46 +00:00
|
|
|
.Cm hostap
|
2012-03-29 05:02:12 +00:00
|
|
|
mode
|
2008-04-20 20:35:46 +00:00
|
|
|
.Fl beacons
|
|
|
|
can also be used to indicate no beacons should
|
|
|
|
be transmitted; this can be useful when creating a WDS configuration but
|
|
|
|
.Cm wds
|
|
|
|
interfaces can only be created as companions to an access point.
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
The following parameters are specific to IEEE 802.11 wireless interfaces
|
|
|
|
cloned with a
|
|
|
|
.Cm create
|
|
|
|
operation:
|
2004-12-08 19:18:07 +00:00
|
|
|
.Bl -tag -width indent
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm ampdu
|
|
|
|
Enable sending and receiving AMPDU frames when using 802.11n (default).
|
|
|
|
The 802.11n specification states a compliant station must be capable
|
2010-07-31 21:09:49 +00:00
|
|
|
of receiving AMPDU frames but transmission is optional.
|
2008-04-20 20:35:46 +00:00
|
|
|
Use
|
|
|
|
.Fl ampdu
|
|
|
|
to disable all use of AMPDU with 802.11n.
|
|
|
|
For testing and/or to work around interoperability problems one can use
|
|
|
|
.Cm ampdutx
|
|
|
|
and
|
|
|
|
.Cm ampdurx
|
|
|
|
to control use of AMPDU in one direction.
|
|
|
|
.It Cm ampdudensity Ar density
|
|
|
|
Set the AMPDU density parameter used when operating with 802.11n.
|
|
|
|
This parameter controls the inter-packet gap for AMPDU frames.
|
|
|
|
The sending device normally controls this setting but a receiving station
|
|
|
|
may request wider gaps.
|
|
|
|
Legal values for
|
|
|
|
.Ar density
|
|
|
|
are 0, .25, .5, 1, 2, 4, 8, and 16 (microseconds).
|
|
|
|
A value of
|
|
|
|
.Cm -
|
|
|
|
is treated the same as 0.
|
|
|
|
.It Cm ampdulimit Ar limit
|
|
|
|
Set the limit on packet size for receiving AMPDU frames when operating
|
|
|
|
with 802.11n.
|
|
|
|
Legal values for
|
|
|
|
.Ar limit
|
|
|
|
are 8192, 16384, 32768, and 65536 but one can also specify
|
|
|
|
just the unique prefix: 8, 16, 32, 64.
|
|
|
|
Note the sender may limit the size of AMPDU frames to be less
|
|
|
|
than the maximum specified by the receiving station.
|
|
|
|
.It Cm amsdu
|
|
|
|
Enable sending and receiving AMSDU frames when using 802.11n.
|
|
|
|
By default AMSDU is received but not transmitted.
|
|
|
|
Use
|
|
|
|
.Fl amsdu
|
|
|
|
to disable all use of AMSDU with 802.11n.
|
|
|
|
For testing and/or to work around interoperability problems one can use
|
|
|
|
.Cm amsdutx
|
|
|
|
and
|
|
|
|
.Cm amsdurx
|
|
|
|
to control use of AMSDU in one direction.
|
|
|
|
.It Cm amsdulimit Ar limit
|
|
|
|
Set the limit on packet size for sending and receiving AMSDU frames
|
|
|
|
when operating with 802.11n.
|
|
|
|
Legal values for
|
|
|
|
.Ar limit
|
|
|
|
are 7935 and 3839 (bytes).
|
|
|
|
Note the sender may limit the size of AMSDU frames to be less
|
|
|
|
than the maximum specified by the receiving station.
|
|
|
|
Note also that devices are not required to support the 7935 limit,
|
|
|
|
only 3839 is required by the specification and the larger value
|
|
|
|
may require more memory to be dedicated to support functionality
|
|
|
|
that is rarely used.
|
2004-12-08 19:18:07 +00:00
|
|
|
.It Cm apbridge
|
2005-01-10 16:17:34 +00:00
|
|
|
When operating as an access point, pass packets between
|
2004-12-08 19:18:07 +00:00
|
|
|
wireless clients directly (default).
|
|
|
|
To instead let them pass up through the
|
2005-01-10 16:17:34 +00:00
|
|
|
system and be forwarded using some other mechanism, use
|
|
|
|
.Fl apbridge .
|
2004-12-08 19:18:07 +00:00
|
|
|
Disabling the internal bridging
|
|
|
|
is useful when traffic is to be processed with
|
|
|
|
packet filtering.
|
2001-05-26 09:27:08 +00:00
|
|
|
.It Cm authmode Ar mode
|
2004-12-08 19:18:07 +00:00
|
|
|
Set the desired authentication mode in infrastructure mode.
|
2008-04-20 20:35:46 +00:00
|
|
|
Not all adapters support all modes.
|
2001-07-05 12:37:08 +00:00
|
|
|
The set of
|
2001-05-26 09:27:08 +00:00
|
|
|
valid modes is
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm none , open , shared
|
2005-01-10 16:17:34 +00:00
|
|
|
(shared key),
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm 8021x
|
2005-01-10 16:17:34 +00:00
|
|
|
(IEEE 802.1x),
|
2005-08-02 19:13:13 +00:00
|
|
|
and
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm wpa
|
2005-01-10 16:17:34 +00:00
|
|
|
(IEEE WPA/WPA2/802.11i).
|
2004-12-08 19:18:07 +00:00
|
|
|
The
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm 8021x
|
2001-05-26 09:27:08 +00:00
|
|
|
and
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm wpa
|
2005-08-02 19:13:13 +00:00
|
|
|
modes are only useful when using an authentication service
|
2004-12-08 19:18:07 +00:00
|
|
|
(a supplicant for client operation or an authenticator when
|
|
|
|
operating as an access point).
|
2001-05-26 09:27:08 +00:00
|
|
|
Modes are case insensitive.
|
2007-07-09 15:39:58 +00:00
|
|
|
.It Cm bgscan
|
|
|
|
Enable background scanning when operating as a station.
|
|
|
|
Background scanning is a technique whereby a station associated to
|
|
|
|
an access point will temporarily leave the channel to scan for
|
|
|
|
neighboring stations.
|
|
|
|
This allows a station to maintain a cache of nearby access points
|
2007-11-02 05:23:22 +00:00
|
|
|
so that roaming between access points can be done without
|
2007-07-09 15:39:58 +00:00
|
|
|
a lengthy scan operation.
|
|
|
|
Background scanning is done only when a station is not busy and
|
|
|
|
any outbound traffic will cancel a scan operation.
|
|
|
|
Background scanning should never cause packets to be lost though
|
|
|
|
there may be some small latency if outbound traffic interrupts a
|
|
|
|
scan operation.
|
|
|
|
By default background scanning is enabled if the device is capable.
|
|
|
|
To disable background scanning, use
|
|
|
|
.Fl bgscan .
|
|
|
|
Background scanning is controlled by the
|
|
|
|
.Cm bgscanidle
|
|
|
|
and
|
|
|
|
.Cm bgscanintvl
|
|
|
|
parameters.
|
|
|
|
Background scanning must be enabled for roaming; this is an artifact
|
|
|
|
of the current implementation and may not be required in the future.
|
|
|
|
.It Cm bgscanidle Ar idletime
|
|
|
|
Set the minimum time a station must be idle (not transmitting or
|
|
|
|
receiving frames) before a background scan is initiated.
|
|
|
|
The
|
|
|
|
.Ar idletime
|
|
|
|
parameter is specified in milliseconds.
|
|
|
|
By default a station must be idle at least 250 milliseconds before
|
|
|
|
a background scan is initiated.
|
|
|
|
The idle time may not be set to less than 100 milliseconds.
|
|
|
|
.It Cm bgscanintvl Ar interval
|
|
|
|
Set the interval at which background scanning is attempted.
|
|
|
|
The
|
|
|
|
.Ar interval
|
|
|
|
parameter is specified in seconds.
|
2007-11-02 05:23:22 +00:00
|
|
|
By default a background scan is considered every 300 seconds (5 minutes).
|
2012-03-29 05:02:12 +00:00
|
|
|
The
|
2007-07-09 15:39:58 +00:00
|
|
|
.Ar interval
|
|
|
|
may not be set to less than 15 seconds.
|
2005-08-02 19:13:13 +00:00
|
|
|
.It Cm bintval Ar interval
|
|
|
|
Set the interval at which beacon frames are sent when operating in
|
|
|
|
ad-hoc or ap mode.
|
|
|
|
The
|
|
|
|
.Ar interval
|
Update for revised 802.11 support:
o revised channel handling support; ifconfig now queries the kernel to
find the list of available channels and handles channel promotion;
channel attributes can be specified as part of the channel; e.g. 36:a
for channel 36 in 11a (as opposed to turbo A or HT A)
o use channel list to map between freq and IEEE channel #; this eliminates
all knowledge of how the mapping is done and fixes handling of cases
where channels overlap in the IEEE channel # space but are distinct in
the frequency+attributes space (e.g. PSB)
o add new knobs: bgscan, ff (Atheors fast frames), dturbo (Atheros
Dynamic Turbo mode), bgscanidle, bgscanintvl, scanvalid, roam:rssi11a,
roam:rssi11b, roam:rssi11g, roam:rate11a, roam:rate11b, roam:rate11g
(roaming parameters), burst, doth (forthcoming 11h support)
o print contents of WME, ATH, WPA, RSN, information elements with -v option
o print signal strength in dBm
o print noise floor in dBm
o add list txpow to print tx power caps/channel
o change default channel display in status to be more informative
2007-06-11 03:56:33 +00:00
|
|
|
parameter is specified in TU's (1024 usecs).
|
2005-08-02 19:13:13 +00:00
|
|
|
By default beacon frames are transmitted every 100 TU's.
|
2006-07-26 03:08:45 +00:00
|
|
|
.It Cm bmissthreshold Ar count
|
|
|
|
Set the number of consecutive missed beacons at which the station
|
2006-09-18 11:55:10 +00:00
|
|
|
will attempt to roam (i.e., search for a new access point).
|
2006-07-26 03:08:45 +00:00
|
|
|
The
|
|
|
|
.Ar count
|
2006-09-18 11:55:10 +00:00
|
|
|
parameter must be in the range 1 to 255; though the
|
|
|
|
upper bound may be reduced according to device capabilities.
|
2006-07-26 03:08:45 +00:00
|
|
|
The default threshold is 7 consecutive missed beacons; but
|
|
|
|
this may be overridden by the device driver.
|
|
|
|
Another name for the
|
|
|
|
.Cm bmissthreshold
|
|
|
|
parameter is
|
|
|
|
.Cm bmiss .
|
2004-12-08 19:18:07 +00:00
|
|
|
.It Cm bssid Ar address
|
|
|
|
Specify the MAC address of the access point to use when operating
|
|
|
|
as a station in a BSS network.
|
|
|
|
This overrides any automatic selection done by the system.
|
2005-01-10 16:17:34 +00:00
|
|
|
To disable a previously selected access point, supply
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm any , none ,
|
2004-12-08 19:18:07 +00:00
|
|
|
or
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm -
|
2004-12-08 19:18:07 +00:00
|
|
|
for the address.
|
2006-10-02 08:55:54 +00:00
|
|
|
This option is useful when more than one access point uses the same SSID.
|
2004-12-08 19:18:07 +00:00
|
|
|
Another name for the
|
|
|
|
.Cm bssid
|
|
|
|
parameter is
|
|
|
|
.Cm ap .
|
2005-12-14 19:44:39 +00:00
|
|
|
.It Cm burst
|
|
|
|
Enable packet bursting.
|
|
|
|
Packet bursting is a transmission technique whereby the wireless
|
|
|
|
medium is acquired once to send multiple frames and the interframe
|
|
|
|
spacing is reduced.
|
|
|
|
This technique can significantly increase throughput by reducing
|
|
|
|
transmission overhead.
|
|
|
|
Packet bursting is supported by the 802.11e QoS specification
|
|
|
|
and some devices that do not support QoS may still be capable.
|
|
|
|
By default packet bursting is enabled if a device is capable
|
|
|
|
of doing it.
|
|
|
|
To disable packet bursting, use
|
|
|
|
.Fl burst .
|
2004-12-08 19:18:07 +00:00
|
|
|
.It Cm chanlist Ar channels
|
|
|
|
Set the desired channels to use when scanning for access
|
|
|
|
points, neighbors in an IBSS network, or looking for unoccupied
|
|
|
|
channels when operating as an access point.
|
|
|
|
The set of channels is specified as a comma-separated list with
|
2005-01-10 16:17:34 +00:00
|
|
|
each element in the list representing either a single channel number or a range
|
2004-12-08 19:18:07 +00:00
|
|
|
of the form
|
|
|
|
.Dq Li a-b .
|
|
|
|
Channel numbers must be in the range 1 to 255 and be permissible
|
|
|
|
according to the operating characteristics of the device.
|
|
|
|
.It Cm channel Ar number
|
|
|
|
Set a single desired channel.
|
|
|
|
Channels range from 1 to 255, but the exact selection available
|
|
|
|
depends on the region your adaptor was manufactured for.
|
|
|
|
Setting
|
|
|
|
the channel to
|
2008-07-30 16:22:52 +00:00
|
|
|
.Li any ,
|
2004-12-08 19:18:07 +00:00
|
|
|
or
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm -
|
2008-07-30 16:22:52 +00:00
|
|
|
will clear any desired channel and, if the device is marked up,
|
|
|
|
force a scan for a channel to operate on.
|
2004-12-08 19:18:07 +00:00
|
|
|
Alternatively the frequency, in megahertz, may be specified
|
|
|
|
instead of the channel number.
|
Update for revised 802.11 support:
o revised channel handling support; ifconfig now queries the kernel to
find the list of available channels and handles channel promotion;
channel attributes can be specified as part of the channel; e.g. 36:a
for channel 36 in 11a (as opposed to turbo A or HT A)
o use channel list to map between freq and IEEE channel #; this eliminates
all knowledge of how the mapping is done and fixes handling of cases
where channels overlap in the IEEE channel # space but are distinct in
the frequency+attributes space (e.g. PSB)
o add new knobs: bgscan, ff (Atheors fast frames), dturbo (Atheros
Dynamic Turbo mode), bgscanidle, bgscanintvl, scanvalid, roam:rssi11a,
roam:rssi11b, roam:rssi11g, roam:rate11a, roam:rate11b, roam:rate11g
(roaming parameters), burst, doth (forthcoming 11h support)
o print contents of WME, ATH, WPA, RSN, information elements with -v option
o print signal strength in dBm
o print noise floor in dBm
o add list txpow to print tx power caps/channel
o change default channel display in status to be more informative
2007-06-11 03:56:33 +00:00
|
|
|
.Pp
|
|
|
|
When there are several ways to use a channel the channel
|
|
|
|
number/frequency may be appended with attributes to clarify.
|
|
|
|
For example, if a device is capable of operating on channel 6
|
|
|
|
with 802.11n and 802.11g then one can specify that g-only use
|
|
|
|
should be used by specifying ``6:g''.
|
|
|
|
Similarly the channel width can be specified by appending it
|
2012-11-07 19:26:32 +00:00
|
|
|
with ``/''; e.g., ``6/40'' specifies a 40MHz wide channel,
|
Update for revised 802.11 support:
o revised channel handling support; ifconfig now queries the kernel to
find the list of available channels and handles channel promotion;
channel attributes can be specified as part of the channel; e.g. 36:a
for channel 36 in 11a (as opposed to turbo A or HT A)
o use channel list to map between freq and IEEE channel #; this eliminates
all knowledge of how the mapping is done and fixes handling of cases
where channels overlap in the IEEE channel # space but are distinct in
the frequency+attributes space (e.g. PSB)
o add new knobs: bgscan, ff (Atheors fast frames), dturbo (Atheros
Dynamic Turbo mode), bgscanidle, bgscanintvl, scanvalid, roam:rssi11a,
roam:rssi11b, roam:rssi11g, roam:rate11a, roam:rate11b, roam:rate11g
(roaming parameters), burst, doth (forthcoming 11h support)
o print contents of WME, ATH, WPA, RSN, information elements with -v option
o print signal strength in dBm
o print noise floor in dBm
o add list txpow to print tx power caps/channel
o change default channel display in status to be more informative
2007-06-11 03:56:33 +00:00
|
|
|
These attributes can be combined as in: ``6:ht/40''.
|
2010-08-16 15:18:30 +00:00
|
|
|
The full set of flags specified following a ``:'' are:
|
Update for revised 802.11 support:
o revised channel handling support; ifconfig now queries the kernel to
find the list of available channels and handles channel promotion;
channel attributes can be specified as part of the channel; e.g. 36:a
for channel 36 in 11a (as opposed to turbo A or HT A)
o use channel list to map between freq and IEEE channel #; this eliminates
all knowledge of how the mapping is done and fixes handling of cases
where channels overlap in the IEEE channel # space but are distinct in
the frequency+attributes space (e.g. PSB)
o add new knobs: bgscan, ff (Atheors fast frames), dturbo (Atheros
Dynamic Turbo mode), bgscanidle, bgscanintvl, scanvalid, roam:rssi11a,
roam:rssi11b, roam:rssi11g, roam:rate11a, roam:rate11b, roam:rate11g
(roaming parameters), burst, doth (forthcoming 11h support)
o print contents of WME, ATH, WPA, RSN, information elements with -v option
o print signal strength in dBm
o print noise floor in dBm
o add list txpow to print tx power caps/channel
o change default channel display in status to be more informative
2007-06-11 03:56:33 +00:00
|
|
|
.Cm a
|
|
|
|
(802.11a),
|
|
|
|
.Cm b
|
|
|
|
(802.11b),
|
|
|
|
.Cm d
|
|
|
|
(Atheros Dynamic Turbo mode),
|
|
|
|
.Cm g
|
|
|
|
(802.11g),
|
|
|
|
.Cm h
|
|
|
|
or
|
|
|
|
.Cm n
|
|
|
|
(802.11n aka HT),
|
|
|
|
.Cm s
|
|
|
|
(Atheros Static Turbo mode),
|
|
|
|
and
|
|
|
|
.Cm t
|
2007-07-09 15:39:58 +00:00
|
|
|
(Atheros Dynamic Turbo mode, or appended to ``st'' and ``dt'').
|
Update for revised 802.11 support:
o revised channel handling support; ifconfig now queries the kernel to
find the list of available channels and handles channel promotion;
channel attributes can be specified as part of the channel; e.g. 36:a
for channel 36 in 11a (as opposed to turbo A or HT A)
o use channel list to map between freq and IEEE channel #; this eliminates
all knowledge of how the mapping is done and fixes handling of cases
where channels overlap in the IEEE channel # space but are distinct in
the frequency+attributes space (e.g. PSB)
o add new knobs: bgscan, ff (Atheors fast frames), dturbo (Atheros
Dynamic Turbo mode), bgscanidle, bgscanintvl, scanvalid, roam:rssi11a,
roam:rssi11b, roam:rssi11g, roam:rate11a, roam:rate11b, roam:rate11g
(roaming parameters), burst, doth (forthcoming 11h support)
o print contents of WME, ATH, WPA, RSN, information elements with -v option
o print signal strength in dBm
o print noise floor in dBm
o add list txpow to print tx power caps/channel
o change default channel display in status to be more informative
2007-06-11 03:56:33 +00:00
|
|
|
The full set of channel widths following a '/' are:
|
2012-03-29 05:02:12 +00:00
|
|
|
.Cm 5
|
Update for revised 802.11 support:
o revised channel handling support; ifconfig now queries the kernel to
find the list of available channels and handles channel promotion;
channel attributes can be specified as part of the channel; e.g. 36:a
for channel 36 in 11a (as opposed to turbo A or HT A)
o use channel list to map between freq and IEEE channel #; this eliminates
all knowledge of how the mapping is done and fixes handling of cases
where channels overlap in the IEEE channel # space but are distinct in
the frequency+attributes space (e.g. PSB)
o add new knobs: bgscan, ff (Atheors fast frames), dturbo (Atheros
Dynamic Turbo mode), bgscanidle, bgscanintvl, scanvalid, roam:rssi11a,
roam:rssi11b, roam:rssi11g, roam:rate11a, roam:rate11b, roam:rate11g
(roaming parameters), burst, doth (forthcoming 11h support)
o print contents of WME, ATH, WPA, RSN, information elements with -v option
o print signal strength in dBm
o print noise floor in dBm
o add list txpow to print tx power caps/channel
o change default channel display in status to be more informative
2007-06-11 03:56:33 +00:00
|
|
|
(5MHz aka quarter-rate channel),
|
2012-03-29 05:02:12 +00:00
|
|
|
.Cm 10
|
Update for revised 802.11 support:
o revised channel handling support; ifconfig now queries the kernel to
find the list of available channels and handles channel promotion;
channel attributes can be specified as part of the channel; e.g. 36:a
for channel 36 in 11a (as opposed to turbo A or HT A)
o use channel list to map between freq and IEEE channel #; this eliminates
all knowledge of how the mapping is done and fixes handling of cases
where channels overlap in the IEEE channel # space but are distinct in
the frequency+attributes space (e.g. PSB)
o add new knobs: bgscan, ff (Atheors fast frames), dturbo (Atheros
Dynamic Turbo mode), bgscanidle, bgscanintvl, scanvalid, roam:rssi11a,
roam:rssi11b, roam:rssi11g, roam:rate11a, roam:rate11b, roam:rate11g
(roaming parameters), burst, doth (forthcoming 11h support)
o print contents of WME, ATH, WPA, RSN, information elements with -v option
o print signal strength in dBm
o print noise floor in dBm
o add list txpow to print tx power caps/channel
o change default channel display in status to be more informative
2007-06-11 03:56:33 +00:00
|
|
|
(10MHz aka half-rate channel),
|
2012-03-29 05:02:12 +00:00
|
|
|
.Cm 20
|
Update for revised 802.11 support:
o revised channel handling support; ifconfig now queries the kernel to
find the list of available channels and handles channel promotion;
channel attributes can be specified as part of the channel; e.g. 36:a
for channel 36 in 11a (as opposed to turbo A or HT A)
o use channel list to map between freq and IEEE channel #; this eliminates
all knowledge of how the mapping is done and fixes handling of cases
where channels overlap in the IEEE channel # space but are distinct in
the frequency+attributes space (e.g. PSB)
o add new knobs: bgscan, ff (Atheors fast frames), dturbo (Atheros
Dynamic Turbo mode), bgscanidle, bgscanintvl, scanvalid, roam:rssi11a,
roam:rssi11b, roam:rssi11g, roam:rate11a, roam:rate11b, roam:rate11g
(roaming parameters), burst, doth (forthcoming 11h support)
o print contents of WME, ATH, WPA, RSN, information elements with -v option
o print signal strength in dBm
o print noise floor in dBm
o add list txpow to print tx power caps/channel
o change default channel display in status to be more informative
2007-06-11 03:56:33 +00:00
|
|
|
(20MHz mostly for use in specifying ht20),
|
|
|
|
and
|
2012-03-29 05:02:12 +00:00
|
|
|
.Cm 40
|
2010-08-16 15:18:30 +00:00
|
|
|
(40MHz mostly for use in specifying ht40).
|
Update for revised 802.11 support:
o revised channel handling support; ifconfig now queries the kernel to
find the list of available channels and handles channel promotion;
channel attributes can be specified as part of the channel; e.g. 36:a
for channel 36 in 11a (as opposed to turbo A or HT A)
o use channel list to map between freq and IEEE channel #; this eliminates
all knowledge of how the mapping is done and fixes handling of cases
where channels overlap in the IEEE channel # space but are distinct in
the frequency+attributes space (e.g. PSB)
o add new knobs: bgscan, ff (Atheors fast frames), dturbo (Atheros
Dynamic Turbo mode), bgscanidle, bgscanintvl, scanvalid, roam:rssi11a,
roam:rssi11b, roam:rssi11g, roam:rate11a, roam:rate11b, roam:rate11g
(roaming parameters), burst, doth (forthcoming 11h support)
o print contents of WME, ATH, WPA, RSN, information elements with -v option
o print signal strength in dBm
o print noise floor in dBm
o add list txpow to print tx power caps/channel
o change default channel display in status to be more informative
2007-06-11 03:56:33 +00:00
|
|
|
In addition,
|
|
|
|
a 40MHz HT channel specification may include the location
|
|
|
|
of the extension channel by appending ``+'' or ``-'' for above and below,
|
2012-11-07 19:26:32 +00:00
|
|
|
respectively; e.g., ``2437:ht/40+'' specifies 40MHz wide HT operation
|
Update for revised 802.11 support:
o revised channel handling support; ifconfig now queries the kernel to
find the list of available channels and handles channel promotion;
channel attributes can be specified as part of the channel; e.g. 36:a
for channel 36 in 11a (as opposed to turbo A or HT A)
o use channel list to map between freq and IEEE channel #; this eliminates
all knowledge of how the mapping is done and fixes handling of cases
where channels overlap in the IEEE channel # space but are distinct in
the frequency+attributes space (e.g. PSB)
o add new knobs: bgscan, ff (Atheors fast frames), dturbo (Atheros
Dynamic Turbo mode), bgscanidle, bgscanintvl, scanvalid, roam:rssi11a,
roam:rssi11b, roam:rssi11g, roam:rate11a, roam:rate11b, roam:rate11g
(roaming parameters), burst, doth (forthcoming 11h support)
o print contents of WME, ATH, WPA, RSN, information elements with -v option
o print signal strength in dBm
o print noise floor in dBm
o add list txpow to print tx power caps/channel
o change default channel display in status to be more informative
2007-06-11 03:56:33 +00:00
|
|
|
with the center channel at frequency 2437 and the extension channel above.
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm country Ar name
|
|
|
|
Set the country code to use in calculating the regulatory constraints
|
|
|
|
for operation.
|
|
|
|
In particular the set of available channels, how the wireless device
|
|
|
|
will operation on the channels, and the maximum transmit power that
|
|
|
|
can be used on a channel are defined by this setting.
|
|
|
|
Country/Region codes are specified as a 2-character abbreviation
|
|
|
|
defined by ISO 3166 or using a longer, but possibly ambiguous, spelling;
|
2012-11-07 19:26:32 +00:00
|
|
|
e.g., "ES" and "Spain".
|
2013-05-13 18:13:50 +00:00
|
|
|
The set of country codes are taken from
|
|
|
|
.Pa /etc/regdomain.xml
|
|
|
|
and can also
|
2008-04-20 20:35:46 +00:00
|
|
|
be viewed with the ``list countries'' request.
|
|
|
|
Note that not all devices support changing the country code from a default
|
|
|
|
setting; typically stored in EEPROM.
|
|
|
|
See also
|
|
|
|
.Cm regdomain ,
|
|
|
|
.Cm indoor ,
|
|
|
|
.Cm outdoor ,
|
|
|
|
and
|
|
|
|
.Cm anywhere .
|
|
|
|
.It Cm dfs
|
|
|
|
Enable Dynamic Frequency Selection (DFS) as specified in 802.11h.
|
|
|
|
DFS embodies several facilities including detection of overlapping
|
|
|
|
radar signals, dynamic transmit power control, and channel selection
|
|
|
|
according to a least-congested criteria.
|
2012-02-28 13:19:34 +00:00
|
|
|
DFS support is mandatory for some 5GHz frequencies in certain
|
2012-11-07 19:26:32 +00:00
|
|
|
locales (e.g., ETSI).
|
2008-04-20 20:35:46 +00:00
|
|
|
By default DFS is enabled according to the regulatory definitions
|
2013-05-13 18:13:50 +00:00
|
|
|
specified in
|
|
|
|
.Pa /etc/regdomain.xml
|
|
|
|
and the current country code, regdomain,
|
2008-04-20 20:35:46 +00:00
|
|
|
and channel.
|
|
|
|
Note the underlying device (and driver) must support radar detection
|
|
|
|
for full DFS support to work.
|
|
|
|
To be fully compliant with the local regulatory agency frequencies that
|
|
|
|
require DFS should not be used unless it is fully supported.
|
|
|
|
Use
|
|
|
|
.Fl dfs
|
|
|
|
to disable this functionality for testing.
|
|
|
|
.It Cm dotd
|
|
|
|
Enable support for the 802.11d specification (default).
|
|
|
|
When this support is enabled in station mode, beacon frames that advertise
|
|
|
|
a country code different than the currently configured country code will
|
|
|
|
cause an event to be dispatched to user applications.
|
|
|
|
This event can be used by the station to adopt that country code and
|
|
|
|
operate according to the associated regulatory constraints.
|
|
|
|
When operating as an access point with 802.11d enabled the beacon and
|
|
|
|
probe response frames transmitted will advertise the current regulatory
|
|
|
|
domain settings.
|
|
|
|
To disable 802.11d use
|
|
|
|
.Fl dotd .
|
2007-07-09 15:39:58 +00:00
|
|
|
.It Cm doth
|
2008-04-20 20:35:46 +00:00
|
|
|
Enable 802.11h support including spectrum management.
|
|
|
|
When 802.11h is enabled beacon and probe response frames will have
|
|
|
|
the SpectrumMgt bit set in the capabilities field and
|
|
|
|
country and power constraint information elements will be present.
|
|
|
|
802.11h support also includes handling Channel Switch Announcements (CSA)
|
|
|
|
which are a mechanism to coordinate channel changes by an access point.
|
2007-07-09 15:39:58 +00:00
|
|
|
By default 802.11h is enabled if the device is capable.
|
|
|
|
To disable 802.11h use
|
|
|
|
.Fl doth .
|
2005-12-26 18:15:09 +00:00
|
|
|
.It Cm deftxkey Ar index
|
|
|
|
Set the default key to use for transmission.
|
|
|
|
Typically this is only set when using WEP encryption.
|
2008-02-29 20:42:17 +00:00
|
|
|
Note that you must set a default transmit key
|
|
|
|
for the system to know which key to use in encrypting outbound traffic.
|
2005-12-26 18:15:09 +00:00
|
|
|
The
|
|
|
|
.Cm weptxkey
|
|
|
|
is an alias for this request; it is provided for backwards compatibility.
|
2005-08-02 19:13:13 +00:00
|
|
|
.It Cm dtimperiod Ar period
|
|
|
|
Set the
|
|
|
|
DTIM
|
|
|
|
period for transmitting buffered multicast data frames when
|
|
|
|
operating in ap mode.
|
|
|
|
The
|
|
|
|
.Ar period
|
|
|
|
specifies the number of beacon intervals between DTIM
|
|
|
|
and must be in the range 1 to 15.
|
2005-11-18 10:36:29 +00:00
|
|
|
By default DTIM is 1 (i.e., DTIM occurs at each beacon).
|
2011-11-12 23:17:01 +00:00
|
|
|
.It Cm quiet
|
2014-06-06 00:22:19 +00:00
|
|
|
Enable the use of quiet IE.
|
|
|
|
Hostap will use this to silence other
|
2011-11-12 23:17:01 +00:00
|
|
|
stations to reduce interference for radar detection when
|
2012-02-28 13:19:34 +00:00
|
|
|
operating on 5GHz frequency and doth support is enabled.
|
2011-11-12 23:17:01 +00:00
|
|
|
Use
|
|
|
|
.Fl quiet
|
|
|
|
to disable this functionality.
|
|
|
|
.It Cm quiet_period Ar period
|
|
|
|
Set the QUIET
|
|
|
|
.Ar period
|
|
|
|
to the number of beacon intervals between the start of regularly
|
|
|
|
scheduled quiet intervals defined by Quiet element.
|
|
|
|
.It Cm quiet_count Ar count
|
|
|
|
Set the QUIET
|
|
|
|
.Ar count
|
|
|
|
to the number of TBTTs until the beacon interval during which the
|
2014-06-06 00:22:19 +00:00
|
|
|
next quiet interval shall start.
|
|
|
|
A value of 1 indicates the quiet
|
2011-11-12 23:17:01 +00:00
|
|
|
interval will start during the beacon interval starting at the next
|
2014-06-06 00:22:19 +00:00
|
|
|
TBTT.
|
|
|
|
A value 0 is reserved.
|
2011-11-12 23:17:01 +00:00
|
|
|
.It Cm quiet_offset Ar offset
|
|
|
|
Set the QUIET
|
|
|
|
.Ar offset
|
|
|
|
to the offset of the start of the quiet interval from the TBTT
|
|
|
|
specified by the Quiet count, expressed in TUs.
|
|
|
|
The value of the
|
|
|
|
.Ar offset
|
|
|
|
shall be less than one beacon interval.
|
|
|
|
.It Cm quiet_duration Ar dur
|
|
|
|
Set the QUIET
|
|
|
|
.Ar dur
|
|
|
|
to the duration of the Quiet interval, expressed in TUs.
|
|
|
|
The value should be less than beacon interval.
|
2007-07-09 15:39:58 +00:00
|
|
|
.It Cm dturbo
|
|
|
|
Enable the use of Atheros Dynamic Turbo mode when communicating with
|
|
|
|
another Dynamic Turbo-capable station.
|
|
|
|
Dynamic Turbo mode is an Atheros-specific mechanism by which
|
|
|
|
stations switch between normal 802.11 operation and a ``boosted''
|
|
|
|
mode in which a 40MHz wide channel is used for communication.
|
|
|
|
Stations using Dynamic Turbo mode operate boosted only when the
|
|
|
|
channel is free of non-dturbo stations; when a non-dturbo station
|
|
|
|
is identified on the channel all stations will automatically drop
|
|
|
|
back to normal operation.
|
|
|
|
By default, Dynamic Turbo mode is not enabled, even if the device is capable.
|
|
|
|
Note that turbo mode (dynamic or static) is only allowed on some
|
|
|
|
channels depending on the regulatory constraints; use the
|
|
|
|
.Cm list chan
|
|
|
|
command to identify the channels where turbo mode may be used.
|
|
|
|
To disable Dynamic Turbo mode use
|
|
|
|
.Fl dturbo .
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm dwds
|
|
|
|
Enable Dynamic WDS (DWDS) support.
|
|
|
|
DWDS is a facility by which 4-address traffic can be carried between
|
|
|
|
stations operating in infrastructure mode.
|
|
|
|
A station first associates to an access point and authenticates using
|
2012-11-07 19:26:32 +00:00
|
|
|
normal procedures (e.g., WPA).
|
2008-04-20 20:35:46 +00:00
|
|
|
Then 4-address frames are passed to carry traffic for stations
|
|
|
|
operating on either side of the wireless link.
|
|
|
|
DWDS extends the normal WDS mechanism by leveraging existing security
|
|
|
|
protocols and eliminating static binding.
|
|
|
|
.Pp
|
|
|
|
When DWDS is enabled on an access point 4-address frames received from
|
|
|
|
an authorized station will generate a ``DWDS discovery'' event to user
|
|
|
|
applications.
|
|
|
|
This event should be used to create a WDS interface that is bound
|
|
|
|
to the remote station (and usually plumbed into a bridge).
|
|
|
|
Once the WDS interface is up and running 4-address traffic then logically
|
|
|
|
flows through that interface.
|
|
|
|
.Pp
|
|
|
|
When DWDS is enabled on a station, traffic with a destination address
|
|
|
|
different from the peer station are encapsulated in a 4-address frame
|
|
|
|
and transmitted to the peer.
|
|
|
|
All 4-address traffic uses the security information of the stations
|
2012-11-07 19:26:32 +00:00
|
|
|
(e.g., cryptographic keys).
|
2008-04-20 20:35:46 +00:00
|
|
|
A station is associated using 802.11n facilities may transport
|
|
|
|
4-address traffic using these same mechanisms; this depends on available
|
|
|
|
resources and capabilities of the device.
|
|
|
|
The DWDS implementation guards against layer 2 routing loops of
|
|
|
|
multicast traffic.
|
|
|
|
.It Cm ff
|
|
|
|
Enable the use of Atheros Fast Frames when communicating with
|
|
|
|
another Fast Frames-capable station.
|
|
|
|
Fast Frames are an encapsulation technique by which two 802.3
|
|
|
|
frames are transmitted in a single 802.11 frame.
|
|
|
|
This can noticeably improve throughput but requires that the
|
|
|
|
receiving station understand how to decapsulate the frame.
|
|
|
|
Fast frame use is negotiated using the Atheros 802.11 vendor-specific
|
|
|
|
protocol extension so enabling use is safe when communicating with
|
|
|
|
non-Atheros devices.
|
|
|
|
By default, use of fast frames is enabled if the device is capable.
|
|
|
|
To explicitly disable fast frames, use
|
|
|
|
.Fl ff .
|
2005-08-02 19:13:13 +00:00
|
|
|
.It Cm fragthreshold Ar length
|
|
|
|
Set the threshold for which transmitted frames are broken into fragments.
|
|
|
|
The
|
|
|
|
.Ar length
|
|
|
|
argument is the frame size in bytes and must be in the range 256 to 2346.
|
|
|
|
Setting
|
|
|
|
.Ar length
|
|
|
|
to
|
2005-11-18 10:36:29 +00:00
|
|
|
.Li 2346 ,
|
|
|
|
.Cm any ,
|
2005-08-02 19:13:13 +00:00
|
|
|
or
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm -
|
2005-08-02 19:13:13 +00:00
|
|
|
disables transmit fragmentation.
|
2008-04-20 20:35:46 +00:00
|
|
|
Not all adapters honor the fragmentation threshold.
|
2004-12-08 19:18:07 +00:00
|
|
|
.It Cm hidessid
|
2005-01-10 16:17:34 +00:00
|
|
|
When operating as an access point, do not broadcast the SSID
|
2005-08-02 19:13:13 +00:00
|
|
|
in beacon frames or respond to probe request frames unless
|
2005-11-18 10:36:29 +00:00
|
|
|
they are directed to the ap (i.e., they include the ap's SSID).
|
2005-08-02 19:13:13 +00:00
|
|
|
By default, the SSID is included in beacon frames and
|
|
|
|
undirected probe request frames are answered.
|
|
|
|
To re-enable the broadcast of the SSID etc., use
|
2004-12-08 19:18:07 +00:00
|
|
|
.Fl hidessid .
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm ht
|
|
|
|
Enable use of High Throughput (HT) when using 802.11n (default).
|
|
|
|
The 802.11n specification includes mechanisms for operation
|
|
|
|
on 20MHz and 40MHz wide channels using different signalling mechanisms
|
|
|
|
than specified in 802.11b, 802.11g, and 802.11a.
|
|
|
|
Stations negotiate use of these facilities, termed HT20 and HT40,
|
|
|
|
when they associate.
|
|
|
|
To disable all use of 802.11n use
|
|
|
|
.Fl ht .
|
2012-11-07 19:26:32 +00:00
|
|
|
To disable use of HT20 (e.g., to force only HT40 use) use
|
2008-04-20 20:35:46 +00:00
|
|
|
.Fl ht20 .
|
|
|
|
To disable use of HT40 use
|
|
|
|
.Fl ht40 .
|
|
|
|
.Pp
|
|
|
|
HT configuration is used to ``auto promote'' operation
|
|
|
|
when several choices are available.
|
|
|
|
For example, if a station associates to an 11n-capable access point
|
|
|
|
it controls whether the station uses legacy operation, HT20, or HT40.
|
|
|
|
When an 11n-capable device is setup as an access point and
|
|
|
|
Auto Channel Selection is used to locate a channel to operate on,
|
|
|
|
HT configuration controls whether legacy, HT20, or HT40 operation is setup
|
|
|
|
on the selected channel.
|
|
|
|
If a fixed channel is specified for a station then HT configuration can
|
2012-11-07 19:26:32 +00:00
|
|
|
be given as part of the channel specification; e.g., 6:ht/20 to setup
|
2008-04-20 20:35:46 +00:00
|
|
|
HT20 operation on channel 6.
|
|
|
|
.It Cm htcompat
|
|
|
|
Enable use of compatibility support for pre-802.11n devices (default).
|
|
|
|
The 802.11n protocol specification went through several incompatible iterations.
|
|
|
|
Some vendors implemented 11n support to older specifications that
|
|
|
|
will not interoperate with a purely 11n-compliant station.
|
|
|
|
In particular the information elements included in management frames
|
|
|
|
for old devices are different.
|
|
|
|
When compatibility support is enabled both standard and compatible data
|
|
|
|
will be provided.
|
2010-04-28 10:57:27 +00:00
|
|
|
Stations that associate using the compatibility mechanisms are flagged
|
2008-04-20 20:35:46 +00:00
|
|
|
in ``list sta''.
|
2010-04-28 10:57:27 +00:00
|
|
|
To disable compatibility support use
|
2008-04-20 20:35:46 +00:00
|
|
|
.Fl htcompat .
|
|
|
|
.It Cm htprotmode Ar technique
|
|
|
|
For interfaces operating in 802.11n, use the specified
|
|
|
|
.Ar technique
|
|
|
|
for protecting HT frames in a mixed legacy/HT network.
|
|
|
|
The set of valid techniques is
|
|
|
|
.Cm off ,
|
|
|
|
and
|
|
|
|
.Cm rts
|
|
|
|
(RTS/CTS, default).
|
|
|
|
Technique names are case insensitive.
|
|
|
|
.It Cm inact
|
|
|
|
Enable inactivity processing for stations associated to an
|
|
|
|
access point (default).
|
|
|
|
When operating as an access point the 802.11 layer monitors
|
|
|
|
the activity of each associated station.
|
|
|
|
When a station is inactive for 5 minutes it will send several
|
|
|
|
``probe frames'' to see if the station is still present.
|
|
|
|
If no response is received then the station is deauthenticated.
|
|
|
|
Applications that prefer to handle this work can disable this
|
|
|
|
facility by using
|
|
|
|
.Fl inact .
|
|
|
|
.It Cm indoor
|
|
|
|
Set the location to use in calculating regulatory constraints.
|
|
|
|
The location is also advertised in beacon and probe response frames
|
|
|
|
when 802.11d is enabled with
|
|
|
|
.Cm dotd .
|
|
|
|
See also
|
|
|
|
.Cm outdoor ,
|
|
|
|
.Cm anywhere ,
|
|
|
|
.Cm country ,
|
|
|
|
and
|
|
|
|
.Cm regdomain .
|
2005-11-18 10:36:29 +00:00
|
|
|
.It Cm list active
|
2005-08-02 19:13:13 +00:00
|
|
|
Display the list of channels available for use taking into account
|
|
|
|
any restrictions set with the
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm chanlist
|
2006-02-27 19:57:07 +00:00
|
|
|
directive.
|
|
|
|
See the description of
|
|
|
|
.Cm list chan
|
|
|
|
for more information.
|
2005-11-18 10:36:29 +00:00
|
|
|
.It Cm list caps
|
2005-08-02 19:13:13 +00:00
|
|
|
Display the adaptor's capabilities, including the operating
|
|
|
|
modes supported.
|
2005-11-18 10:36:29 +00:00
|
|
|
.It Cm list chan
|
2005-08-02 19:13:13 +00:00
|
|
|
Display the list of channels available for use.
|
2006-02-27 19:57:07 +00:00
|
|
|
Channels are shown with their IEEE channel number, equivalent
|
|
|
|
frequency, and usage modes.
|
|
|
|
Channels identified as
|
|
|
|
.Ql 11g
|
|
|
|
are also usable in
|
|
|
|
.Ql 11b
|
|
|
|
mode.
|
|
|
|
Channels identified as
|
|
|
|
.Ql 11a Turbo
|
|
|
|
may be used only for Atheros' Static Turbo mode
|
2006-09-18 11:55:10 +00:00
|
|
|
(specified with
|
|
|
|
. Cm mediaopt turbo ) .
|
2006-02-27 19:57:07 +00:00
|
|
|
Channels marked with a
|
|
|
|
.Ql *
|
|
|
|
have a regulatory constraint that they be passively scanned.
|
|
|
|
This means a station is not permitted to transmit on the channel until
|
|
|
|
it identifies the channel is being used for 802.11 communication;
|
|
|
|
typically by hearing a beacon frame from an access point operating
|
|
|
|
on the channel.
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm list freq
|
2005-08-02 19:13:13 +00:00
|
|
|
is another way of requesting this information.
|
2007-11-02 05:23:22 +00:00
|
|
|
By default a compacted list of channels is displayed; if the
|
|
|
|
.Fl v
|
|
|
|
option is specified then all channels are shown.
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm list countries
|
|
|
|
Display the set of country codes and regulatory domains that can be
|
|
|
|
used in regulatory configuration.
|
2005-11-18 10:36:29 +00:00
|
|
|
.It Cm list mac
|
2005-08-13 17:38:09 +00:00
|
|
|
Display the current MAC Access Control List state.
|
|
|
|
Each address is prefixed with a character that indicates the
|
|
|
|
current policy applied to it:
|
2005-11-18 10:36:29 +00:00
|
|
|
.Ql +
|
2005-08-13 17:38:09 +00:00
|
|
|
indicates the address is allowed access,
|
2005-11-18 10:36:29 +00:00
|
|
|
.Ql -
|
2005-08-13 17:38:09 +00:00
|
|
|
indicates the address is denied access,
|
2005-11-18 10:36:29 +00:00
|
|
|
.Ql *
|
2005-08-13 17:38:09 +00:00
|
|
|
indicates the address is present but the current policy open
|
2005-11-18 10:36:29 +00:00
|
|
|
(so the ACL is not consulted).
|
Implementation of the upcoming Wireless Mesh standard, 802.11s, on the
net80211 wireless stack. This work is based on the March 2009 D3.0 draft
standard. This standard is expected to become final next year.
This includes two main net80211 modules, ieee80211_mesh.c
which deals with peer link management, link metric calculation,
routing table control and mesh configuration and ieee80211_hwmp.c
which deals with the actually routing process on the mesh network.
HWMP is the mandatory routing protocol on by the mesh standard, but
others, such as RA-OLSR, can be implemented.
Authentication and encryption are not implemented.
There are several scripts under tools/tools/net80211/scripts that can be
used to test different mesh network topologies and they also teach you
how to setup a mesh vap (for the impatient: ifconfig wlan0 create
wlandev ... wlanmode mesh).
A new build option is available: IEEE80211_SUPPORT_MESH and it's enabled
by default on GENERIC kernels for i386, amd64, sparc64 and pc98.
Drivers that support mesh networks right now are: ath, ral and mwl.
More information at: http://wiki.freebsd.org/WifiMesh
Please note that this work is experimental. Also, please note that
bridging a mesh vap with another network interface is not yet supported.
Many thanks to the FreeBSD Foundation for sponsoring this project and to
Sam Leffler for his support.
Also, I would like to thank Gateworks Corporation for sending me a
Cambria board which was used during the development of this project.
Reviewed by: sam
Approved by: re (kensmith)
Obtained from: projects/mesh11s
2009-07-11 15:02:45 +00:00
|
|
|
.It Cm list mesh
|
|
|
|
Displays the mesh routing table, used for forwarding packets on a mesh
|
|
|
|
network.
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm list regdomain
|
|
|
|
Display the current regulatory settings including the available channels
|
|
|
|
and transmit power caps.
|
|
|
|
.It Cm list roam
|
|
|
|
Display the parameters that govern roaming operation.
|
|
|
|
.It Cm list txparam
|
|
|
|
Display the parameters that govern transmit operation.
|
|
|
|
.It Cm list txpower
|
|
|
|
Display the transmit power caps for each channel.
|
2005-11-18 10:36:29 +00:00
|
|
|
.It Cm list scan
|
2005-08-02 19:13:13 +00:00
|
|
|
Display the access points and/or ad-hoc neighbors
|
|
|
|
located in the vicinity.
|
2008-04-20 20:35:46 +00:00
|
|
|
This information may be updated automatically by the adapter
|
|
|
|
with a
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm scan
|
2007-07-09 15:39:58 +00:00
|
|
|
request or through background scanning.
|
2008-04-20 20:35:46 +00:00
|
|
|
Depending on the capabilities of the stations the following
|
|
|
|
flags can be included in the output:
|
|
|
|
.Bl -tag -width 3n
|
|
|
|
.It Li A
|
2020-06-04 13:06:49 +00:00
|
|
|
Channel agility.
|
|
|
|
.It Li B
|
|
|
|
PBCC modulation.
|
|
|
|
.It Li C
|
|
|
|
Poll request capability.
|
|
|
|
.It Li D
|
|
|
|
DSSS/OFDM capability.
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Li E
|
2020-06-04 13:06:49 +00:00
|
|
|
Extended Service Set (ESS).
|
|
|
|
.It Li I
|
|
|
|
Independent Basic Service Set (IBSS).
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Li P
|
2020-06-04 13:06:49 +00:00
|
|
|
Privacy capability.
|
|
|
|
The station requires authentication.
|
|
|
|
.It Li R
|
|
|
|
Robust Secure Network (RSN).
|
2010-05-14 15:06:12 +00:00
|
|
|
.It Li S
|
|
|
|
Short Preamble.
|
|
|
|
Indicates that the station is doing short preamble to optionally
|
|
|
|
improve throughput performance with 802.11g and 802.11b.
|
2020-06-04 13:06:49 +00:00
|
|
|
.It Li c
|
|
|
|
Pollable capability.
|
|
|
|
.It Li s
|
|
|
|
Short slot time capability.
|
2008-04-20 20:35:46 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
By default interesting information elements captured from the neighboring
|
|
|
|
stations are displayed at the end of each row.
|
|
|
|
Possible elements include:
|
|
|
|
.Cm WME
|
|
|
|
(station supports WME),
|
|
|
|
.Cm WPA
|
|
|
|
(station supports WPA),
|
2008-08-09 05:37:22 +00:00
|
|
|
.Cm WPS
|
|
|
|
(station supports WPS),
|
2008-04-20 20:35:46 +00:00
|
|
|
.Cm RSN
|
|
|
|
(station supports 802.11i/RSN),
|
|
|
|
.Cm HTCAP
|
|
|
|
(station supports 802.11n/HT communication),
|
|
|
|
.Cm ATH
|
2008-10-05 05:12:48 +00:00
|
|
|
(station supports Atheros protocol extensions),
|
2008-04-20 20:35:46 +00:00
|
|
|
.Cm VEN
|
|
|
|
(station supports unknown vendor-specific extensions).
|
|
|
|
If the
|
|
|
|
.Fl v
|
|
|
|
flag is used all the information elements and their
|
|
|
|
contents will be shown.
|
2008-10-19 09:45:29 +00:00
|
|
|
Specifying the
|
2008-04-20 20:35:46 +00:00
|
|
|
.Fl v
|
|
|
|
flag also enables display of long SSIDs.
|
2008-10-19 09:45:29 +00:00
|
|
|
The
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm list ap
|
2008-10-19 09:45:29 +00:00
|
|
|
command is another way of requesting this information.
|
2005-11-18 10:36:29 +00:00
|
|
|
.It Cm list sta
|
2005-08-02 19:13:13 +00:00
|
|
|
When operating as an access point display the stations that are
|
|
|
|
currently associated.
|
|
|
|
When operating in ad-hoc mode display stations identified as
|
|
|
|
neighbors in the IBSS.
|
Implementation of the upcoming Wireless Mesh standard, 802.11s, on the
net80211 wireless stack. This work is based on the March 2009 D3.0 draft
standard. This standard is expected to become final next year.
This includes two main net80211 modules, ieee80211_mesh.c
which deals with peer link management, link metric calculation,
routing table control and mesh configuration and ieee80211_hwmp.c
which deals with the actually routing process on the mesh network.
HWMP is the mandatory routing protocol on by the mesh standard, but
others, such as RA-OLSR, can be implemented.
Authentication and encryption are not implemented.
There are several scripts under tools/tools/net80211/scripts that can be
used to test different mesh network topologies and they also teach you
how to setup a mesh vap (for the impatient: ifconfig wlan0 create
wlandev ... wlanmode mesh).
A new build option is available: IEEE80211_SUPPORT_MESH and it's enabled
by default on GENERIC kernels for i386, amd64, sparc64 and pc98.
Drivers that support mesh networks right now are: ath, ral and mwl.
More information at: http://wiki.freebsd.org/WifiMesh
Please note that this work is experimental. Also, please note that
bridging a mesh vap with another network interface is not yet supported.
Many thanks to the FreeBSD Foundation for sponsoring this project and to
Sam Leffler for his support.
Also, I would like to thank Gateworks Corporation for sending me a
Cambria board which was used during the development of this project.
Reviewed by: sam
Approved by: re (kensmith)
Obtained from: projects/mesh11s
2009-07-11 15:02:45 +00:00
|
|
|
When operating in mesh mode display stations identified as
|
|
|
|
neighbors in the MBSS.
|
2007-07-09 15:39:58 +00:00
|
|
|
When operating in station mode display the access point.
|
2006-06-23 17:22:03 +00:00
|
|
|
Capabilities advertised by the stations are described under
|
|
|
|
the
|
|
|
|
.Cm scan
|
|
|
|
request.
|
2020-06-04 13:06:49 +00:00
|
|
|
The following flags can be included in the output:
|
2006-06-23 17:22:03 +00:00
|
|
|
.Bl -tag -width 3n
|
|
|
|
.It Li A
|
|
|
|
Authorized.
|
|
|
|
Indicates that the station is permitted to send/receive data frames.
|
|
|
|
.It Li E
|
|
|
|
Extended Rate Phy (ERP).
|
|
|
|
Indicates that the station is operating in an 802.11g network
|
|
|
|
using extended transmit rates.
|
2007-07-09 15:39:58 +00:00
|
|
|
.It Li H
|
|
|
|
High Throughput (HT).
|
2008-04-20 20:35:46 +00:00
|
|
|
Indicates that the station is using HT transmit rates.
|
2020-06-04 13:06:49 +00:00
|
|
|
If a
|
|
|
|
.Sq Li +
|
|
|
|
follows immediately after then the station associated
|
2008-04-20 20:35:46 +00:00
|
|
|
using deprecated mechanisms supported only when
|
|
|
|
.Cm htcompat
|
|
|
|
is enabled.
|
2006-06-23 17:22:03 +00:00
|
|
|
.It Li P
|
|
|
|
Power Save.
|
|
|
|
Indicates that the station is operating in power save mode.
|
|
|
|
.It Li Q
|
|
|
|
Quality of Service (QoS).
|
|
|
|
Indicates that the station is using QoS encapsulation for
|
|
|
|
data frame.
|
|
|
|
QoS encapsulation is enabled only when WME mode is enabled.
|
2010-05-14 15:06:12 +00:00
|
|
|
.It Li S
|
2020-06-04 13:06:49 +00:00
|
|
|
Short GI in HT 40MHz mode enabled.
|
|
|
|
If a
|
|
|
|
.Sq Li +
|
|
|
|
follows immediately after then short GI in HT 20MHz mode is enabled as well.
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Li T
|
|
|
|
Transitional Security Network (TSN).
|
|
|
|
Indicates that the station associated using TSN; see also
|
|
|
|
.Cm tsn
|
|
|
|
below.
|
|
|
|
.It Li W
|
|
|
|
Wi-Fi Protected Setup (WPS).
|
|
|
|
Indicates that the station associated using WPS.
|
2020-06-04 13:06:49 +00:00
|
|
|
.It Li s
|
|
|
|
Short GI in HT 20MHz mode enabled.
|
2006-06-23 17:22:03 +00:00
|
|
|
.El
|
2007-11-02 05:23:22 +00:00
|
|
|
.Pp
|
|
|
|
By default information elements received from associated stations
|
|
|
|
are displayed in a short form; the
|
|
|
|
.Fl v
|
2008-10-05 05:12:48 +00:00
|
|
|
flag causes this information to be displayed symbolically.
|
2005-11-18 10:36:29 +00:00
|
|
|
.It Cm list wme
|
2008-08-02 18:10:14 +00:00
|
|
|
Display the current channel parameters to use when operating in WME mode.
|
|
|
|
If the
|
|
|
|
.Fl v
|
|
|
|
option is specified then both channel and BSS parameters are displayed
|
|
|
|
for each AC (first channel, then BSS).
|
2005-08-02 19:13:13 +00:00
|
|
|
When WME mode is enabled for an adaptor this information will be
|
|
|
|
displayed with the regular status; this command is mostly useful
|
|
|
|
for examining parameters when WME mode is disabled.
|
|
|
|
See the description of the
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm wme
|
2005-08-02 19:13:13 +00:00
|
|
|
directive for information on the various parameters.
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm maxretry Ar count
|
|
|
|
Set the maximum number of tries to use in sending unicast frames.
|
|
|
|
The default setting is 6 but drivers may override this with a value
|
|
|
|
they choose.
|
2005-12-12 19:23:55 +00:00
|
|
|
.It Cm mcastrate Ar rate
|
|
|
|
Set the rate for transmitting multicast/broadcast frames.
|
2012-11-07 19:26:32 +00:00
|
|
|
Rates are specified as megabits/second in decimal; e.g.,\& 5.5 for 5.5 Mb/s.
|
2005-12-12 19:23:55 +00:00
|
|
|
This rate should be valid for the current operating conditions;
|
|
|
|
if an invalid rate is specified drivers are free to chose an
|
|
|
|
appropriate rate.
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm mgtrate Ar rate
|
|
|
|
Set the rate for transmitting management and/or control frames.
|
2012-11-07 19:26:32 +00:00
|
|
|
Rates are specified as megabits/second in decimal; e.g.,\& 5.5 for 5.5 Mb/s.
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm outdoor
|
|
|
|
Set the location to use in calculating regulatory constraints.
|
|
|
|
The location is also advertised in beacon and probe response frames
|
|
|
|
when 802.11d is enabled with
|
|
|
|
.Cm dotd .
|
|
|
|
See also
|
|
|
|
.Cm anywhere ,
|
|
|
|
.Cm country ,
|
|
|
|
.Cm indoor ,
|
|
|
|
and
|
|
|
|
.Cm regdomain .
|
2001-05-26 09:27:08 +00:00
|
|
|
.It Cm powersave
|
2004-12-08 19:18:07 +00:00
|
|
|
Enable powersave operation.
|
2005-01-10 16:17:34 +00:00
|
|
|
When operating as a client, the station will conserve power by
|
2004-12-08 19:18:07 +00:00
|
|
|
periodically turning off the radio and listening for
|
|
|
|
messages from the access point telling it there are packets waiting.
|
|
|
|
The station must then retrieve the packets.
|
2007-07-09 15:39:58 +00:00
|
|
|
Not all devices support power save operation as a client.
|
|
|
|
The 802.11 specification requires that all access points support
|
|
|
|
power save but some drivers do not.
|
2004-12-08 19:18:07 +00:00
|
|
|
Use
|
|
|
|
.Fl powersave
|
2007-07-09 15:39:58 +00:00
|
|
|
to disable powersave operation when operating as a client.
|
2001-05-26 09:27:08 +00:00
|
|
|
.It Cm powersavesleep Ar sleep
|
Update for revised 802.11 support:
o revised channel handling support; ifconfig now queries the kernel to
find the list of available channels and handles channel promotion;
channel attributes can be specified as part of the channel; e.g. 36:a
for channel 36 in 11a (as opposed to turbo A or HT A)
o use channel list to map between freq and IEEE channel #; this eliminates
all knowledge of how the mapping is done and fixes handling of cases
where channels overlap in the IEEE channel # space but are distinct in
the frequency+attributes space (e.g. PSB)
o add new knobs: bgscan, ff (Atheors fast frames), dturbo (Atheros
Dynamic Turbo mode), bgscanidle, bgscanintvl, scanvalid, roam:rssi11a,
roam:rssi11b, roam:rssi11g, roam:rate11a, roam:rate11b, roam:rate11g
(roaming parameters), burst, doth (forthcoming 11h support)
o print contents of WME, ATH, WPA, RSN, information elements with -v option
o print signal strength in dBm
o print noise floor in dBm
o add list txpow to print tx power caps/channel
o change default channel display in status to be more informative
2007-06-11 03:56:33 +00:00
|
|
|
Set the desired max powersave sleep time in TU's (1024 usecs).
|
|
|
|
By default the max powersave sleep time is 100 TU's.
|
2004-03-30 22:59:22 +00:00
|
|
|
.It Cm protmode Ar technique
|
2004-12-08 19:18:07 +00:00
|
|
|
For interfaces operating in 802.11g, use the specified
|
2004-05-17 08:35:43 +00:00
|
|
|
.Ar technique
|
|
|
|
for protecting OFDM frames in a mixed 11b/11g network.
|
2004-03-30 22:59:22 +00:00
|
|
|
The set of valid techniques is
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm off , cts
|
2004-03-30 22:59:22 +00:00
|
|
|
(CTS to self),
|
|
|
|
and
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm rtscts
|
2004-03-30 22:59:22 +00:00
|
|
|
(RTS/CTS).
|
|
|
|
Technique names are case insensitive.
|
2007-07-09 15:39:58 +00:00
|
|
|
Not all devices support
|
|
|
|
.Cm cts
|
|
|
|
as a protection technique.
|
2005-07-06 15:39:11 +00:00
|
|
|
.It Cm pureg
|
|
|
|
When operating as an access point in 802.11g mode allow only
|
|
|
|
11g-capable stations to associate (11b-only stations are not
|
|
|
|
permitted to associate).
|
|
|
|
To allow both 11g and 11b-only stations to associate, use
|
|
|
|
.Fl pureg .
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm puren
|
|
|
|
When operating as an access point in 802.11n mode allow only
|
|
|
|
HT-capable stations to associate (legacy stations are not
|
|
|
|
permitted to associate).
|
|
|
|
To allow both HT and legacy stations to associate, use
|
|
|
|
.Fl puren .
|
|
|
|
.It Cm regdomain Ar sku
|
|
|
|
Set the regulatory domain to use in calculating the regulatory constraints
|
|
|
|
for operation.
|
|
|
|
In particular the set of available channels, how the wireless device
|
|
|
|
will operation on the channels, and the maximum transmit power that
|
|
|
|
can be used on a channel are defined by this setting.
|
2013-05-13 18:13:50 +00:00
|
|
|
Regdomain codes (SKU's) are taken from
|
|
|
|
.Pa /etc/regdomain.xml
|
|
|
|
and can also
|
2008-04-20 20:35:46 +00:00
|
|
|
be viewed with the ``list countries'' request.
|
|
|
|
Note that not all devices support changing the regdomain from a default
|
|
|
|
setting; typically stored in EEPROM.
|
|
|
|
See also
|
|
|
|
.Cm country ,
|
|
|
|
.Cm indoor ,
|
|
|
|
.Cm outdoor ,
|
|
|
|
and
|
|
|
|
.Cm anywhere .
|
2008-09-22 00:30:26 +00:00
|
|
|
.It Cm rifs
|
|
|
|
Enable use of Reduced InterFrame Spacing (RIFS) when operating in 802.11n
|
|
|
|
on an HT channel.
|
|
|
|
Note that RIFS must be supported by both the station and access point
|
|
|
|
for it to be used.
|
|
|
|
To disable RIFS use
|
|
|
|
.Fl rifs .
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm roam:rate Ar rate
|
|
|
|
Set the threshold for controlling roaming when operating in a BSS.
|
|
|
|
The
|
|
|
|
.Ar rate
|
|
|
|
parameter specifies the transmit rate in megabits
|
|
|
|
at which roaming should be considered.
|
|
|
|
If the current transmit rate drops below this setting and background scanning
|
|
|
|
is enabled, then the system will check if a more desirable access point is
|
|
|
|
available and switch over to it.
|
|
|
|
The current scan cache contents are used if they are considered
|
|
|
|
valid according to the
|
|
|
|
.Cm scanvalid
|
|
|
|
parameter; otherwise a background scan operation is triggered before
|
|
|
|
any selection occurs.
|
|
|
|
Each channel type has a separate rate threshold; the default values are:
|
|
|
|
12 Mb/s (11a), 2 Mb/s (11b), 2 Mb/s (11g), MCS 1 (11na, 11ng).
|
|
|
|
.It Cm roam:rssi Ar rssi
|
|
|
|
Set the threshold for controlling roaming when operating in a BSS.
|
|
|
|
The
|
|
|
|
.Ar rssi
|
|
|
|
parameter specifies the receive signal strength in dBm units
|
|
|
|
at which roaming should be considered.
|
|
|
|
If the current rssi drops below this setting and background scanning
|
|
|
|
is enabled, then the system will check if a more desirable access point is
|
|
|
|
available and switch over to it.
|
|
|
|
The current scan cache contents are used if they are considered
|
|
|
|
valid according to the
|
|
|
|
.Cm scanvalid
|
|
|
|
parameter; otherwise a background scan operation is triggered before
|
|
|
|
any selection occurs.
|
2008-08-27 12:54:29 +00:00
|
|
|
Each channel type has a separate rssi threshold; the default values are
|
2008-04-20 20:35:46 +00:00
|
|
|
all 7 dBm.
|
2004-12-08 19:18:07 +00:00
|
|
|
.It Cm roaming Ar mode
|
|
|
|
When operating as a station, control how the system will
|
|
|
|
behave when communication with the current access point
|
|
|
|
is broken.
|
2005-01-10 16:17:34 +00:00
|
|
|
The
|
|
|
|
.Ar mode
|
|
|
|
argument may be one of
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm device
|
2004-12-08 19:18:07 +00:00
|
|
|
(leave it to the hardware device to decide),
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm auto
|
2005-01-10 16:17:34 +00:00
|
|
|
(handle either in the device or the operating system\[em]as appropriate),
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm manual
|
2004-12-08 19:18:07 +00:00
|
|
|
(do nothing until explicitly instructed).
|
2005-01-10 16:17:34 +00:00
|
|
|
By default, the device is left to handle this if it is
|
|
|
|
capable; otherwise, the operating system will automatically
|
2004-12-08 19:18:07 +00:00
|
|
|
attempt to reestablish communication.
|
2007-07-09 15:39:58 +00:00
|
|
|
Manual mode is used by applications such as
|
|
|
|
.Xr wpa_supplicant 8
|
|
|
|
that want to control the selection of an access point.
|
2004-03-30 22:59:22 +00:00
|
|
|
.It Cm rtsthreshold Ar length
|
2004-12-08 19:18:07 +00:00
|
|
|
Set the threshold for which
|
2004-03-30 22:59:22 +00:00
|
|
|
transmitted frames are preceded by transmission of an
|
|
|
|
RTS
|
|
|
|
control frame.
|
2004-05-17 08:35:43 +00:00
|
|
|
The
|
|
|
|
.Ar length
|
|
|
|
argument
|
2005-08-02 19:13:13 +00:00
|
|
|
is the frame size in bytes and must be in the range 1 to 2346.
|
|
|
|
Setting
|
|
|
|
.Ar length
|
|
|
|
to
|
2005-11-18 10:36:29 +00:00
|
|
|
.Li 2346 ,
|
|
|
|
.Cm any ,
|
2005-08-02 19:13:13 +00:00
|
|
|
or
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm -
|
2005-08-02 19:13:13 +00:00
|
|
|
disables transmission of RTS frames.
|
2008-04-20 20:35:46 +00:00
|
|
|
Not all adapters support setting the RTS threshold.
|
2004-12-08 19:18:07 +00:00
|
|
|
.It Cm scan
|
2005-08-02 19:13:13 +00:00
|
|
|
Initiate a scan of neighboring stations, wait for it to complete, and
|
|
|
|
display all stations found.
|
|
|
|
Only the super-user can initiate a scan.
|
2008-04-20 20:35:46 +00:00
|
|
|
See
|
|
|
|
.Cm list scan
|
|
|
|
for information on the display.
|
|
|
|
By default a background scan is done; otherwise a foreground
|
|
|
|
scan is done and the station may roam to a different access point.
|
2005-08-02 19:13:13 +00:00
|
|
|
The
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm list scan
|
2005-08-02 19:13:13 +00:00
|
|
|
request can be used to show recent scan results without
|
|
|
|
initiating a new scan.
|
2007-07-09 15:39:58 +00:00
|
|
|
.It Cm scanvalid Ar threshold
|
|
|
|
Set the maximum time the scan cache contents are considered valid;
|
2012-11-07 19:26:32 +00:00
|
|
|
i.e., will be used without first triggering a scan operation to
|
2007-07-09 15:39:58 +00:00
|
|
|
refresh the data.
|
|
|
|
The
|
|
|
|
.Ar threshold
|
|
|
|
parameter is specified in seconds and defaults to 60 seconds.
|
|
|
|
The minimum setting for
|
|
|
|
.Ar threshold
|
|
|
|
is 10 seconds.
|
|
|
|
One should take care setting this threshold; if it is set too low
|
|
|
|
then attempts to roam to another access point may trigger unnecessary
|
|
|
|
background scan operations.
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm shortgi
|
|
|
|
Enable use of Short Guard Interval when operating in 802.11n
|
|
|
|
on an HT channel.
|
|
|
|
NB: this currently enables Short GI on both HT40 and HT20 channels.
|
|
|
|
To disable Short GI use
|
|
|
|
.Fl shortgi .
|
2008-09-22 00:30:26 +00:00
|
|
|
.It Cm smps
|
|
|
|
Enable use of Static Spatial Multiplexing Power Save (SMPS)
|
|
|
|
when operating in 802.11n.
|
|
|
|
A station operating with Static SMPS maintains only a single
|
|
|
|
receive chain active (this can significantly reduce power consumption).
|
|
|
|
To disable SMPS use
|
|
|
|
.Fl smps .
|
|
|
|
.It Cm smpsdyn
|
|
|
|
Enable use of Dynamic Spatial Multiplexing Power Save (SMPS)
|
|
|
|
when operating in 802.11n.
|
|
|
|
A station operating with Dynamic SMPS maintains only a single
|
|
|
|
receive chain active but switches to multiple receive chains when it
|
|
|
|
receives an RTS frame (this can significantly reduce power consumption).
|
|
|
|
Note that stations cannot distinguish between RTS/CTS intended to
|
|
|
|
enable multiple receive chains and those used for other purposes.
|
|
|
|
To disable SMPS use
|
|
|
|
.Fl smps .
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm ssid Ar ssid
|
|
|
|
Set the desired Service Set Identifier (aka network name).
|
|
|
|
The SSID is a string up to 32 characters
|
|
|
|
in length and may be specified as either a normal string or in
|
|
|
|
hexadecimal when preceded by
|
|
|
|
.Ql 0x .
|
|
|
|
Additionally, the SSID may be cleared by setting it to
|
|
|
|
.Ql - .
|
2009-01-08 17:12:47 +00:00
|
|
|
.It Cm tdmaslot Ar slot
|
|
|
|
When operating with TDMA, use the specified
|
|
|
|
.Ar slot
|
|
|
|
configuration.
|
|
|
|
The
|
|
|
|
.Ar slot
|
|
|
|
is a number between 0 and the maximum number of slots in the BSS.
|
|
|
|
Note that a station configured as slot 0 is a master and
|
|
|
|
will broadcast beacon frames advertising the BSS;
|
|
|
|
stations configured to use other slots will always
|
|
|
|
scan to locate a master before they ever transmit.
|
|
|
|
By default
|
|
|
|
.Cm tdmaslot
|
|
|
|
is set to 1.
|
|
|
|
.It Cm tdmaslotcnt Ar cnt
|
|
|
|
When operating with TDMA, setup a BSS with
|
|
|
|
.Ar cnt
|
|
|
|
slots.
|
|
|
|
The slot count may be at most 8.
|
|
|
|
The current implementation is only tested with two stations
|
2012-11-07 19:26:32 +00:00
|
|
|
(i.e., point to point applications).
|
2009-01-08 17:12:47 +00:00
|
|
|
This setting is only meaningful when a station is configured as slot 0;
|
|
|
|
other stations adopt this setting from the BSS they join.
|
|
|
|
By default
|
|
|
|
.Cm tdmaslotcnt
|
|
|
|
is set to 2.
|
|
|
|
.It Cm tdmaslotlen Ar len
|
|
|
|
When operating with TDMA, setup a BSS such that each station has a slot
|
|
|
|
.Ar len
|
|
|
|
microseconds long.
|
|
|
|
The slot length must be at least 150 microseconds (1/8 TU)
|
|
|
|
and no more than 65 milliseconds.
|
|
|
|
Note that setting too small a slot length may result in poor channel
|
|
|
|
bandwidth utilization due to factors such as timer granularity and
|
|
|
|
guard time.
|
|
|
|
This setting is only meaningful when a station is configured as slot 0;
|
|
|
|
other stations adopt this setting from the BSS they join.
|
|
|
|
By default
|
|
|
|
.Cm tdmaslotlen
|
|
|
|
is set to 10 milliseconds.
|
|
|
|
.It Cm tdmabintval Ar intval
|
|
|
|
When operating with TDMA, setup a BSS such that beacons are transmitted every
|
|
|
|
.Ar intval
|
|
|
|
superframes to synchronize the TDMA slot timing.
|
2012-11-07 19:26:32 +00:00
|
|
|
A superframe is defined as the number of slots times the slot length; e.g.,
|
2009-01-08 17:12:47 +00:00
|
|
|
a BSS with two slots of 10 milliseconds has a 20 millisecond superframe.
|
|
|
|
The beacon interval may not be zero.
|
|
|
|
A lower setting of
|
|
|
|
.Cm tdmabintval
|
|
|
|
causes the timers to be resynchronized more often; this can be help if
|
|
|
|
significant timer drift is observed.
|
|
|
|
By default
|
|
|
|
.Cm tdmabintval
|
|
|
|
is set to 5.
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm tsn
|
|
|
|
When operating as an access point with WPA/802.11i allow legacy
|
|
|
|
stations to associate using static key WEP and open authentication.
|
|
|
|
To disallow legacy station use of WEP, use
|
|
|
|
.Fl tsn .
|
2004-03-30 22:59:22 +00:00
|
|
|
.It Cm txpower Ar power
|
2004-12-08 19:18:07 +00:00
|
|
|
Set the power used to transmit frames.
|
2004-05-17 08:35:43 +00:00
|
|
|
The
|
|
|
|
.Ar power
|
2007-11-02 05:23:22 +00:00
|
|
|
argument is specified in .5 dBm units.
|
2004-03-30 22:59:22 +00:00
|
|
|
Out of range values are truncated.
|
|
|
|
Typically only a few discreet power settings are available and
|
|
|
|
the driver will use the setting closest to the specified value.
|
2008-04-20 20:35:46 +00:00
|
|
|
Not all adapters support changing the transmit power.
|
|
|
|
.It Cm ucastrate Ar rate
|
|
|
|
Set a fixed rate for transmitting unicast frames.
|
2012-11-07 19:26:32 +00:00
|
|
|
Rates are specified as megabits/second in decimal; e.g.,\& 5.5 for 5.5 Mb/s.
|
2008-04-20 20:35:46 +00:00
|
|
|
This rate should be valid for the current operating conditions;
|
|
|
|
if an invalid rate is specified drivers are free to chose an
|
|
|
|
appropriate rate.
|
2001-05-26 09:27:08 +00:00
|
|
|
.It Cm wepmode Ar mode
|
2004-12-08 19:18:07 +00:00
|
|
|
Set the desired WEP mode.
|
2008-04-20 20:35:46 +00:00
|
|
|
Not all adapters support all modes.
|
2001-07-05 12:37:08 +00:00
|
|
|
The set of valid modes is
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm off , on ,
|
2001-05-26 09:27:08 +00:00
|
|
|
and
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm mixed .
|
2004-05-17 08:35:43 +00:00
|
|
|
The
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm mixed
|
2001-05-26 09:27:08 +00:00
|
|
|
mode explicitly tells the adaptor to allow association with access
|
2001-07-05 12:37:08 +00:00
|
|
|
points which allow both encrypted and unencrypted traffic.
|
2008-04-20 20:35:46 +00:00
|
|
|
On these adapters,
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm on
|
2001-07-05 12:37:08 +00:00
|
|
|
means that the access point must only allow encrypted connections.
|
2008-04-20 20:35:46 +00:00
|
|
|
On other adapters,
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm on
|
2001-05-26 09:27:08 +00:00
|
|
|
is generally another name for
|
2005-11-18 10:36:29 +00:00
|
|
|
.Cm mixed .
|
2001-05-26 09:27:08 +00:00
|
|
|
Modes are case insensitive.
|
|
|
|
.It Cm weptxkey Ar index
|
2004-12-08 19:18:07 +00:00
|
|
|
Set the WEP key to be used for transmission.
|
2005-12-26 18:15:09 +00:00
|
|
|
This is the same as setting the default transmission key with
|
|
|
|
.Cm deftxkey .
|
2001-07-05 12:37:08 +00:00
|
|
|
.It Cm wepkey Ar key Ns | Ns Ar index : Ns Ar key
|
2004-12-08 19:18:07 +00:00
|
|
|
Set the selected WEP key.
|
2001-07-05 12:37:08 +00:00
|
|
|
If an
|
2001-05-26 09:27:08 +00:00
|
|
|
.Ar index
|
2001-07-05 12:37:08 +00:00
|
|
|
is not given, key 1 is set.
|
|
|
|
A WEP key will be either 5 or 13
|
2010-08-16 15:18:30 +00:00
|
|
|
characters (40 or 104 bits) depending on the local network and the
|
2001-07-05 12:37:08 +00:00
|
|
|
capabilities of the adaptor.
|
|
|
|
It may be specified either as a plain
|
2005-06-13 15:49:59 +00:00
|
|
|
string or as a string of hexadecimal digits preceded by
|
2001-07-05 12:37:08 +00:00
|
|
|
.Ql 0x .
|
2002-08-12 06:59:04 +00:00
|
|
|
For maximum portability, hex keys are recommended;
|
2002-08-13 11:51:03 +00:00
|
|
|
the mapping of text keys to WEP encryption is usually driver-specific.
|
2002-11-25 16:01:28 +00:00
|
|
|
In particular, the
|
|
|
|
.Tn Windows
|
|
|
|
drivers do this mapping differently to
|
2002-08-13 11:51:03 +00:00
|
|
|
.Fx .
|
2001-05-26 09:27:08 +00:00
|
|
|
A key may be cleared by setting it to
|
2001-07-05 12:37:08 +00:00
|
|
|
.Ql - .
|
|
|
|
If WEP is supported then there are at least four keys.
|
2008-04-20 20:35:46 +00:00
|
|
|
Some adapters support more than four keys.
|
2001-07-05 12:37:08 +00:00
|
|
|
If that is the case, then the first four keys
|
2001-05-26 09:27:08 +00:00
|
|
|
(1-4) will be the standard temporary keys and any others will be adaptor
|
|
|
|
specific keys such as permanent keys stored in NVRAM.
|
2008-02-29 20:42:17 +00:00
|
|
|
.Pp
|
|
|
|
Note that you must set a default transmit key with
|
|
|
|
.Cm deftxkey
|
|
|
|
for the system to know which key to use in encrypting outbound traffic.
|
2004-12-08 19:18:07 +00:00
|
|
|
.It Cm wme
|
2005-08-02 19:13:13 +00:00
|
|
|
Enable Wireless Multimedia Extensions (WME) support, if available,
|
2004-12-08 19:18:07 +00:00
|
|
|
for the specified interface.
|
|
|
|
WME is a subset of the IEEE 802.11e standard to support the
|
|
|
|
efficient communication of realtime and multimedia data.
|
2005-01-10 16:17:34 +00:00
|
|
|
To disable WME support, use
|
2004-12-08 19:18:07 +00:00
|
|
|
.Fl wme .
|
2008-04-20 20:35:46 +00:00
|
|
|
Another name for this parameter is
|
|
|
|
.Cm wmm .
|
2005-08-02 19:13:13 +00:00
|
|
|
.Pp
|
|
|
|
The following parameters are meaningful only when WME support is in use.
|
|
|
|
Parameters are specified per-AC (Access Category) and
|
|
|
|
split into those that are used by a station when acting
|
|
|
|
as an access point and those for client stations in the BSS.
|
|
|
|
The latter are received from the access point and may not be changed
|
|
|
|
(at the station).
|
|
|
|
The following Access Categories are recognized:
|
|
|
|
.Pp
|
2005-11-18 10:36:29 +00:00
|
|
|
.Bl -tag -width ".Cm AC_BK" -compact
|
2005-08-02 19:13:13 +00:00
|
|
|
.It Cm AC_BE
|
2005-11-18 10:36:29 +00:00
|
|
|
(or
|
|
|
|
.Cm BE )
|
|
|
|
best effort delivery,
|
2005-08-02 19:13:13 +00:00
|
|
|
.It Cm AC_BK
|
2005-11-18 10:36:29 +00:00
|
|
|
(or
|
|
|
|
.Cm BK )
|
|
|
|
background traffic,
|
2005-08-02 19:13:13 +00:00
|
|
|
.It Cm AC_VI
|
2005-11-18 10:36:29 +00:00
|
|
|
(or
|
|
|
|
.Cm VI )
|
|
|
|
video traffic,
|
2005-08-02 19:13:13 +00:00
|
|
|
.It Cm AC_VO
|
2005-11-18 10:36:29 +00:00
|
|
|
(or
|
|
|
|
.Cm VO )
|
|
|
|
voice traffic.
|
2005-08-02 19:13:13 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
AC parameters are case-insensitive.
|
|
|
|
Traffic classification is done in the operating system using the
|
|
|
|
vlan priority associated with data frames or the
|
|
|
|
ToS (Type of Service) indication in IP-encapsulated frames.
|
2005-11-18 10:36:29 +00:00
|
|
|
If neither information is present, traffic is assigned to the
|
2005-08-02 19:13:13 +00:00
|
|
|
Best Effort (BE) category.
|
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm ack Ar ac
|
|
|
|
Set the ACK policy for QoS transmissions by the local station;
|
|
|
|
this controls whether or not data frames transmitted by a station
|
|
|
|
require an ACK response from the receiving station.
|
|
|
|
To disable waiting for an ACK use
|
|
|
|
.Fl ack .
|
|
|
|
This parameter is applied only to the local station.
|
|
|
|
.It Cm acm Ar ac
|
|
|
|
Enable the Admission Control Mandatory (ACM) mechanism
|
|
|
|
for transmissions by the local station.
|
|
|
|
To disable the ACM use
|
|
|
|
.Fl acm .
|
|
|
|
On stations in a BSS this parameter is read-only and indicates
|
|
|
|
the setting received from the access point.
|
|
|
|
NB: ACM is not supported right now.
|
|
|
|
.It Cm aifs Ar ac Ar count
|
|
|
|
Set the Arbitration Inter Frame Spacing (AIFS)
|
|
|
|
channel access parameter to use for transmissions
|
|
|
|
by the local station.
|
|
|
|
On stations in a BSS this parameter is read-only and indicates
|
|
|
|
the setting received from the access point.
|
|
|
|
.It Cm cwmin Ar ac Ar count
|
|
|
|
Set the CWmin channel access parameter to use for transmissions
|
|
|
|
by the local station.
|
|
|
|
On stations in a BSS this parameter is read-only and indicates
|
|
|
|
the setting received from the access point.
|
|
|
|
.It Cm cwmax Ar ac Ar count
|
|
|
|
Set the CWmax channel access parameter to use for transmissions
|
|
|
|
by the local station.
|
|
|
|
On stations in a BSS this parameter is read-only and indicates
|
|
|
|
the setting received from the access point.
|
|
|
|
.It Cm txoplimit Ar ac Ar limit
|
|
|
|
Set the Transmission Opportunity Limit channel access parameter
|
|
|
|
to use for transmissions by the local station.
|
|
|
|
This parameter defines an interval of time when a WME station
|
|
|
|
has the right to initiate transmissions onto the wireless medium.
|
|
|
|
On stations in a BSS this parameter is read-only and indicates
|
|
|
|
the setting received from the access point.
|
|
|
|
.It Cm bss:aifs Ar ac Ar count
|
|
|
|
Set the AIFS channel access parameter to send to stations in a BSS.
|
|
|
|
This parameter is meaningful only when operating in ap mode.
|
|
|
|
.It Cm bss:cwmin Ar ac Ar count
|
|
|
|
Set the CWmin channel access parameter to send to stations in a BSS.
|
|
|
|
This parameter is meaningful only when operating in ap mode.
|
|
|
|
.It Cm bss:cwmax Ar ac Ar count
|
|
|
|
Set the CWmax channel access parameter to send to stations in a BSS.
|
|
|
|
This parameter is meaningful only when operating in ap mode.
|
|
|
|
.It Cm bss:txoplimit Ar ac Ar limit
|
|
|
|
Set the TxOpLimit channel access parameter to send to stations in a BSS.
|
|
|
|
This parameter is meaningful only when operating in ap mode.
|
|
|
|
.El
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm wps
|
|
|
|
Enable Wireless Privacy Subscriber support.
|
|
|
|
Note that WPS support requires a WPS-capable supplicant.
|
|
|
|
To disable this function use
|
|
|
|
.Fl wps .
|
2005-08-02 19:13:13 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
The following parameters support an optional access control list
|
2008-04-20 20:35:46 +00:00
|
|
|
feature available with some adapters when operating in ap mode; see
|
2005-08-02 19:13:13 +00:00
|
|
|
.Xr wlan_acl 4 .
|
|
|
|
This facility allows an access point to accept/deny association
|
|
|
|
requests based on the MAC address of the station.
|
|
|
|
Note that this feature does not significantly enhance security
|
|
|
|
as MAC address spoofing is easy to do.
|
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm mac:add Ar address
|
|
|
|
Add the specified MAC address to the database.
|
|
|
|
Depending on the policy setting association requests from the
|
|
|
|
specified station will be allowed or denied.
|
|
|
|
.It Cm mac:allow
|
|
|
|
Set the ACL policy to permit association only by
|
|
|
|
stations registered in the database.
|
2006-02-15 23:16:03 +00:00
|
|
|
.It Cm mac:del Ar address
|
2005-08-02 19:13:13 +00:00
|
|
|
Delete the specified MAC address from the database.
|
|
|
|
.It Cm mac:deny
|
|
|
|
Set the ACL policy to deny association only by
|
|
|
|
stations registered in the database.
|
2006-02-15 23:16:03 +00:00
|
|
|
.It Cm mac:kick Ar address
|
2005-08-13 17:38:09 +00:00
|
|
|
Force the specified station to be deauthenticated.
|
|
|
|
This typically is done to block a station after updating the
|
|
|
|
address database.
|
2005-08-02 19:13:13 +00:00
|
|
|
.It Cm mac:open
|
|
|
|
Set the ACL policy to allow all stations to associate.
|
|
|
|
.It Cm mac:flush
|
|
|
|
Delete all entries in the database.
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm mac:radius
|
|
|
|
Set the ACL policy to permit association only by
|
|
|
|
stations approved by a RADIUS server.
|
|
|
|
Note that this feature requires the
|
|
|
|
.Xr hostapd 8
|
|
|
|
program be configured to do the right thing
|
|
|
|
as it handles the RADIUS processing
|
|
|
|
(and marks stations as authorized).
|
2004-12-08 19:18:07 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
Implementation of the upcoming Wireless Mesh standard, 802.11s, on the
net80211 wireless stack. This work is based on the March 2009 D3.0 draft
standard. This standard is expected to become final next year.
This includes two main net80211 modules, ieee80211_mesh.c
which deals with peer link management, link metric calculation,
routing table control and mesh configuration and ieee80211_hwmp.c
which deals with the actually routing process on the mesh network.
HWMP is the mandatory routing protocol on by the mesh standard, but
others, such as RA-OLSR, can be implemented.
Authentication and encryption are not implemented.
There are several scripts under tools/tools/net80211/scripts that can be
used to test different mesh network topologies and they also teach you
how to setup a mesh vap (for the impatient: ifconfig wlan0 create
wlandev ... wlanmode mesh).
A new build option is available: IEEE80211_SUPPORT_MESH and it's enabled
by default on GENERIC kernels for i386, amd64, sparc64 and pc98.
Drivers that support mesh networks right now are: ath, ral and mwl.
More information at: http://wiki.freebsd.org/WifiMesh
Please note that this work is experimental. Also, please note that
bridging a mesh vap with another network interface is not yet supported.
Many thanks to the FreeBSD Foundation for sponsoring this project and to
Sam Leffler for his support.
Also, I would like to thank Gateworks Corporation for sending me a
Cambria board which was used during the development of this project.
Reviewed by: sam
Approved by: re (kensmith)
Obtained from: projects/mesh11s
2009-07-11 15:02:45 +00:00
|
|
|
The following parameters are related to a wireless interface operating in mesh
|
|
|
|
mode:
|
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm meshid Ar meshid
|
|
|
|
Set the desired Mesh Identifier.
|
|
|
|
The Mesh ID is a string up to 32 characters in length.
|
|
|
|
A mesh interface must have a Mesh Identifier specified
|
|
|
|
to reach an operational state.
|
|
|
|
.It Cm meshttl Ar ttl
|
|
|
|
Set the desired ``time to live'' for mesh forwarded packets;
|
|
|
|
this is the number of hops a packet may be forwarded before
|
|
|
|
it is discarded.
|
|
|
|
The default setting for
|
|
|
|
.Cm meshttl
|
|
|
|
is 31.
|
|
|
|
.It Cm meshpeering
|
|
|
|
Enable or disable peering with neighbor mesh stations.
|
|
|
|
Stations must peer before any data packets can be exchanged.
|
|
|
|
By default
|
|
|
|
.Cm meshpeering
|
|
|
|
is enabled.
|
|
|
|
.It Cm meshforward
|
|
|
|
Enable or disable forwarding packets by a mesh interface.
|
|
|
|
By default
|
|
|
|
.Cm meshforward
|
|
|
|
is enabled.
|
2012-05-01 16:15:34 +00:00
|
|
|
.It Cm meshgate
|
|
|
|
This attribute specifies whether or not the mesh STA activates mesh gate
|
|
|
|
announcements.
|
|
|
|
By default
|
|
|
|
.Cm meshgate
|
|
|
|
is disabled.
|
Implementation of the upcoming Wireless Mesh standard, 802.11s, on the
net80211 wireless stack. This work is based on the March 2009 D3.0 draft
standard. This standard is expected to become final next year.
This includes two main net80211 modules, ieee80211_mesh.c
which deals with peer link management, link metric calculation,
routing table control and mesh configuration and ieee80211_hwmp.c
which deals with the actually routing process on the mesh network.
HWMP is the mandatory routing protocol on by the mesh standard, but
others, such as RA-OLSR, can be implemented.
Authentication and encryption are not implemented.
There are several scripts under tools/tools/net80211/scripts that can be
used to test different mesh network topologies and they also teach you
how to setup a mesh vap (for the impatient: ifconfig wlan0 create
wlandev ... wlanmode mesh).
A new build option is available: IEEE80211_SUPPORT_MESH and it's enabled
by default on GENERIC kernels for i386, amd64, sparc64 and pc98.
Drivers that support mesh networks right now are: ath, ral and mwl.
More information at: http://wiki.freebsd.org/WifiMesh
Please note that this work is experimental. Also, please note that
bridging a mesh vap with another network interface is not yet supported.
Many thanks to the FreeBSD Foundation for sponsoring this project and to
Sam Leffler for his support.
Also, I would like to thank Gateworks Corporation for sending me a
Cambria board which was used during the development of this project.
Reviewed by: sam
Approved by: re (kensmith)
Obtained from: projects/mesh11s
2009-07-11 15:02:45 +00:00
|
|
|
.It Cm meshmetric Ar protocol
|
|
|
|
Set the specified
|
|
|
|
.Ar protocol
|
|
|
|
as the link metric protocol used on a mesh network.
|
|
|
|
The default protocol is called
|
|
|
|
.Ar AIRTIME .
|
|
|
|
The mesh interface will restart after changing this setting.
|
|
|
|
.It Cm meshpath Ar protocol
|
|
|
|
Set the specified
|
|
|
|
.Ar protocol
|
|
|
|
as the path selection protocol used on a mesh network.
|
|
|
|
The only available protocol at the moment is called
|
|
|
|
.Ar HWMP
|
|
|
|
(Hybrid Wireless Mesh Protocol).
|
|
|
|
The mesh interface will restart after changing this setting.
|
|
|
|
.It Cm hwmprootmode Ar mode
|
|
|
|
Stations on a mesh network can operate as ``root nodes.''
|
|
|
|
Root nodes try to find paths to all mesh nodes and advertise themselves
|
|
|
|
regularly.
|
|
|
|
When there is a root mesh node on a network, other mesh nodes can setup
|
|
|
|
paths between themselves faster because they can use the root node
|
|
|
|
to find the destination.
|
|
|
|
This path may not be the best, but on-demand
|
|
|
|
routing will eventually find the best path.
|
|
|
|
The following modes are recognized:
|
|
|
|
.Pp
|
|
|
|
.Bl -tag -width ".Cm PROACTIVE" -compact
|
|
|
|
.It Cm DISABLED
|
|
|
|
Disable root mode.
|
|
|
|
.It Cm NORMAL
|
|
|
|
Send broadcast path requests every two seconds.
|
|
|
|
Nodes on the mesh without a path to this root mesh station with try to
|
|
|
|
discover a path to us.
|
|
|
|
.It Cm PROACTIVE
|
2012-06-05 18:19:52 +00:00
|
|
|
Send broadcast path requests every two seconds and every node must reply
|
2010-08-16 15:18:30 +00:00
|
|
|
with a path reply even if it already has a path to this root mesh station.
|
Implementation of the upcoming Wireless Mesh standard, 802.11s, on the
net80211 wireless stack. This work is based on the March 2009 D3.0 draft
standard. This standard is expected to become final next year.
This includes two main net80211 modules, ieee80211_mesh.c
which deals with peer link management, link metric calculation,
routing table control and mesh configuration and ieee80211_hwmp.c
which deals with the actually routing process on the mesh network.
HWMP is the mandatory routing protocol on by the mesh standard, but
others, such as RA-OLSR, can be implemented.
Authentication and encryption are not implemented.
There are several scripts under tools/tools/net80211/scripts that can be
used to test different mesh network topologies and they also teach you
how to setup a mesh vap (for the impatient: ifconfig wlan0 create
wlandev ... wlanmode mesh).
A new build option is available: IEEE80211_SUPPORT_MESH and it's enabled
by default on GENERIC kernels for i386, amd64, sparc64 and pc98.
Drivers that support mesh networks right now are: ath, ral and mwl.
More information at: http://wiki.freebsd.org/WifiMesh
Please note that this work is experimental. Also, please note that
bridging a mesh vap with another network interface is not yet supported.
Many thanks to the FreeBSD Foundation for sponsoring this project and to
Sam Leffler for his support.
Also, I would like to thank Gateworks Corporation for sending me a
Cambria board which was used during the development of this project.
Reviewed by: sam
Approved by: re (kensmith)
Obtained from: projects/mesh11s
2009-07-11 15:02:45 +00:00
|
|
|
.It Cm RANN
|
2010-07-31 21:09:49 +00:00
|
|
|
Send broadcast root announcement (RANN) frames.
|
Implementation of the upcoming Wireless Mesh standard, 802.11s, on the
net80211 wireless stack. This work is based on the March 2009 D3.0 draft
standard. This standard is expected to become final next year.
This includes two main net80211 modules, ieee80211_mesh.c
which deals with peer link management, link metric calculation,
routing table control and mesh configuration and ieee80211_hwmp.c
which deals with the actually routing process on the mesh network.
HWMP is the mandatory routing protocol on by the mesh standard, but
others, such as RA-OLSR, can be implemented.
Authentication and encryption are not implemented.
There are several scripts under tools/tools/net80211/scripts that can be
used to test different mesh network topologies and they also teach you
how to setup a mesh vap (for the impatient: ifconfig wlan0 create
wlandev ... wlanmode mesh).
A new build option is available: IEEE80211_SUPPORT_MESH and it's enabled
by default on GENERIC kernels for i386, amd64, sparc64 and pc98.
Drivers that support mesh networks right now are: ath, ral and mwl.
More information at: http://wiki.freebsd.org/WifiMesh
Please note that this work is experimental. Also, please note that
bridging a mesh vap with another network interface is not yet supported.
Many thanks to the FreeBSD Foundation for sponsoring this project and to
Sam Leffler for his support.
Also, I would like to thank Gateworks Corporation for sending me a
Cambria board which was used during the development of this project.
Reviewed by: sam
Approved by: re (kensmith)
Obtained from: projects/mesh11s
2009-07-11 15:02:45 +00:00
|
|
|
Nodes on the mesh without a path to this root mesh station with try to
|
|
|
|
discover a path to us.
|
|
|
|
.El
|
|
|
|
By default
|
2012-03-29 05:02:12 +00:00
|
|
|
.Cm hwmprootmode
|
Implementation of the upcoming Wireless Mesh standard, 802.11s, on the
net80211 wireless stack. This work is based on the March 2009 D3.0 draft
standard. This standard is expected to become final next year.
This includes two main net80211 modules, ieee80211_mesh.c
which deals with peer link management, link metric calculation,
routing table control and mesh configuration and ieee80211_hwmp.c
which deals with the actually routing process on the mesh network.
HWMP is the mandatory routing protocol on by the mesh standard, but
others, such as RA-OLSR, can be implemented.
Authentication and encryption are not implemented.
There are several scripts under tools/tools/net80211/scripts that can be
used to test different mesh network topologies and they also teach you
how to setup a mesh vap (for the impatient: ifconfig wlan0 create
wlandev ... wlanmode mesh).
A new build option is available: IEEE80211_SUPPORT_MESH and it's enabled
by default on GENERIC kernels for i386, amd64, sparc64 and pc98.
Drivers that support mesh networks right now are: ath, ral and mwl.
More information at: http://wiki.freebsd.org/WifiMesh
Please note that this work is experimental. Also, please note that
bridging a mesh vap with another network interface is not yet supported.
Many thanks to the FreeBSD Foundation for sponsoring this project and to
Sam Leffler for his support.
Also, I would like to thank Gateworks Corporation for sending me a
Cambria board which was used during the development of this project.
Reviewed by: sam
Approved by: re (kensmith)
Obtained from: projects/mesh11s
2009-07-11 15:02:45 +00:00
|
|
|
is set to
|
|
|
|
.Ar DISABLED .
|
|
|
|
.It Cm hwmpmaxhops Ar cnt
|
|
|
|
Set the maximum number of hops allowed in an HMWP path to
|
|
|
|
.Ar cnt .
|
|
|
|
The default setting for
|
|
|
|
.Cm hwmpmaxhops
|
|
|
|
is 31.
|
|
|
|
.El
|
|
|
|
.Pp
|
2005-08-02 19:13:13 +00:00
|
|
|
The following parameters are for compatibility with other systems:
|
2004-12-08 19:18:07 +00:00
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm nwid Ar ssid
|
|
|
|
Another name for the
|
|
|
|
.Cm ssid
|
|
|
|
parameter.
|
|
|
|
Included for
|
|
|
|
.Nx
|
|
|
|
compatibility.
|
2008-04-20 20:35:46 +00:00
|
|
|
.It Cm stationname Ar name
|
|
|
|
Set the name of this station.
|
|
|
|
The station name is not part of the IEEE 802.11
|
|
|
|
protocol though some interfaces support it.
|
|
|
|
As such it only
|
|
|
|
seems to be meaningful to identical or virtually identical equipment.
|
|
|
|
Setting the station name is identical in syntax to setting the SSID.
|
|
|
|
One can also use
|
|
|
|
.Cm station
|
|
|
|
for
|
2004-12-08 19:18:07 +00:00
|
|
|
.Bsx
|
|
|
|
compatibility.
|
2001-05-26 09:27:08 +00:00
|
|
|
.It Cm wep
|
|
|
|
Another way of saying
|
2001-07-05 12:37:08 +00:00
|
|
|
.Cm wepmode on .
|
|
|
|
Included for
|
|
|
|
.Bsx
|
|
|
|
compatibility.
|
|
|
|
.It Fl wep
|
|
|
|
Another way of saying
|
|
|
|
.Cm wepmode off .
|
|
|
|
Included for
|
|
|
|
.Bsx
|
|
|
|
compatibility.
|
2001-05-26 09:27:08 +00:00
|
|
|
.It Cm nwkey key
|
|
|
|
Another way of saying:
|
2001-07-05 12:37:08 +00:00
|
|
|
.Dq Li "wepmode on weptxkey 1 wepkey 1:key wepkey 2:- wepkey 3:- wepkey 4:-" .
|
|
|
|
Included for
|
|
|
|
.Nx
|
|
|
|
compatibility.
|
|
|
|
.It Cm nwkey Xo
|
|
|
|
.Sm off
|
|
|
|
.Ar n : k1 , k2 , k3 , k4
|
|
|
|
.Sm on
|
|
|
|
.Xc
|
2001-05-26 09:27:08 +00:00
|
|
|
Another way of saying
|
2001-07-05 12:37:08 +00:00
|
|
|
.Dq Li "wepmode on weptxkey n wepkey 1:k1 wepkey 2:k2 wepkey 3:k3 wepkey 4:k4" .
|
|
|
|
Included for
|
|
|
|
.Nx
|
|
|
|
compatibility.
|
|
|
|
.It Fl nwkey
|
2001-05-26 09:27:08 +00:00
|
|
|
Another way of saying
|
2001-07-05 12:37:08 +00:00
|
|
|
.Cm wepmode off .
|
|
|
|
Included for
|
|
|
|
.Nx
|
|
|
|
compatibility.
|
1994-05-26 06:35:07 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
2005-06-05 03:32:53 +00:00
|
|
|
The following parameters are specific to bridge interfaces:
|
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm addm Ar interface
|
|
|
|
Add the interface named by
|
|
|
|
.Ar interface
|
|
|
|
as a member of the bridge.
|
|
|
|
The interface is put into promiscuous mode
|
|
|
|
so that it can receive every packet sent on the network.
|
|
|
|
.It Cm deletem Ar interface
|
|
|
|
Remove the interface named by
|
|
|
|
.Ar interface
|
|
|
|
from the bridge.
|
|
|
|
Promiscuous mode is disabled on the interface when
|
|
|
|
it is removed from the bridge.
|
|
|
|
.It Cm maxaddr Ar size
|
|
|
|
Set the size of the bridge address cache to
|
|
|
|
.Ar size .
|
2012-02-29 21:11:02 +00:00
|
|
|
The default is 2000 entries.
|
2005-06-05 03:32:53 +00:00
|
|
|
.It Cm timeout Ar seconds
|
|
|
|
Set the timeout of address cache entries to
|
|
|
|
.Ar seconds
|
|
|
|
seconds.
|
|
|
|
If
|
|
|
|
.Ar seconds
|
|
|
|
is zero, then address cache entries will not be expired.
|
2012-02-29 21:11:02 +00:00
|
|
|
The default is 1200 seconds.
|
2005-08-14 03:28:08 +00:00
|
|
|
.It Cm addr
|
|
|
|
Display the addresses that have been learned by the bridge.
|
|
|
|
.It Cm static Ar interface-name Ar address
|
|
|
|
Add a static entry into the address cache pointing to
|
|
|
|
.Ar interface-name .
|
|
|
|
Static entries are never aged out of the cache or re-placed, even if the
|
|
|
|
address is seen on a different interface.
|
2005-06-05 03:32:53 +00:00
|
|
|
.It Cm deladdr Ar address
|
|
|
|
Delete
|
|
|
|
.Ar address
|
|
|
|
from the address cache.
|
|
|
|
.It Cm flush
|
|
|
|
Delete all dynamically-learned addresses from the address cache.
|
|
|
|
.It Cm flushall
|
|
|
|
Delete all addresses, including static addresses, from the address cache.
|
|
|
|
.It Cm discover Ar interface
|
|
|
|
Mark an interface as a
|
|
|
|
.Dq discovering
|
|
|
|
interface.
|
|
|
|
When the bridge has no address cache entry
|
|
|
|
(either dynamic or static)
|
|
|
|
for the destination address of a packet,
|
|
|
|
the bridge will forward the packet to all
|
|
|
|
member interfaces marked as
|
|
|
|
.Dq discovering .
|
|
|
|
This is the default for all interfaces added to a bridge.
|
|
|
|
.It Cm -discover Ar interface
|
|
|
|
Clear the
|
|
|
|
.Dq discovering
|
|
|
|
attribute on a member interface.
|
|
|
|
For packets without the
|
|
|
|
.Dq discovering
|
|
|
|
attribute, the only packets forwarded on the interface are broadcast
|
|
|
|
or multicast packets and packets for which the destination address
|
|
|
|
is known to be on the interface's segment.
|
|
|
|
.It Cm learn Ar interface
|
|
|
|
Mark an interface as a
|
|
|
|
.Dq learning
|
|
|
|
interface.
|
|
|
|
When a packet arrives on such an interface, the source
|
|
|
|
address of the packet is entered into the address cache as being a
|
|
|
|
destination address on the interface's segment.
|
|
|
|
This is the default for all interfaces added to a bridge.
|
|
|
|
.It Cm -learn Ar interface
|
|
|
|
Clear the
|
|
|
|
.Dq learning
|
|
|
|
attribute on a member interface.
|
2006-11-09 06:32:38 +00:00
|
|
|
.It Cm sticky Ar interface
|
|
|
|
Mark an interface as a
|
|
|
|
.Dq sticky
|
|
|
|
interface.
|
|
|
|
Dynamically learned address entries are treated at static once entered into
|
|
|
|
the cache.
|
|
|
|
Sticky entries are never aged out of the cache or replaced, even if the
|
|
|
|
address is seen on a different interface.
|
|
|
|
.It Cm -sticky Ar interface
|
|
|
|
Clear the
|
|
|
|
.Dq sticky
|
|
|
|
attribute on a member interface.
|
2007-08-01 00:33:52 +00:00
|
|
|
.It Cm private Ar interface
|
|
|
|
Mark an interface as a
|
|
|
|
.Dq private
|
|
|
|
interface.
|
|
|
|
A private interface does not forward any traffic to any other port that is also
|
|
|
|
a private interface.
|
|
|
|
.It Cm -private Ar interface
|
|
|
|
Clear the
|
|
|
|
.Dq private
|
|
|
|
attribute on a member interface.
|
2005-12-14 02:52:13 +00:00
|
|
|
.It Cm span Ar interface
|
|
|
|
Add the interface named by
|
|
|
|
.Ar interface
|
|
|
|
as a span port on the bridge.
|
|
|
|
Span ports transmit a copy of every frame received by the bridge.
|
|
|
|
This is most useful for snooping a bridged network passively on
|
|
|
|
another host connected to one of the span ports of the bridge.
|
|
|
|
.It Cm -span Ar interface
|
|
|
|
Delete the interface named by
|
|
|
|
.Ar interface
|
|
|
|
from the list of span ports of the bridge.
|
2005-06-05 03:32:53 +00:00
|
|
|
.It Cm stp Ar interface
|
|
|
|
Enable Spanning Tree protocol on
|
|
|
|
.Ar interface .
|
|
|
|
The
|
|
|
|
.Xr if_bridge 4
|
|
|
|
driver has support for the IEEE 802.1D Spanning Tree protocol (STP).
|
|
|
|
Spanning Tree is used to detect and remove loops in a network topology.
|
|
|
|
.It Cm -stp Ar interface
|
|
|
|
Disable Spanning Tree protocol on
|
|
|
|
.Ar interface .
|
|
|
|
This is the default for all interfaces added to a bridge.
|
2006-11-01 09:07:47 +00:00
|
|
|
.It Cm edge Ar interface
|
|
|
|
Set
|
|
|
|
.Ar interface
|
|
|
|
as an edge port.
|
|
|
|
An edge port connects directly to end stations cannot create bridging
|
|
|
|
loops in the network, this allows it to transition straight to forwarding.
|
|
|
|
.It Cm -edge Ar interface
|
|
|
|
Disable edge status on
|
|
|
|
.Ar interface .
|
|
|
|
.It Cm autoedge Ar interface
|
|
|
|
Allow
|
|
|
|
.Ar interface
|
|
|
|
to automatically detect edge status.
|
|
|
|
This is the default for all interfaces added to a bridge.
|
|
|
|
.It Cm -autoedge Ar interface
|
2007-01-20 00:56:49 +00:00
|
|
|
Disable automatic edge status on
|
2006-11-01 09:07:47 +00:00
|
|
|
.Ar interface .
|
2006-12-11 23:46:40 +00:00
|
|
|
.It Cm ptp Ar interface
|
2006-11-27 21:59:04 +00:00
|
|
|
Set the
|
|
|
|
.Ar interface
|
|
|
|
as a point to point link.
|
|
|
|
This is required for straight transitions to forwarding and
|
|
|
|
should be enabled on a direct link to another RSTP capable switch.
|
2006-12-11 23:46:40 +00:00
|
|
|
.It Cm -ptp Ar interface
|
2006-11-27 21:59:04 +00:00
|
|
|
Disable point to point link status on
|
|
|
|
.Ar interface .
|
|
|
|
This should be disabled for a half duplex link and for an interface
|
|
|
|
connected to a shared network segment,
|
|
|
|
like a hub or a wireless network.
|
2006-12-11 23:46:40 +00:00
|
|
|
.It Cm autoptp Ar interface
|
2006-11-27 21:59:04 +00:00
|
|
|
Automatically detect the point to point status on
|
|
|
|
.Ar interface
|
|
|
|
by checking the full duplex link status.
|
|
|
|
This is the default for interfaces added to the bridge.
|
2006-12-11 23:46:40 +00:00
|
|
|
.It Cm -autoptp Ar interface
|
2006-11-27 21:59:04 +00:00
|
|
|
Disable automatic point to point link detection on
|
|
|
|
.Ar interface .
|
2005-06-05 03:32:53 +00:00
|
|
|
.It Cm maxage Ar seconds
|
|
|
|
Set the time that a Spanning Tree protocol configuration is valid.
|
|
|
|
The default is 20 seconds.
|
2006-11-01 09:07:47 +00:00
|
|
|
The minimum is 6 seconds and the maximum is 40 seconds.
|
2005-06-05 03:32:53 +00:00
|
|
|
.It Cm fwddelay Ar seconds
|
|
|
|
Set the time that must pass before an interface begins forwarding
|
|
|
|
packets when Spanning Tree is enabled.
|
|
|
|
The default is 15 seconds.
|
2006-11-01 09:07:47 +00:00
|
|
|
The minimum is 4 seconds and the maximum is 30 seconds.
|
2005-06-05 03:32:53 +00:00
|
|
|
.It Cm hellotime Ar seconds
|
|
|
|
Set the time between broadcasting of Spanning Tree protocol
|
|
|
|
configuration messages.
|
2006-11-01 09:07:47 +00:00
|
|
|
The hello time may only be changed when operating in legacy stp mode.
|
2005-06-05 03:32:53 +00:00
|
|
|
The default is 2 seconds.
|
2006-11-01 09:07:47 +00:00
|
|
|
The minimum is 1 second and the maximum is 2 seconds.
|
2005-06-05 03:32:53 +00:00
|
|
|
.It Cm priority Ar value
|
|
|
|
Set the bridge priority for Spanning Tree.
|
|
|
|
The default is 32768.
|
2006-11-01 09:07:47 +00:00
|
|
|
The minimum is 0 and the maximum is 61440.
|
2007-03-29 21:30:26 +00:00
|
|
|
.It Cm proto Ar value
|
2006-11-01 09:07:47 +00:00
|
|
|
Set the Spanning Tree protocol.
|
|
|
|
The default is rstp.
|
|
|
|
The available options are stp and rstp.
|
2006-11-27 20:18:43 +00:00
|
|
|
.It Cm holdcnt Ar value
|
2006-11-01 09:07:47 +00:00
|
|
|
Set the transmit hold count for Spanning Tree.
|
|
|
|
This is the number of packets transmitted before being rate limited.
|
|
|
|
The default is 6.
|
|
|
|
The minimum is 1 and the maximum is 10.
|
2005-06-05 03:32:53 +00:00
|
|
|
.It Cm ifpriority Ar interface Ar value
|
|
|
|
Set the Spanning Tree priority of
|
|
|
|
.Ar interface
|
|
|
|
to
|
|
|
|
.Ar value .
|
|
|
|
The default is 128.
|
2006-11-01 09:07:47 +00:00
|
|
|
The minimum is 0 and the maximum is 240.
|
2005-06-05 03:32:53 +00:00
|
|
|
.It Cm ifpathcost Ar interface Ar value
|
|
|
|
Set the Spanning Tree path cost of
|
|
|
|
.Ar interface
|
|
|
|
to
|
|
|
|
.Ar value .
|
2006-11-01 09:07:47 +00:00
|
|
|
The default is calculated from the link speed.
|
|
|
|
To change a previously selected path cost back to automatic, set the
|
|
|
|
cost to 0.
|
|
|
|
The minimum is 1 and the maximum is 200000000.
|
2007-11-04 08:32:27 +00:00
|
|
|
.It Cm ifmaxaddr Ar interface Ar size
|
|
|
|
Set the maximum number of hosts allowed from an interface, packets with unknown
|
|
|
|
source addresses are dropped until an existing host cache entry expires or is
|
|
|
|
removed.
|
|
|
|
Set to 0 to disable.
|
2005-06-05 03:32:53 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
2007-04-17 00:35:11 +00:00
|
|
|
The following parameters are specific to lagg interfaces:
|
2007-04-10 00:35:31 +00:00
|
|
|
.Bl -tag -width indent
|
2007-04-17 00:35:11 +00:00
|
|
|
.It Cm laggport Ar interface
|
2007-04-10 00:35:31 +00:00
|
|
|
Add the interface named by
|
|
|
|
.Ar interface
|
2007-04-17 00:35:11 +00:00
|
|
|
as a port of the aggregation interface.
|
|
|
|
.It Cm -laggport Ar interface
|
2007-04-10 00:35:31 +00:00
|
|
|
Remove the interface named by
|
|
|
|
.Ar interface
|
2007-04-17 00:35:11 +00:00
|
|
|
from the aggregation interface.
|
|
|
|
.It Cm laggproto Ar proto
|
|
|
|
Set the aggregation protocol.
|
2014-10-01 21:37:32 +00:00
|
|
|
The default is
|
|
|
|
.Li failover .
|
|
|
|
The available options are
|
|
|
|
.Li failover ,
|
|
|
|
.Li lacp ,
|
|
|
|
.Li loadbalance ,
|
|
|
|
.Li roundrobin ,
|
|
|
|
.Li broadcast
|
|
|
|
and
|
|
|
|
.Li none .
|
2012-03-06 22:58:13 +00:00
|
|
|
.It Cm lagghash Ar option Ns Oo , Ns Ar option Oc
|
|
|
|
Set the packet layers to hash for aggregation protocols which load balance.
|
|
|
|
The default is
|
|
|
|
.Dq l2,l3,l4 .
|
|
|
|
The options can be combined using commas.
|
|
|
|
.Pp
|
|
|
|
.Bl -tag -width ".Cm l2" -compact
|
|
|
|
.It Cm l2
|
|
|
|
src/dst mac address and optional vlan number.
|
|
|
|
.It Cm l3
|
|
|
|
src/dst address for IPv4 or IPv6.
|
|
|
|
.It Cm l4
|
2012-03-07 06:25:17 +00:00
|
|
|
src/dst port for TCP/UDP/SCTP.
|
2012-03-06 22:58:13 +00:00
|
|
|
.El
|
2018-12-22 11:38:54 +00:00
|
|
|
.It Cm -use_flowid
|
2014-10-01 21:37:32 +00:00
|
|
|
Enable local hash computation for RSS hash on the interface.
|
|
|
|
The
|
|
|
|
.Li loadbalance
|
|
|
|
and
|
|
|
|
.Li lacp
|
|
|
|
modes will use the RSS hash from the network card if available
|
|
|
|
to avoid computing one, this may give poor traffic distribution
|
|
|
|
if the hash is invalid or uses less of the protocol header information.
|
2018-12-22 11:38:54 +00:00
|
|
|
.Cm -use_flowid
|
2014-10-01 21:37:32 +00:00
|
|
|
disables use of RSS hash from the network card.
|
|
|
|
The default value can be set via the
|
|
|
|
.Va net.link.lagg.default_use_flowid
|
|
|
|
.Xr sysctl 8
|
|
|
|
variable.
|
|
|
|
.Li 0
|
|
|
|
means
|
|
|
|
.Dq disabled
|
|
|
|
and
|
|
|
|
.Li 1
|
|
|
|
means
|
|
|
|
.Dq enabled .
|
2018-12-22 11:38:54 +00:00
|
|
|
.It Cm use_flowid
|
|
|
|
Use the RSS hash from the network card if available.
|
2014-10-01 21:37:32 +00:00
|
|
|
.It Cm flowid_shift Ar number
|
|
|
|
Set a shift parameter for RSS local hash computation.
|
|
|
|
Hash is calculated by using flowid bits in a packet header mbuf
|
|
|
|
which are shifted by the number of this parameter.
|
2019-05-03 14:43:21 +00:00
|
|
|
.It Cm use_numa
|
|
|
|
Enable selection of egress ports based on the native
|
|
|
|
.Xr NUMA 4
|
|
|
|
domain for the packets being transmitted.
|
|
|
|
This is currently only implemented for lacp mode.
|
|
|
|
This works only on
|
|
|
|
.Xr NUMA 4
|
|
|
|
hardware, running a kernel compiled with the
|
|
|
|
.Xr NUMA 4
|
|
|
|
option, and when interfaces from multiple
|
|
|
|
.Xr NUMA 4
|
|
|
|
domains are ports of the aggregation interface.
|
|
|
|
.It Cm -use_numa
|
|
|
|
Disable selection of egress ports based on the native
|
|
|
|
.Xr NUMA 4
|
|
|
|
domain for the packets being transmitted.
|
2015-08-12 20:21:04 +00:00
|
|
|
.It Cm lacp_fast_timeout
|
|
|
|
Enable lacp fast-timeout on the interface.
|
|
|
|
.It Cm -lacp_fast_timeout
|
|
|
|
Disable lacp fast-timeout on the interface.
|
2015-11-06 15:33:27 +00:00
|
|
|
.It Cm lacp_strict
|
|
|
|
Enable lacp strict compliance on the interface.
|
|
|
|
The default value can be set via the
|
|
|
|
.Va net.link.lagg.lacp.default_strict_mode
|
|
|
|
.Xr sysctl 8
|
|
|
|
variable.
|
|
|
|
.Li 0
|
|
|
|
means
|
|
|
|
.Dq disabled
|
|
|
|
and
|
|
|
|
.Li 1
|
|
|
|
means
|
|
|
|
.Dq enabled .
|
|
|
|
.It Cm -lacp_strict
|
|
|
|
Disable lacp strict compliance on the interface.
|
2019-12-22 21:56:47 +00:00
|
|
|
.It Cm rr_limit Ar number
|
|
|
|
Configure a stride for an interface in round-robin mode.
|
|
|
|
The default stride is 1.
|
2007-04-10 00:35:31 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
2017-04-29 15:35:30 +00:00
|
|
|
The following parameters apply to IP tunnel interfaces,
|
2005-09-22 11:49:52 +00:00
|
|
|
.Xr gif 4 :
|
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm tunnel Ar src_addr dest_addr
|
|
|
|
Configure the physical source and destination address for IP tunnel
|
|
|
|
interfaces.
|
|
|
|
The arguments
|
|
|
|
.Ar src_addr
|
|
|
|
and
|
|
|
|
.Ar dest_addr
|
|
|
|
are interpreted as the outer source/destination for the encapsulating
|
|
|
|
IPv4/IPv6 header.
|
2005-09-29 23:53:29 +00:00
|
|
|
.It Fl tunnel
|
2005-09-22 11:49:52 +00:00
|
|
|
Unconfigure the physical source and destination address for IP tunnel
|
|
|
|
interfaces previously configured with
|
|
|
|
.Cm tunnel .
|
2005-09-29 23:53:29 +00:00
|
|
|
.It Cm deletetunnel
|
|
|
|
Another name for the
|
|
|
|
.Fl tunnel
|
|
|
|
parameter.
|
2009-09-12 22:17:13 +00:00
|
|
|
.It Cm accept_rev_ethip_ver
|
2010-07-31 21:09:49 +00:00
|
|
|
Set a flag to accept both correct EtherIP packets and ones
|
2014-06-06 00:22:19 +00:00
|
|
|
with reversed version field.
|
|
|
|
Enabled by default.
|
2009-09-12 22:17:13 +00:00
|
|
|
This is for backward compatibility with
|
|
|
|
.Fx 6.1 ,
|
|
|
|
6.2, 6.3, 7.0, and 7.1.
|
|
|
|
.It Cm -accept_rev_ethip_ver
|
|
|
|
Clear a flag
|
|
|
|
.Cm accept_rev_ethip_ver .
|
2015-05-15 12:19:45 +00:00
|
|
|
.It Cm ignore_source
|
|
|
|
Set a flag to accept encapsulated packets destined to this host
|
|
|
|
independently from source address.
|
|
|
|
This may be useful for hosts, that receive encapsulated packets
|
|
|
|
from the load balancers.
|
|
|
|
.It Cm -ignore_source
|
|
|
|
Clear a flag
|
|
|
|
.Cm ignore_source .
|
2009-09-12 22:17:13 +00:00
|
|
|
.It Cm send_rev_ethip_ver
|
|
|
|
Set a flag to send EtherIP packets with reversed version
|
2014-06-06 00:22:19 +00:00
|
|
|
field intentionally.
|
|
|
|
Disabled by default.
|
2009-09-12 22:17:13 +00:00
|
|
|
This is for backward compatibility with
|
|
|
|
.Fx 6.1 ,
|
|
|
|
6.2, 6.3, 7.0, and 7.1.
|
|
|
|
.It Cm -send_rev_ethip_ver
|
|
|
|
Clear a flag
|
|
|
|
.Cm send_rev_ethip_ver .
|
2005-09-22 11:49:52 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
2017-04-29 15:35:30 +00:00
|
|
|
The following parameters apply to GRE tunnel interfaces,
|
2008-06-20 17:26:34 +00:00
|
|
|
.Xr gre 4 :
|
|
|
|
.Bl -tag -width indent
|
2017-04-29 15:35:30 +00:00
|
|
|
.It Cm tunnel Ar src_addr dest_addr
|
|
|
|
Configure the physical source and destination address for GRE tunnel
|
|
|
|
interfaces.
|
|
|
|
The arguments
|
|
|
|
.Ar src_addr
|
|
|
|
and
|
|
|
|
.Ar dest_addr
|
|
|
|
are interpreted as the outer source/destination for the encapsulating
|
|
|
|
IPv4/IPv6 header.
|
|
|
|
.It Fl tunnel
|
|
|
|
Unconfigure the physical source and destination address for GRE tunnel
|
|
|
|
interfaces previously configured with
|
|
|
|
.Cm tunnel .
|
|
|
|
.It Cm deletetunnel
|
|
|
|
Another name for the
|
|
|
|
.Fl tunnel
|
|
|
|
parameter.
|
2008-06-20 17:26:34 +00:00
|
|
|
.It Cm grekey Ar key
|
|
|
|
Configure the GRE key to be used for outgoing packets.
|
|
|
|
Note that
|
|
|
|
.Xr gre 4 will always accept GRE packets with invalid or absent keys.
|
|
|
|
This command will result in a four byte MTU reduction on the interface.
|
|
|
|
.El
|
|
|
|
.Pp
|
2005-09-22 11:49:52 +00:00
|
|
|
The following parameters are specific to
|
2005-12-16 11:38:18 +00:00
|
|
|
.Xr pfsync 4
|
|
|
|
interfaces:
|
|
|
|
.Bl -tag -width indent
|
2012-04-03 18:11:30 +00:00
|
|
|
.It Cm syncdev Ar iface
|
|
|
|
Use the specified interface
|
|
|
|
to send and receive pfsync state synchronisation messages.
|
|
|
|
.It Fl syncdev
|
|
|
|
Stop sending pfsync state synchronisation messages over the network.
|
|
|
|
.It Cm syncpeer Ar peer_address
|
|
|
|
Make the pfsync link point-to-point rather than using
|
|
|
|
multicast to broadcast the state synchronisation messages.
|
|
|
|
The peer_address is the IP address of the other host taking part in
|
|
|
|
the pfsync cluster.
|
|
|
|
.It Fl syncpeer
|
|
|
|
Broadcast the packets using multicast.
|
2005-12-16 11:38:18 +00:00
|
|
|
.It Cm maxupd Ar n
|
|
|
|
Set the maximum number of updates for a single state which
|
|
|
|
can be collapsed into one.
|
2006-09-18 11:55:10 +00:00
|
|
|
This is an 8-bit number; the default value is 128.
|
2012-04-03 18:11:30 +00:00
|
|
|
.It Cm defer
|
2012-04-07 09:11:07 +00:00
|
|
|
Defer transmission of the first packet in a state until a peer has
|
2012-04-03 18:11:30 +00:00
|
|
|
acknowledged that the associated state has been inserted.
|
|
|
|
.It Fl defer
|
|
|
|
Do not defer the first packet in a state.
|
|
|
|
This is the default.
|
2005-12-16 11:38:18 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
The following parameters are specific to
|
2005-09-22 11:49:52 +00:00
|
|
|
.Xr vlan 4
|
|
|
|
interfaces:
|
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm vlan Ar vlan_tag
|
|
|
|
Set the VLAN tag value to
|
|
|
|
.Ar vlan_tag .
|
2012-01-04 21:04:57 +00:00
|
|
|
This value is a 12-bit VLAN Identifier (VID) which is used to create an 802.1Q
|
2005-09-22 11:49:52 +00:00
|
|
|
VLAN header for packets sent from the
|
|
|
|
.Xr vlan 4
|
|
|
|
interface.
|
|
|
|
Note that
|
|
|
|
.Cm vlan
|
|
|
|
and
|
|
|
|
.Cm vlandev
|
|
|
|
must both be set at the same time.
|
Add support to priority code point (PCP) that is an 3-bit field
which refers to IEEE 802.1p class of service and maps to the frame
priority level.
Values in order of priority are: 1 (Background (lowest)),
0 (Best effort (default)), 2 (Excellent effort),
3 (Critical applications), 4 (Video, < 100ms latency),
5 (Video, < 10ms latency), 6 (Internetwork control) and
7 (Network control (highest)).
Example of usage:
root# ifconfig em0.1 create
root# ifconfig em0.1 vlanpcp 3
Note:
The review D801 includes the pf(4) part, but as discussed with kristof,
we won't commit the pf(4) bits for now.
The credits of the original code is from rwatson.
Differential Revision: https://reviews.freebsd.org/D801
Reviewed by: gnn, adrian, loos
Discussed with: rwatson, glebius, kristof
Tested by: many including Matthew Grooms <mgrooms__shrew.net>
Obtained from: pfSense
Relnotes: Yes
2016-06-06 09:51:58 +00:00
|
|
|
.It Cm vlanpcp Ar priority_code_point
|
2016-09-16 04:22:21 +00:00
|
|
|
Priority code point
|
Add support to priority code point (PCP) that is an 3-bit field
which refers to IEEE 802.1p class of service and maps to the frame
priority level.
Values in order of priority are: 1 (Background (lowest)),
0 (Best effort (default)), 2 (Excellent effort),
3 (Critical applications), 4 (Video, < 100ms latency),
5 (Video, < 10ms latency), 6 (Internetwork control) and
7 (Network control (highest)).
Example of usage:
root# ifconfig em0.1 create
root# ifconfig em0.1 vlanpcp 3
Note:
The review D801 includes the pf(4) part, but as discussed with kristof,
we won't commit the pf(4) bits for now.
The credits of the original code is from rwatson.
Differential Revision: https://reviews.freebsd.org/D801
Reviewed by: gnn, adrian, loos
Discussed with: rwatson, glebius, kristof
Tested by: many including Matthew Grooms <mgrooms__shrew.net>
Obtained from: pfSense
Relnotes: Yes
2016-06-06 09:51:58 +00:00
|
|
|
.Pq Dv PCP
|
|
|
|
is an 3-bit field which refers to the IEEE 802.1p
|
|
|
|
class of service and maps to the frame priority level.
|
|
|
|
.Pp
|
|
|
|
Values in order of priority are:
|
2016-09-16 04:22:21 +00:00
|
|
|
.Cm 1
|
Add support to priority code point (PCP) that is an 3-bit field
which refers to IEEE 802.1p class of service and maps to the frame
priority level.
Values in order of priority are: 1 (Background (lowest)),
0 (Best effort (default)), 2 (Excellent effort),
3 (Critical applications), 4 (Video, < 100ms latency),
5 (Video, < 10ms latency), 6 (Internetwork control) and
7 (Network control (highest)).
Example of usage:
root# ifconfig em0.1 create
root# ifconfig em0.1 vlanpcp 3
Note:
The review D801 includes the pf(4) part, but as discussed with kristof,
we won't commit the pf(4) bits for now.
The credits of the original code is from rwatson.
Differential Revision: https://reviews.freebsd.org/D801
Reviewed by: gnn, adrian, loos
Discussed with: rwatson, glebius, kristof
Tested by: many including Matthew Grooms <mgrooms__shrew.net>
Obtained from: pfSense
Relnotes: Yes
2016-06-06 09:51:58 +00:00
|
|
|
.Pq Dv Background (lowest) ,
|
|
|
|
.Cm 0
|
|
|
|
.Pq Dv Best effort (default) ,
|
|
|
|
.Cm 2
|
|
|
|
.Pq Dv Excellent effort ,
|
|
|
|
.Cm 3
|
|
|
|
.Pq Dv Critical applications ,
|
|
|
|
.Cm 4
|
|
|
|
.Pq Dv Video, < 100ms latency ,
|
|
|
|
.Cm 5
|
|
|
|
.Pq Dv Video, < 10ms latency ,
|
|
|
|
.Cm 6
|
|
|
|
.Pq Dv Internetwork control ,
|
|
|
|
.Cm 7
|
|
|
|
.Pq Dv Network control (highest) .
|
2005-09-22 11:49:52 +00:00
|
|
|
.It Cm vlandev Ar iface
|
|
|
|
Associate the physical interface
|
|
|
|
.Ar iface
|
|
|
|
with a
|
|
|
|
.Xr vlan 4
|
|
|
|
interface.
|
|
|
|
Packets transmitted through the
|
|
|
|
.Xr vlan 4
|
|
|
|
interface will be
|
|
|
|
diverted to the specified physical interface
|
|
|
|
.Ar iface
|
|
|
|
with 802.1Q VLAN encapsulation.
|
|
|
|
Packets with 802.1Q encapsulation received
|
2012-01-04 21:04:57 +00:00
|
|
|
by the parent interface with the correct VLAN Identifier will be diverted to
|
2005-09-22 11:49:52 +00:00
|
|
|
the associated
|
|
|
|
.Xr vlan 4
|
|
|
|
pseudo-interface.
|
|
|
|
The
|
|
|
|
.Xr vlan 4
|
|
|
|
interface is assigned a
|
2014-06-06 00:22:19 +00:00
|
|
|
copy of the parent interface's flags and the parent's Ethernet address.
|
2005-09-22 11:49:52 +00:00
|
|
|
The
|
|
|
|
.Cm vlandev
|
|
|
|
and
|
|
|
|
.Cm vlan
|
|
|
|
must both be set at the same time.
|
|
|
|
If the
|
|
|
|
.Xr vlan 4
|
|
|
|
interface already has
|
|
|
|
a physical interface associated with it, this command will fail.
|
|
|
|
To
|
|
|
|
change the association to another physical interface, the existing
|
|
|
|
association must be cleared first.
|
|
|
|
.Pp
|
|
|
|
Note: if the hardware tagging capability
|
|
|
|
is set on the parent interface, the
|
|
|
|
.Xr vlan 4
|
|
|
|
pseudo
|
|
|
|
interface's behavior changes:
|
|
|
|
the
|
|
|
|
.Xr vlan 4
|
|
|
|
interface recognizes that the
|
|
|
|
parent interface supports insertion and extraction of VLAN tags on its
|
|
|
|
own (usually in firmware) and that it should pass packets to and from
|
|
|
|
the parent unaltered.
|
2005-09-29 23:38:24 +00:00
|
|
|
.It Fl vlandev Op Ar iface
|
2005-09-22 11:49:52 +00:00
|
|
|
If the driver is a
|
|
|
|
.Xr vlan 4
|
2005-09-29 23:38:24 +00:00
|
|
|
pseudo device, disassociate the parent interface from it.
|
2005-09-22 11:49:52 +00:00
|
|
|
This breaks the link between the
|
|
|
|
.Xr vlan 4
|
|
|
|
interface and its parent,
|
2012-01-04 21:04:57 +00:00
|
|
|
clears its VLAN Identifier, flags and its link address and shuts the interface
|
|
|
|
down.
|
2005-09-29 23:38:24 +00:00
|
|
|
The
|
|
|
|
.Ar iface
|
|
|
|
argument is useless and hence deprecated.
|
2005-09-22 11:49:52 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
A major overhaul of the CARP implementation. The ip_carp.c was started
from scratch, copying needed functionality from the old implemenation
on demand, with a thorough review of all code. The main change is that
interface layer has been removed from the CARP. Now redundant addresses
are configured exactly on the interfaces, they run on.
The CARP configuration itself is, as before, configured and read via
SIOCSVH/SIOCGVH ioctls. A new prefix created with SIOCAIFADDR or
SIOCAIFADDR_IN6 may now be configured to a particular virtual host id,
which makes the prefix redundant.
ifconfig(8) semantics has been changed too: now one doesn't need
to clone carpXX interface, he/she should directly configure a vhid
on a Ethernet interface.
To supply vhid data from the kernel to an application the getifaddrs(8)
function had been changed to pass ifam_data with each address. [1]
The new implementation definitely closes all PRs related to carp(4)
being an interface, and may close several others. It also allows
to run a single redundant IP per interface.
Big thanks to Bjoern Zeeb for his help with inet6 part of patch, for
idea on using ifam_data and for several rounds of reviewing!
PR: kern/117000, kern/126945, kern/126714, kern/120130, kern/117448
Reviewed by: bz
Submitted by: bz [1]
2011-12-16 12:16:56 +00:00
|
|
|
The following parameters are used to configure
|
2014-10-20 14:42:42 +00:00
|
|
|
.Xr vxlan 4
|
|
|
|
interfaces.
|
|
|
|
.Bl -tag -width indent
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Cm vxlanid Ar identifier
|
2014-10-20 14:42:42 +00:00
|
|
|
This value is a 24-bit VXLAN Network Identifier (VNI) that identifies the
|
|
|
|
virtual network segment membership of the interface.
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Cm vxlanlocal Ar address
|
2014-10-20 14:42:42 +00:00
|
|
|
The source address used in the encapsulating IPv4/IPv6 header.
|
|
|
|
The address should already be assigned to an existing interface.
|
|
|
|
When the interface is configured in unicast mode, the listening socket
|
|
|
|
is bound to this address.
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Cm vxlanremote Ar address
|
2014-10-20 14:42:42 +00:00
|
|
|
The interface can be configured in a unicast, or point-to-point, mode
|
|
|
|
to create a tunnel between two hosts.
|
|
|
|
This is the IP address of the remote end of the tunnel.
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Cm vxlangroup Ar address
|
2014-10-20 14:42:42 +00:00
|
|
|
The interface can be configured in a multicast mode
|
|
|
|
to create a virtual network of hosts.
|
|
|
|
This is the IP multicast group address the interface will join.
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Cm vxlanlocalport Ar port
|
2014-10-20 14:42:42 +00:00
|
|
|
The port number the interface will listen on.
|
|
|
|
The default port number is 4789.
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Cm vxlanremoteport Ar port
|
2014-10-20 14:42:42 +00:00
|
|
|
The destination port number used in the encapsulating IPv4/IPv6 header.
|
|
|
|
The remote host should be listening on this port.
|
|
|
|
The default port number is 4789.
|
|
|
|
Note some other implementations, such as Linux,
|
|
|
|
do not default to the IANA assigned port,
|
|
|
|
but instead listen on port 8472.
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Cm vxlanportrange Ar low high
|
2014-10-20 14:42:42 +00:00
|
|
|
The range of source ports used in the encapsulating IPv4/IPv6 header.
|
|
|
|
The port selected within the range is based on a hash of the inner frame.
|
|
|
|
A range is useful to provide entropy within the outer IP header
|
|
|
|
for more effective load balancing.
|
|
|
|
The default range is between the
|
|
|
|
.Xr sysctl 8
|
|
|
|
variables
|
|
|
|
.Va net.inet.ip.portrange.first
|
|
|
|
and
|
|
|
|
.Va net.inet.ip.portrange.last
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Cm vxlantimeout Ar timeout
|
2014-10-20 14:42:42 +00:00
|
|
|
The maximum time, in seconds, before an entry in the forwarding table
|
|
|
|
is pruned.
|
|
|
|
The default is 1200 seconds (20 minutes).
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Cm vxlanmaxaddr Ar max
|
2014-10-20 14:42:42 +00:00
|
|
|
The maximum number of entries in the forwarding table.
|
|
|
|
The default is 2000.
|
|
|
|
.It Cm vxlandev Ar dev
|
|
|
|
When the interface is configured in multicast mode, the
|
|
|
|
.Cm dev
|
|
|
|
interface is used to transmit IP multicast packets.
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Cm vxlanttl Ar ttl
|
2014-10-20 14:42:42 +00:00
|
|
|
The TTL used in the encapsulating IPv4/IPv6 header.
|
|
|
|
The default is 64.
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Cm vxlanlearn
|
2014-10-20 14:42:42 +00:00
|
|
|
The source IP address and inner source Ethernet MAC address of
|
|
|
|
received packets are used to dynamically populate the forwarding table.
|
|
|
|
When in multicast mode, an entry in the forwarding table allows the
|
|
|
|
interface to send the frame directly to the remote host instead of
|
|
|
|
broadcasting the frame to the multicast group.
|
|
|
|
This is the default.
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Fl vxlanlearn
|
2016-09-16 04:22:21 +00:00
|
|
|
The forwarding table is not populated by received packets.
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Cm vxlanflush
|
2014-10-20 14:42:42 +00:00
|
|
|
Delete all dynamically-learned addresses from the forwarding table.
|
2014-12-17 05:36:34 +00:00
|
|
|
.It Cm vxlanflushall
|
2014-10-20 14:42:42 +00:00
|
|
|
Delete all addresses, including static addresses, from the forwarding table.
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
The following parameters are used to configure
|
2006-02-03 14:41:41 +00:00
|
|
|
.Xr carp 4
|
A major overhaul of the CARP implementation. The ip_carp.c was started
from scratch, copying needed functionality from the old implemenation
on demand, with a thorough review of all code. The main change is that
interface layer has been removed from the CARP. Now redundant addresses
are configured exactly on the interfaces, they run on.
The CARP configuration itself is, as before, configured and read via
SIOCSVH/SIOCGVH ioctls. A new prefix created with SIOCAIFADDR or
SIOCAIFADDR_IN6 may now be configured to a particular virtual host id,
which makes the prefix redundant.
ifconfig(8) semantics has been changed too: now one doesn't need
to clone carpXX interface, he/she should directly configure a vhid
on a Ethernet interface.
To supply vhid data from the kernel to an application the getifaddrs(8)
function had been changed to pass ifam_data with each address. [1]
The new implementation definitely closes all PRs related to carp(4)
being an interface, and may close several others. It also allows
to run a single redundant IP per interface.
Big thanks to Bjoern Zeeb for his help with inet6 part of patch, for
idea on using ifam_data and for several rounds of reviewing!
PR: kern/117000, kern/126945, kern/126714, kern/120130, kern/117448
Reviewed by: bz
Submitted by: bz [1]
2011-12-16 12:16:56 +00:00
|
|
|
protocol on an interface:
|
2006-02-03 14:41:41 +00:00
|
|
|
.Bl -tag -width indent
|
A major overhaul of the CARP implementation. The ip_carp.c was started
from scratch, copying needed functionality from the old implemenation
on demand, with a thorough review of all code. The main change is that
interface layer has been removed from the CARP. Now redundant addresses
are configured exactly on the interfaces, they run on.
The CARP configuration itself is, as before, configured and read via
SIOCSVH/SIOCGVH ioctls. A new prefix created with SIOCAIFADDR or
SIOCAIFADDR_IN6 may now be configured to a particular virtual host id,
which makes the prefix redundant.
ifconfig(8) semantics has been changed too: now one doesn't need
to clone carpXX interface, he/she should directly configure a vhid
on a Ethernet interface.
To supply vhid data from the kernel to an application the getifaddrs(8)
function had been changed to pass ifam_data with each address. [1]
The new implementation definitely closes all PRs related to carp(4)
being an interface, and may close several others. It also allows
to run a single redundant IP per interface.
Big thanks to Bjoern Zeeb for his help with inet6 part of patch, for
idea on using ifam_data and for several rounds of reviewing!
PR: kern/117000, kern/126945, kern/126714, kern/120130, kern/117448
Reviewed by: bz
Submitted by: bz [1]
2011-12-16 12:16:56 +00:00
|
|
|
.It Cm vhid Ar n
|
|
|
|
Set the virtual host ID.
|
|
|
|
This is a required setting to initiate
|
|
|
|
.Xr carp 4 .
|
2012-11-07 19:26:32 +00:00
|
|
|
If the virtual host ID does not exist yet, it is created and attached to the
|
A major overhaul of the CARP implementation. The ip_carp.c was started
from scratch, copying needed functionality from the old implemenation
on demand, with a thorough review of all code. The main change is that
interface layer has been removed from the CARP. Now redundant addresses
are configured exactly on the interfaces, they run on.
The CARP configuration itself is, as before, configured and read via
SIOCSVH/SIOCGVH ioctls. A new prefix created with SIOCAIFADDR or
SIOCAIFADDR_IN6 may now be configured to a particular virtual host id,
which makes the prefix redundant.
ifconfig(8) semantics has been changed too: now one doesn't need
to clone carpXX interface, he/she should directly configure a vhid
on a Ethernet interface.
To supply vhid data from the kernel to an application the getifaddrs(8)
function had been changed to pass ifam_data with each address. [1]
The new implementation definitely closes all PRs related to carp(4)
being an interface, and may close several others. It also allows
to run a single redundant IP per interface.
Big thanks to Bjoern Zeeb for his help with inet6 part of patch, for
idea on using ifam_data and for several rounds of reviewing!
PR: kern/117000, kern/126945, kern/126714, kern/120130, kern/117448
Reviewed by: bz
Submitted by: bz [1]
2011-12-16 12:16:56 +00:00
|
|
|
interface, otherwise configuration of an existing vhid is adjusted.
|
|
|
|
If the
|
|
|
|
.Cm vhid
|
|
|
|
keyword is supplied along with an
|
|
|
|
.Dq inet6
|
|
|
|
or
|
|
|
|
.Dq inet
|
|
|
|
address, then this address is configured to be run under control of the
|
|
|
|
specified vhid.
|
|
|
|
Whenever a last address that refers to a particular vhid is removed from an
|
|
|
|
interface, the vhid is automatically removed from interface and destroyed.
|
|
|
|
Any other configuration parameters for the
|
|
|
|
.Xr carp 4
|
|
|
|
protocol should be supplied along with the
|
|
|
|
.Cm vhid
|
|
|
|
keyword.
|
|
|
|
Acceptable values for vhid are 1 to 255.
|
2006-02-03 14:41:41 +00:00
|
|
|
.It Cm advbase Ar seconds
|
|
|
|
Specifies the base of the advertisement interval in seconds.
|
|
|
|
The acceptable values are 1 to 255.
|
|
|
|
The default value is 1.
|
|
|
|
.It Cm advskew Ar interval
|
|
|
|
Specifies the skew to add to the base advertisement interval to
|
|
|
|
make one host advertise slower than another host.
|
|
|
|
It is specified in 1/256 of seconds.
|
|
|
|
The acceptable values are 1 to 254.
|
|
|
|
The default value is 0.
|
|
|
|
.It Cm pass Ar phrase
|
|
|
|
Set the authentication key to
|
|
|
|
.Ar phrase .
|
A major overhaul of the CARP implementation. The ip_carp.c was started
from scratch, copying needed functionality from the old implemenation
on demand, with a thorough review of all code. The main change is that
interface layer has been removed from the CARP. Now redundant addresses
are configured exactly on the interfaces, they run on.
The CARP configuration itself is, as before, configured and read via
SIOCSVH/SIOCGVH ioctls. A new prefix created with SIOCAIFADDR or
SIOCAIFADDR_IN6 may now be configured to a particular virtual host id,
which makes the prefix redundant.
ifconfig(8) semantics has been changed too: now one doesn't need
to clone carpXX interface, he/she should directly configure a vhid
on a Ethernet interface.
To supply vhid data from the kernel to an application the getifaddrs(8)
function had been changed to pass ifam_data with each address. [1]
The new implementation definitely closes all PRs related to carp(4)
being an interface, and may close several others. It also allows
to run a single redundant IP per interface.
Big thanks to Bjoern Zeeb for his help with inet6 part of patch, for
idea on using ifam_data and for several rounds of reviewing!
PR: kern/117000, kern/126945, kern/126714, kern/120130, kern/117448
Reviewed by: bz
Submitted by: bz [1]
2011-12-16 12:16:56 +00:00
|
|
|
.It Cm state Ar MASTER|BACKUP
|
|
|
|
Forcibly change state of a given vhid.
|
2006-02-03 14:41:41 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
2002-07-06 19:34:18 +00:00
|
|
|
The
|
|
|
|
.Nm
|
|
|
|
utility displays the current configuration for a network interface
|
1994-05-26 06:35:07 +00:00
|
|
|
when no optional parameters are supplied.
|
|
|
|
If a protocol family is specified,
|
1998-07-06 06:53:43 +00:00
|
|
|
.Nm
|
|
|
|
will report only the details specific to that protocol family.
|
1997-05-03 23:03:56 +00:00
|
|
|
.Pp
|
2001-05-29 09:13:44 +00:00
|
|
|
If the
|
|
|
|
.Fl m
|
2001-07-05 12:37:08 +00:00
|
|
|
flag is passed before an interface name,
|
|
|
|
.Nm
|
2004-04-11 13:44:57 +00:00
|
|
|
will display the capability list and all
|
2001-05-29 09:13:44 +00:00
|
|
|
of the supported media for the specified interface.
|
1999-12-07 17:39:16 +00:00
|
|
|
If
|
|
|
|
.Fl L
|
2001-01-20 21:37:37 +00:00
|
|
|
flag is supplied, address lifetime is displayed for IPv6 addresses,
|
1999-12-07 17:39:16 +00:00
|
|
|
as time offset string.
|
|
|
|
.Pp
|
1997-05-03 23:03:56 +00:00
|
|
|
Optionally, the
|
|
|
|
.Fl a
|
2001-07-05 12:37:08 +00:00
|
|
|
flag may be used instead of an interface name.
|
|
|
|
This flag instructs
|
1997-05-03 23:03:56 +00:00
|
|
|
.Nm
|
|
|
|
to display information about all interfaces in the system.
|
1998-07-06 06:53:43 +00:00
|
|
|
The
|
1997-05-03 23:03:56 +00:00
|
|
|
.Fl d
|
2020-06-04 14:44:44 +00:00
|
|
|
flag limits this to interfaces that are down,
|
1997-05-03 23:03:56 +00:00
|
|
|
.Fl u
|
2020-06-04 14:44:44 +00:00
|
|
|
limits this to interfaces that are up,
|
|
|
|
.Fl g
|
|
|
|
limits this to members of the specified group of interfaces, and
|
|
|
|
.Fl G
|
|
|
|
excludes members of the specified group from the list.
|
|
|
|
Both
|
|
|
|
.Fl g
|
|
|
|
and
|
|
|
|
.Fl G
|
|
|
|
flags may be specified to apply both conditions.
|
|
|
|
Only one option
|
|
|
|
.Fl g
|
|
|
|
should be specified as later override previous ones
|
|
|
|
(same for
|
|
|
|
.Fl G ) .
|
|
|
|
.Sy groupname
|
|
|
|
may contain shell patterns in which case it should be quoted.
|
2000-07-19 17:24:53 +00:00
|
|
|
When no arguments are given,
|
|
|
|
.Fl a
|
|
|
|
is implied.
|
1997-05-03 23:03:56 +00:00
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Fl l
|
|
|
|
flag may be used to list all available interfaces on the system, with
|
2001-07-05 12:37:08 +00:00
|
|
|
no other additional information.
|
2014-05-27 20:45:15 +00:00
|
|
|
If an
|
|
|
|
.Ar address_family
|
|
|
|
is specified, only interfaces of that type will be listed.
|
|
|
|
.Fl l Dq ether
|
2014-06-06 00:22:19 +00:00
|
|
|
will list only Ethernet adapters, excluding the loopback interface.
|
2001-07-05 12:37:08 +00:00
|
|
|
Use of this flag is mutually exclusive
|
1997-05-03 23:03:56 +00:00
|
|
|
with all other flags and commands, except for
|
|
|
|
.Fl d
|
|
|
|
(only list interfaces that are down)
|
|
|
|
and
|
2001-07-05 12:37:08 +00:00
|
|
|
.Fl u
|
1997-05-03 23:03:56 +00:00
|
|
|
(only list interfaces that are up).
|
1994-05-26 06:35:07 +00:00
|
|
|
.Pp
|
2001-07-02 20:52:34 +00:00
|
|
|
The
|
2004-12-08 19:18:07 +00:00
|
|
|
.Fl v
|
|
|
|
flag may be used to get more verbose status for an interface.
|
|
|
|
.Pp
|
|
|
|
The
|
2001-07-02 20:52:34 +00:00
|
|
|
.Fl C
|
|
|
|
flag may be used to list all of the interface cloners available on
|
|
|
|
the system, with no additional information.
|
|
|
|
Use of this flag is mutually exclusive with all other flags and commands.
|
|
|
|
.Pp
|
2005-07-14 18:33:21 +00:00
|
|
|
The
|
|
|
|
.Fl k
|
|
|
|
flag causes keying information for the interface, if available, to be
|
|
|
|
printed.
|
A major overhaul of the CARP implementation. The ip_carp.c was started
from scratch, copying needed functionality from the old implemenation
on demand, with a thorough review of all code. The main change is that
interface layer has been removed from the CARP. Now redundant addresses
are configured exactly on the interfaces, they run on.
The CARP configuration itself is, as before, configured and read via
SIOCSVH/SIOCGVH ioctls. A new prefix created with SIOCAIFADDR or
SIOCAIFADDR_IN6 may now be configured to a particular virtual host id,
which makes the prefix redundant.
ifconfig(8) semantics has been changed too: now one doesn't need
to clone carpXX interface, he/she should directly configure a vhid
on a Ethernet interface.
To supply vhid data from the kernel to an application the getifaddrs(8)
function had been changed to pass ifam_data with each address. [1]
The new implementation definitely closes all PRs related to carp(4)
being an interface, and may close several others. It also allows
to run a single redundant IP per interface.
Big thanks to Bjoern Zeeb for his help with inet6 part of patch, for
idea on using ifam_data and for several rounds of reviewing!
PR: kern/117000, kern/126945, kern/126714, kern/120130, kern/117448
Reviewed by: bz
Submitted by: bz [1]
2011-12-16 12:16:56 +00:00
|
|
|
For example, the values of 802.11 WEP keys and
|
|
|
|
.Xr carp 4
|
|
|
|
passphrases will be printed, if accessible to the current user.
|
2005-07-14 18:33:21 +00:00
|
|
|
This information is not printed by default, as it may be considered
|
|
|
|
sensitive.
|
2012-03-29 05:02:12 +00:00
|
|
|
.Pp
|
2007-05-22 17:41:09 +00:00
|
|
|
If the network interface driver is not present in the kernel then
|
|
|
|
.Nm
|
|
|
|
will attempt to load it.
|
|
|
|
The
|
|
|
|
.Fl n
|
|
|
|
flag disables this behavior.
|
2005-07-14 18:33:21 +00:00
|
|
|
.Pp
|
1994-05-26 06:35:07 +00:00
|
|
|
Only the super-user may modify the configuration of a network interface.
|
2007-02-03 03:37:37 +00:00
|
|
|
.Sh EXAMPLES
|
|
|
|
Assign the IPv4 address
|
2007-02-04 16:48:56 +00:00
|
|
|
.Li 192.0.2.10 ,
|
2007-02-03 03:37:37 +00:00
|
|
|
with a network mask of
|
|
|
|
.Li 255.255.255.0 ,
|
|
|
|
to the interface
|
2019-05-18 21:01:36 +00:00
|
|
|
.Li em0 :
|
|
|
|
.Dl # ifconfig em0 inet 192.0.2.10 netmask 255.255.255.0
|
2007-02-03 03:37:37 +00:00
|
|
|
.Pp
|
2007-02-04 16:48:56 +00:00
|
|
|
Add the IPv4 address
|
|
|
|
.Li 192.0.2.45 ,
|
2007-02-03 03:37:37 +00:00
|
|
|
with the CIDR network prefix
|
2007-02-04 16:48:56 +00:00
|
|
|
.Li /28 ,
|
2007-02-03 03:37:37 +00:00
|
|
|
to the interface
|
2019-05-18 21:01:36 +00:00
|
|
|
.Li em0 ,
|
2007-02-04 16:48:56 +00:00
|
|
|
using
|
|
|
|
.Cm add
|
|
|
|
as a synonym for the canonical form of the option
|
|
|
|
.Cm alias :
|
2019-05-18 21:01:36 +00:00
|
|
|
.Dl # ifconfig em0 inet 192.0.2.45/28 add
|
2007-02-04 16:48:56 +00:00
|
|
|
.Pp
|
|
|
|
Remove the IPv4 address
|
|
|
|
.Li 192.0.2.45
|
|
|
|
from the interface
|
2019-05-18 21:01:36 +00:00
|
|
|
.Li em0 :
|
|
|
|
.Dl # ifconfig em0 inet 192.0.2.45 -alias
|
2007-02-03 03:37:37 +00:00
|
|
|
.Pp
|
2009-09-12 22:08:20 +00:00
|
|
|
Enable IPv6 functionality of the interface:
|
|
|
|
.Dl # ifconfig em0 inet6 -ifdisabled
|
|
|
|
.Pp
|
2007-02-04 16:48:56 +00:00
|
|
|
Add the IPv6 address
|
|
|
|
.Li 2001:DB8:DBDB::123/48
|
2007-02-03 03:37:37 +00:00
|
|
|
to the interface
|
|
|
|
.Li em0 :
|
2007-02-04 16:48:56 +00:00
|
|
|
.Dl # ifconfig em0 inet6 2001:db8:bdbd::123 prefixlen 48 alias
|
|
|
|
Note that lower case hexadecimal IPv6 addresses are acceptable.
|
2007-02-03 03:37:37 +00:00
|
|
|
.Pp
|
|
|
|
Remove the IPv6 address added in the above example,
|
|
|
|
using the
|
|
|
|
.Li /
|
2007-02-04 16:48:56 +00:00
|
|
|
character as shorthand for the network prefix,
|
|
|
|
and using
|
|
|
|
.Cm delete
|
|
|
|
as a synonym for the canonical form of the option
|
|
|
|
.Fl alias :
|
|
|
|
.Dl # ifconfig em0 inet6 2001:db8:bdbd::123/48 delete
|
2007-02-03 03:37:37 +00:00
|
|
|
.Pp
|
A major overhaul of the CARP implementation. The ip_carp.c was started
from scratch, copying needed functionality from the old implemenation
on demand, with a thorough review of all code. The main change is that
interface layer has been removed from the CARP. Now redundant addresses
are configured exactly on the interfaces, they run on.
The CARP configuration itself is, as before, configured and read via
SIOCSVH/SIOCGVH ioctls. A new prefix created with SIOCAIFADDR or
SIOCAIFADDR_IN6 may now be configured to a particular virtual host id,
which makes the prefix redundant.
ifconfig(8) semantics has been changed too: now one doesn't need
to clone carpXX interface, he/she should directly configure a vhid
on a Ethernet interface.
To supply vhid data from the kernel to an application the getifaddrs(8)
function had been changed to pass ifam_data with each address. [1]
The new implementation definitely closes all PRs related to carp(4)
being an interface, and may close several others. It also allows
to run a single redundant IP per interface.
Big thanks to Bjoern Zeeb for his help with inet6 part of patch, for
idea on using ifam_data and for several rounds of reviewing!
PR: kern/117000, kern/126945, kern/126714, kern/120130, kern/117448
Reviewed by: bz
Submitted by: bz [1]
2011-12-16 12:16:56 +00:00
|
|
|
Configure a single CARP redundant address on igb0, and then switch it
|
|
|
|
to be master:
|
2013-10-21 05:14:00 +00:00
|
|
|
.Dl # ifconfig igb0 vhid 1 10.0.0.1/24 pass foobar up
|
A major overhaul of the CARP implementation. The ip_carp.c was started
from scratch, copying needed functionality from the old implemenation
on demand, with a thorough review of all code. The main change is that
interface layer has been removed from the CARP. Now redundant addresses
are configured exactly on the interfaces, they run on.
The CARP configuration itself is, as before, configured and read via
SIOCSVH/SIOCGVH ioctls. A new prefix created with SIOCAIFADDR or
SIOCAIFADDR_IN6 may now be configured to a particular virtual host id,
which makes the prefix redundant.
ifconfig(8) semantics has been changed too: now one doesn't need
to clone carpXX interface, he/she should directly configure a vhid
on a Ethernet interface.
To supply vhid data from the kernel to an application the getifaddrs(8)
function had been changed to pass ifam_data with each address. [1]
The new implementation definitely closes all PRs related to carp(4)
being an interface, and may close several others. It also allows
to run a single redundant IP per interface.
Big thanks to Bjoern Zeeb for his help with inet6 part of patch, for
idea on using ifam_data and for several rounds of reviewing!
PR: kern/117000, kern/126945, kern/126714, kern/120130, kern/117448
Reviewed by: bz
Submitted by: bz [1]
2011-12-16 12:16:56 +00:00
|
|
|
.Dl # ifconfig igb0 vhid 1 state master
|
|
|
|
.Pp
|
2007-02-03 03:37:37 +00:00
|
|
|
Configure the interface
|
|
|
|
.Li xl0 ,
|
|
|
|
to use 100baseTX, full duplex Ethernet media options:
|
|
|
|
.Dl # ifconfig xl0 media 100baseTX mediaopt full-duplex
|
|
|
|
.Pp
|
2010-01-27 00:30:07 +00:00
|
|
|
Label the em0 interface as an uplink:
|
|
|
|
.Dl # ifconfig em0 description \&"Uplink to Gigabit Switch 2\&"
|
|
|
|
.Pp
|
2007-02-03 03:37:37 +00:00
|
|
|
Create the software network interface
|
|
|
|
.Li gif1 :
|
|
|
|
.Dl # ifconfig gif1 create
|
|
|
|
.Pp
|
|
|
|
Destroy the software network interface
|
|
|
|
.Li gif1 :
|
|
|
|
.Dl # ifconfig gif1 destroy
|
2011-03-12 19:05:39 +00:00
|
|
|
.Pp
|
2011-04-06 11:20:54 +00:00
|
|
|
Display available wireless networks using
|
2011-03-12 19:05:39 +00:00
|
|
|
.Li wlan0 :
|
2011-03-20 22:47:41 +00:00
|
|
|
.Dl # ifconfig wlan0 list scan
|
2016-05-31 17:30:08 +00:00
|
|
|
.Pp
|
|
|
|
Display inet and inet6 address subnet masks in CIDR notation
|
|
|
|
.Dl # ifconfig -f inet:cidr,inet6:cidr
|
2020-06-04 14:44:44 +00:00
|
|
|
.Pp
|
|
|
|
Display interfaces that are up with the exception of loopback
|
|
|
|
.Dl # ifconfig -a -u -G lo
|
1994-05-26 06:35:07 +00:00
|
|
|
.Sh DIAGNOSTICS
|
1998-06-08 02:00:45 +00:00
|
|
|
Messages indicating the specified interface does not exist, the
|
1994-05-26 06:35:07 +00:00
|
|
|
requested address is unknown, or the user is not privileged and
|
|
|
|
tried to alter an interface's configuration.
|
|
|
|
.Sh SEE ALSO
|
|
|
|
.Xr netstat 1 ,
|
2005-03-19 16:14:31 +00:00
|
|
|
.Xr carp 4 ,
|
2009-09-12 22:17:13 +00:00
|
|
|
.Xr gif 4 ,
|
1994-05-26 06:35:07 +00:00
|
|
|
.Xr netintro 4 ,
|
2005-12-16 11:38:18 +00:00
|
|
|
.Xr pfsync 4 ,
|
2005-03-19 16:14:31 +00:00
|
|
|
.Xr polling 4 ,
|
2004-02-21 14:21:18 +00:00
|
|
|
.Xr vlan 4 ,
|
2014-10-20 14:42:42 +00:00
|
|
|
.Xr vxlan 4 ,
|
2012-11-07 15:59:24 +00:00
|
|
|
.Xr devd.conf 5 ,
|
2001-07-05 12:37:08 +00:00
|
|
|
.\" .Xr eon 5 ,
|
2012-11-07 15:59:24 +00:00
|
|
|
.Xr devd 8 ,
|
2014-12-27 08:22:58 +00:00
|
|
|
.Xr jail 8 ,
|
1994-05-26 06:35:07 +00:00
|
|
|
.Xr rc 8 ,
|
2004-06-14 19:31:10 +00:00
|
|
|
.Xr routed 8 ,
|
|
|
|
.Xr sysctl 8
|
1994-05-26 06:35:07 +00:00
|
|
|
.Sh HISTORY
|
|
|
|
The
|
|
|
|
.Nm
|
2002-07-06 19:34:18 +00:00
|
|
|
utility appeared in
|
1994-05-26 06:35:07 +00:00
|
|
|
.Bx 4.2 .
|
2005-01-18 10:09:38 +00:00
|
|
|
.Sh BUGS
|
|
|
|
Basic IPv6 node operation requires a link-local address on each
|
|
|
|
interface configured for IPv6.
|
|
|
|
Normally, such an address is automatically configured by the
|
2009-09-12 22:08:20 +00:00
|
|
|
kernel on each interface added to the system or enabled; this behavior may
|
|
|
|
be disabled by setting per-interface flag
|
|
|
|
.Cm -auto_linklocal .
|
|
|
|
The default value of this flag is 1 and can be disabled by using the sysctl
|
|
|
|
MIB variable
|
|
|
|
.Va net.inet6.ip6.auto_linklocal .
|
2005-01-18 10:09:38 +00:00
|
|
|
.Pp
|
2009-09-12 22:08:20 +00:00
|
|
|
Do not configure IPv6 addresses with no link-local address by using
|
|
|
|
.Nm .
|
|
|
|
It can result in unexpected behaviors of the kernel.
|