One s/network/-net/ I forgot in my previous commit.
In Wireless section: - Use of replaceable, literal, and command tags where needed - Use of note tags instead of "Note:" - Some little rewordings - Use of lowercase for some role attributes - Punctuation fixes
This commit is contained in:
Marc Fonvieille
parent
e843ed4241
commit
4c2889b644
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=20277
1 changed files with 20 additions and 20 deletions
|
|
@ -532,7 +532,7 @@ default 10.0.0.1 UGS 0 49378 xl0
|
|||
<hostid>RouterA</hostid>'s routing table using <hostid
|
||||
role="ipaddr">192.168.1.2</hostid> as the next hop.</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>route add network 192.168.2.0/24 192.168.1.2</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>route add -net 192.168.2.0/24 192.168.1.2</userinput></screen>
|
||||
|
||||
<para>Now <hostid>RouterA</hostid> can reach any hosts on the
|
||||
<hostid role="ipaddr">192.168.2.0/24</hostid>
|
||||
|
|
@ -894,13 +894,13 @@ wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
|
|||
<para>You will need to know a few things about the wireless
|
||||
network you are joining before you start. In this example, we
|
||||
are joining a network that has a name of
|
||||
<literal>my_net</literal>, and encryption turned off.</para>
|
||||
<replaceable>my_net</replaceable>, and encryption turned off.</para>
|
||||
|
||||
<para>Note: In this example, we are not using encryption, which
|
||||
<note><para>In this example, we are not using encryption, which
|
||||
is a dangerous situation. In the next section, you will learn
|
||||
how to turn on encryption, and why it is important to do so,
|
||||
how to turn on encryption, why it is important to do so,
|
||||
and why some encryption technologies still do not completely
|
||||
protect you.</para>
|
||||
protect you.</para></note>
|
||||
|
||||
<para>Make sure your card is recognized by FreeBSD:</para>
|
||||
|
||||
|
|
@ -916,13 +916,13 @@ wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
|
|||
channel 10 authmode OPEN powersavemode OFF powersavesleep 100
|
||||
wepmode OFF weptxkey 1</screen>
|
||||
|
||||
<para>Now, we will set the card to the correct settings for our
|
||||
<para>Now, we can set the card to the correct settings for our
|
||||
network:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>ifconfig wi0 inet 192.168.0.20 netmask 255.255.255.0 ssid my_net</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>ifconfig wi0 inet <replaceable>192.168.0.20</replaceable> netmask <replaceable>255.255.255.0</replaceable> ssid <replaceable>my_net</replaceable></userinput></screen>
|
||||
|
||||
<para>Replace <hostid role="IPAddr">192.168.0.20</hostid> and
|
||||
<hostid role="Netmask">255.255.255.0</hostid> with a valid IP
|
||||
<para>Replace <hostid role="ipaddr">192.168.0.20</hostid> and
|
||||
<hostid role="netmask">255.255.255.0</hostid> with a valid IP
|
||||
address and netmask on your wired network. Remember, our
|
||||
access point is bridging the data between the wireless
|
||||
network, and the wired network, so it will appear to the other
|
||||
|
|
@ -942,8 +942,8 @@ wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
|
|||
<para>should return some information, and you should see:</para>
|
||||
<screen>status: associated</screen>
|
||||
|
||||
<para>If it does not show associated, then you may be out of
|
||||
range of the access point, do not have encryption on, or
|
||||
<para>If it does not show <literal>associated</literal>, then you may be out of
|
||||
range of the access point, have encryption on, or
|
||||
possibly have a configuration problem.</para>
|
||||
|
||||
</sect4>
|
||||
|
|
@ -966,7 +966,7 @@ wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
|
|||
of the air. </para>
|
||||
|
||||
<para>The two most common ways to encrypt the data between your
|
||||
client and the access point, are WEP, and &man.ipsec.4;.</para>
|
||||
client and the access point are WEP, and &man.ipsec.4;.</para>
|
||||
|
||||
<sect4>
|
||||
<title>WEP</title>
|
||||
|
|
@ -981,13 +981,13 @@ wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
|
|||
<para>It is better than nothing, so use the following to turn on
|
||||
WEP on your new FreeBSD access point:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>ifconfig wi0 inet up ssid my_net wepmode on wepkey 0x1234567890 media DS/11Mbps mediaopt hostap</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>ifconfig wi0 inet up ssid <replaceable>my_net</replaceable> wepmode on wepkey <replaceable>0x1234567890</replaceable> media DS/11Mbps mediaopt hostap</userinput></screen>
|
||||
|
||||
<para>And you can turn on WEP on a client with this command:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>ifconfig wi0 inet 192.168.0.20 netmask 255.255.255.0 ssid my_net wepmode on wepkey 0x1234567890</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>ifconfig wi0 inet <replaceable>192.168.0.20</replaceable> netmask <replaceable>255.255.255.0</replaceable> ssid <replaceable>my_net</replaceable> wepmode on wepkey <replaceable>0x1234567890</replaceable></userinput></screen>
|
||||
|
||||
<para>Note that you should replace the <literal>0x1234567890</literal> with a more unique key.</para>
|
||||
<para>Note that you should replace the <replaceable>0x1234567890</replaceable> with a more unique key.</para>
|
||||
|
||||
</sect4>
|
||||
|
||||
|
|
@ -1020,7 +1020,7 @@ wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
|
|||
<para>The <application>bsd-airtools</application> utilities can be
|
||||
installed from the <filename
|
||||
role="package">net/bsd-airtools</filename> port. Information on
|
||||
installing ports can be found in <xref linkend="ports"> of the
|
||||
installing ports can be found in <xref linkend="ports"> of this
|
||||
handbook.</para>
|
||||
|
||||
<para>The program <command>dstumbler</command> is the packaged
|
||||
|
|
@ -1038,9 +1038,9 @@ wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
|
|||
</sect4>
|
||||
|
||||
<sect4>
|
||||
<title>The <application>wicontrol</application>, <application>ancontrol</application> and <application>raycontrol</application> Utilities</title>
|
||||
<title>The <command>wicontrol</command>, <command>ancontrol</command> and <command>raycontrol</command> Utilities</title>
|
||||
|
||||
<para>These are the tools you use to control how your wireless
|
||||
<para>These are the tools you can use to control how your wireless
|
||||
card behaves on the wireless network. In the examples above, we
|
||||
have chosen to use &man.wicontrol.8;, since our wireless card is
|
||||
a <devicename>wi0</devicename> interface. If you had a Cisco
|
||||
|
|
@ -1051,10 +1051,10 @@ wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
|
|||
</sect4>
|
||||
|
||||
<sect4>
|
||||
<title>The <application>ifconfig</application> Command</title>
|
||||
<title>The <command>ifconfig</command> Command</title>
|
||||
<indexterm><primary>ifconfig</primary></indexterm>
|
||||
|
||||
<para>&man.ifconfig.8; can be used to do many of the same options
|
||||
<para>The &man.ifconfig.8; command can be used to do many of the same options
|
||||
as &man.wicontrol.8;, however it does lack a few options. Check
|
||||
&man.ifconfig.8; for command line parameters and options.</para>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue