Home | History | Annotate | Download | only in hostapd

Lines Matching refs:interface

8 interface=wlan0
12 # interface is included in a bridge. This parameter is not used with Host AP
14 # figure out the bridge interface (assuming sysfs is enabled and mounted to
17 # For nl80211, this parameter can be used to request the AP interface to be
19 # has been started to change the interface mode). If needed, the bridge
20 # interface is also created.
23 # Driver interface type (hostap/wired/none/nl80211/bsd);
29 # Driver interface parameters (mainly for development testing use)
43 # bit 4 (16) = driver interface
59 # Interface for separate control program. If this is specified, hostapd
62 # configuration. The socket file will be named based on the interface name, so
64 # than one interface is used.
69 # Access control for the control interface can be configured by setting the
73 # run as non-root users. However, since the control interface can be used to
76 # want to allow non-root users to use the contron interface, add a new group
78 # control interface access to this group.
497 # If bridge parameter is set, the WDS STA interface will be added to the same
948 # Configuration data for EAP-SIM database/authentication gateway interface.
1014 # Interface to be used for IAPP broadcast packets
1102 # 1 = option; use default interface if RADIUS server does not include VLAN ID
1106 # Per-Station AP_VLAN interface mode
1107 # If enabled, each station is assigned its own AP_VLAN interface.
1110 # If the sta is not assigned to any VLAN, then its AP_VLAN interface will be
1117 # VLAN interface list for dynamic VLAN mode is read from a separate text file.
1119 # interface. Each station is bound to one interface in the same way as with
1121 # interface and the line must include VLAN ID and interface name separated by
1127 # Interface where 802.1q tagged packets should appear when a RADIUS server is
1129 # each VLAN. Then hostapd adds a VLAN interface (associated with the interface
1130 # indicated by 'vlan_tagged_interface') and the appropriate wireless interface
1134 # Bridge (prefix) to add the wifi and the tagged interface to. This gets the
1135 # VLAN ID appended. It defaults to brvlan%d if no tagged interface is given
1136 # and br%s.%d if a tagged interface is given, provided %s = tagged interface
1140 # When hostapd creates a VLAN interface on vlan_tagged_interfaces, it needs
1350 # interface that are used for connections to other APs. This could include
1351 # wired interfaces and WDS links. The normal wireless data interface towards
1606 # interface controlled by the same hostapd process to restrict Probe Request
1620 # interface controlled by the same hostapd process to reject authentication
1637 # Whether to manage this interface independently from other WPS interfaces
1640 # of interfaces. If this is set to non-zero for an interface, WPS commands
1641 # issued on that interface do not apply to other interfaces and WPS operations
1642 # performed on other interfaces do not affect this interface.
1772 # WPS UPnP interface
2152 # option CONFIG_FST is set while compiling hostapd. They allow this interface
2160 # Identifier of an FST Group the interface belongs to.
2163 # Interface priority within the FST Group.
2164 # Announcing a higher priority for an interface means declaring it more
2169 # Default LLT value for this interface in milliseconds. The value used in case
2233 # Above configuration is using the default interface (wlan#, or multi-SSID VLAN
2235 # default interface name to be allocated for the data packets of the new BSS.
2253 # hostapd to use the driver auto-generated interface address (e.g., to use the
2259 # (search for "valid interface combinations").
2267 # most of the above items can be used here (apart from radio interface specific