Lines Matching refs:interface
121 number of driver specific interface included in wpa_supplicant, please
123 interface driver_nl80211 (-Dnl80211 on wpa_supplicant command line)
125 specific interface.
150 driver-specific interface code in wpa_supplicant.
328 Following option can be used to include GSM SIM/USIM interface for GSM/UMTS
398 Please note that if you included more than one driver interface in the
400 interface to use by including -D<driver name> option on the command
417 -b = optional bridge interface name
421 -i = interface name
434 -u = enable DBus control interface
436 -W = wait for a control interface monitor before starting
437 -M = start describing matching interface
438 -N = start describing new interface
466 initialize the interface.
472 running one process for each interface separately or by running just
473 one process and list of options at command line. Each interface is
483 not exist, wpa_supplicant can match an interface when it arrives. Each
484 matched interface is separated with -M argument and the -i argument now
488 specific wired interface called lan0, any interface starting with wlan
489 and lastly any other interface. Each match has its own configuration
490 file, and for the wired interface a specific driver has also been given.
498 If the interface is added in a Linux bridge (e.g., br0), the bridge
499 interface needs to be configured to wpa_supplicant in addition to the
500 main interface:
641 'roboswitch' interface (-Dwired or -Droboswitch on command line).
692 interface to request authentication information, like username and
699 The control interface of wpa_supplicant can be configured to allow
753 interface [ifname] = show interfaces/select interface
798 default interface: first interface found in socket path
810 interface. For example, the following command starts wpa_cli for the
811 default interface (-i can be used to select the interface in case of
812 more than one interface being used at the same time):
819 with two command line arguments: interface name and event (CONNECTED
879 Dynamic interface add and operation without configuration files
884 wpa_supplicant process) control interface is used to add and remove
885 network interfaces. Each network interface can then be configured
886 through a per-network interface control interface. For example,
888 network interfaces and then add a network interface and configure a
894 # Add a new interface (wlan0, no configuration file, driver=nl80211, and
895 # enable control interface)
899 # Configure a network using the newly added network interface:
909 # At this point, the new network interface should start trying to associate
912 # Remove network interface
920 (e.g., to control wireless interface operation), wpa_supplicant
939 user). It opens a UNIX domain socket for each interface that is
940 included on the command line; any other interface will be off limits
962 wpa_priv does not use the network interface before wpa_supplicant is
965 can be started when an interface is added (hotplug/udev/etc. scripts).
966 wpa_priv can control multiple interface with one process, but it is
970 It should be noted that the interface used between wpa_supplicant and
972 driver interface and at times, this interface lacks update especially
1008 Common way style of creating a control interface socket in
1013 be used for the control interface.
1021 radio. The RADIO_WORK control interface command can be used for this.
1097 wpa_supplicant sends control interface event messages consisting details
1099 to external programs. The format of the control interface event messages
1102 - Control interface event message format to indicate DSCP request start
1110 - Control interface event message format to add new policy
1124 - Control interface event message format to remove a particular policy,
1130 interface event message format for rejected policy.
1134 - Control interface event message format to indicate end of DSCP request.
1141 - Control interface event message format to indicate wpa_supplicant started
1146 - Control interface event message format to indicate timeout to receive the
1156 control interface command received from the user is as below: