Source string Read only

(itstool) path: sect4/para
Context English State
The configuration is done in <filename>/etc/hostapd.conf</filename>:
interface=wlan0 <co xml:id="co-ap-wpapsk-iface"/>
debug=1 <co xml:id="co-ap-wpapsk-dbug"/>
ctrl_interface=/var/run/hostapd <co xml:id="co-ap-wpapsk-ciface"/>
ctrl_interface_group=wheel <co xml:id="co-ap-wpapsk-cifacegrp"/>
ssid=freebsdap <co xml:id="co-ap-wpapsk-ssid"/>
wpa=2 <co xml:id="co-ap-wpapsk-wpa"/>
wpa_passphrase=freebsdmall <co xml:id="co-ap-wpapsk-pass"/>
wpa_key_mgmt=WPA-PSK <co xml:id="co-ap-wpapsk-kmgmt"/>
wpa_pairwise=CCMP <co xml:id="co-ap-wpapsk-pwise"/>
Wireless interface used for the access point.
Level of verbosity used during the execution of <citerefentry><refentrytitle>hostapd</refentrytitle><manvolnum>8</manvolnum></citerefentry>. A value of <literal>1</literal> represents the minimal level.
Pathname of the directory used by <citerefentry><refentrytitle>hostapd</refentrytitle><manvolnum>8</manvolnum></citerefentry> to store domain socket files for communication with external programs such as <citerefentry><refentrytitle>hostapd_cli</refentrytitle><manvolnum>8</manvolnum></citerefentry>. The default value is used in this example.
The group allowed to access the control interface files.
The wireless network name, or <acronym>SSID</acronym>, that will appear in wireless scans.
Enable <acronym>WPA</acronym> and specify which <acronym>WPA</acronym> authentication protocol will be required. A value of <literal>2</literal> configures the <acronym>AP</acronym> for <acronym>WPA2</acronym> and is recommended. Set to <literal>1</literal> only if the obsolete <acronym>WPA</acronym> is required.
ASCII passphrase for <acronym>WPA</acronym> authentication.
Always use strong passwords that are at least 8 characters long and made from a rich alphabet so that they will not be easily guessed or attacked.
The key management protocol to use. This example sets <acronym>WPA-PSK</acronym>.
Encryption algorithms accepted by the access point. In this example, only the <acronym>CCMP</acronym> (<acronym>AES</acronym>) cipher is accepted. <acronym>CCMP</acronym> is an alternative to <acronym>TKIP</acronym> and is strongly preferred when possible. <acronym>TKIP</acronym> should be allowed only when there are stations incapable of using <acronym>CCMP</acronym>.
The next step is to start <citerefentry><refentrytitle>hostapd</refentrytitle><manvolnum>8</manvolnum></citerefentry>:
<prompt>#</prompt> <userinput>service hostapd forcestart</userinput>
<prompt>#</prompt> <userinput>ifconfig <replaceable>wlan0</replaceable></userinput>
wlan0: flags=8943&lt;UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
ether 04:f0:21:16:8e:10
inet6 fe80::6f0:21ff:fe16:8e10%wlan0 prefixlen 64 scopeid 0x9
nd6 options=21&lt;PERFORMNUD,AUTO_LINKLOCAL&gt;
media: IEEE 802.11 Wireless Ethernet autoselect mode 11na &lt;hostap&gt;
status: running
ssid No5ignal channel 36 (5180 MHz 11a ht/40+) bssid 04:f0:21:16:8e:10
country US ecm authmode WPA2/802.11i privacy MIXED deftxkey 2
AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 17 mcastrate 6 mgmtrate 6
scanvalid 60 ampdulimit 64k ampdudensity 8 shortgi wme burst
dtimperiod 1 -dfs
groups: wlan
Once the <acronym>AP</acronym> is running, the clients can associate with it. See <xref linkend="network-wireless-wpa"/> for more details. It is possible to see the stations associated with the <acronym>AP</acronym> using <command>ifconfig <replaceable>wlan0</replaceable> list sta</command>.
<acronym>WEP</acronym> Host-based Access Point
It is not recommended to use <acronym>WEP</acronym> for setting up an <acronym>AP</acronym> since there is no authentication mechanism and the encryption is easily cracked. Some legacy wireless cards only support <acronym>WEP</acronym> and these cards will only support an <acronym>AP</acronym> without authentication or encryption.
The wireless device can now be put into hostap mode and configured with the correct <acronym>SSID</acronym> and <acronym>IP</acronym> address:
<prompt>#</prompt> <userinput>ifconfig <replaceable>wlan0</replaceable> create wlandev <replaceable>ath0</replaceable> wlanmode hostap</userinput>
<prompt>#</prompt> <userinput>ifconfig <replaceable>wlan0</replaceable> inet <replaceable></replaceable> netmask <replaceable></replaceable> \
ssid <replaceable>freebsdap</replaceable> wepmode on weptxkey <replaceable>3</replaceable> wepkey <replaceable>3:0x3456789012</replaceable> mode 11g</userinput>
The <literal>weptxkey</literal> indicates which <acronym>WEP</acronym> key will be used in the transmission. This example uses the third key as key numbering starts with <literal>1</literal>. This parameter must be specified in order to encrypt the data.
The <literal>wepkey</literal> sets the selected <acronym>WEP</acronym> key. It should be in the format <replaceable>index:key</replaceable>. If the index is not given, key <literal>1</literal> is set. The index needs to be set when using keys other than the first key.
Use <citerefentry><refentrytitle>ifconfig</refentrytitle><manvolnum>8</manvolnum></citerefentry> to see the status of the <filename>wlan0</filename> interface:
<prompt>#</prompt> <userinput>ifconfig <replaceable>wlan0</replaceable></userinput>
wlan0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
ether 00:11:95:c3:0d:ac
inet netmask 0xffffff00 broadcast
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g &lt;hostap&gt;
status: running
ssid freebsdap channel 4 (2427 Mhz 11g) bssid 00:11:95:c3:0d:ac
country US ecm authmode OPEN privacy ON deftxkey 3 wepkey 3:40-bit
txpower 21.5 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs
From another wireless machine, it is now possible to initiate a scan to find the <acronym>AP</acronym>:
<prompt>#</prompt> <userinput>ifconfig <replaceable>wlan0</replaceable> create wlandev <replaceable>ath0</replaceable></userinput>
<prompt>#</prompt> <userinput>ifconfig <replaceable>wlan0</replaceable> up scan</userinput>
freebsdap 00:11:95:c3:0d:ac 1 54M 22:1 100 EPS
In this example, the client machine found the <acronym>AP</acronym> and can associate with it using the correct parameters. See <xref linkend="network-wireless-wep"/> for more details.
Using Both Wired and Wireless Connections
A wired connection provides better performance and reliability, while a wireless connection provides flexibility and mobility. Laptop users typically want to roam seamlessly between the two types of connections.
On FreeBSD, it is possible to combine two or even more network interfaces together in a <quote>failover</quote> fashion. This type of configuration uses the most preferred and available connection from a group of network interfaces, and the operating system switches automatically when the link state changes.
Link aggregation and failover is covered in <xref linkend="network-aggregation"/> and an example for using both wired and wireless connections is provided at <xref linkend="networking-lagg-wired-and-wireless"/>.


No matching activity found.

Browse all component changes

Things to check

Multiple failing checks

The translations in several languages have failing checks



English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect4/para
Source string location
String age
a year ago
Source string age
a year ago
Translation file
books/handbook.pot, string 10817