os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Use of manual page entity

Browse source 
- Use of various tags
- Some rewordings to avoid contractions and to start a sentence with an
  application name etc.
This commit is contained in:
Marc Fonvieille 2002-12-31 15:29:03 +00:00
parent e570e7129c
commit 05a4f6ddd4
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=15480
1 changed files with 20 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

40
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -553,7 +553,7 @@ wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
to help you accomplish that task.</para>
<para>Now that you have the bridging stuff done, we need to tell the FreeBSD
kernel which interfaces to bridge together. We do that by using sysctl:</para>
kernel which interfaces to bridge together. We do that by using &man.sysctl.8;:</para>
<screen>&prompt.root; <userinput>sysctl net.link.ether.bridge=1</userinput></screen>
<screen>&prompt.root; <userinput>sysctl net.link.ether.bridge_cfg="wi0 xl0"</userinput></screen>
@ -568,13 +568,13 @@ wi0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
<screen>&prompt.root; <userinput>wicontrol -p 6</userinput></screen>
<para>The first &man.wicontrol.8; command tells FreeBSD that the name of this access point
is FreeBSD AP by using the -s FreeBSD AP flags, to use auto rate selection at the
highest rate (11Mbps) with the -t 3 flags, and the SSID (station ID) is set to
my_net with the -n flag. Check out &man.wicontrol.8; for more information.</para>
is <literal>FreeBSD AP</literal> by using the <option>-s</option> flag, to use auto rate selection at the
highest rate (11Mbps) with the <option>-t 3</option> flags, and the SSID (station ID) is set to
<literal>my_net</literal> with the <option>-n</option> flag. Check out &man.wicontrol.8; for more information.</para>
<para>The &man.ifconfig.8; line brings the wi0 interface up, and sets its SSID to my_net.
<para>The &man.ifconfig.8; line brings the <devicename>wi0</devicename> interface up, and sets its SSID to <literal>my_net</literal>.
This is a little redundant, but it is shown here to emphasize that you can do
these settings in either place. You will also notice a mediaopt hostap setting;
these settings in either place. You will also notice a <option>mediaopt hostap</option> setting;
this setting is to tell &man.ifconfig.8; to put the interface into access point mode.</para>
<para>The second &man.wicontrol.8; line turns the interface into access point mode, instead
@ -610,7 +610,7 @@ wi0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
<sect4>
<title>Setting Up A Wireless FreeBSD Client</title>
<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 my_net, and
you start. In this example, we are joining a network that has a name of <literal>my_net</literal>, and
encryption turned off.</para>
<para>Note: In this example, we are not using encryption, which is a dangerous situation.
@ -635,7 +635,7 @@ wi0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
<screen>&prompt.root; <userinput>ifconfig wi0 inet 192.168.0.20 netmask 255.255.255.0 ssid my_net</userinput></screen>
<para>Replace 192.168.0.20 and 255.255.255.0 with a valid IP address and netmask on
<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 devices on
your network that you are on the wired network just as they are.</para>
@ -677,16 +677,16 @@ wi0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
has been cracked, and is fairly trivial to break. This also means it is not something
to rely on when it comes to encrypting sensitive data. </para>
<para>It is better than nothing, so here's how to turn on WEP on your new FreeBSD
<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 mediaopt hostap</userinput></screen>
<para>And here's how you turn on WEP on a client:</para>
<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>
<para>Note that you should replace the 0x1234567890 with a more unique key.</para>
<para>Note that you should replace the <literal>0x1234567890</literal> with a more unique key.</para>
</sect4>
@ -706,19 +706,19 @@ wi0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
they do.</para>
<sect4>
<title>bsd-airtools</title>
<para>bsd-airtools is a package that includes wireless auditing tools for wep key
<title><application>bsd-airtools</application></title>
<para>The <application>bsd-airtools</application> package is a complete toolset that includes wireless auditing tools for WEP key
cracking, access point detection, etc.</para>
<para>bsd-airtools can be installed from the ports collection. Information on
<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 handbook.<para>
<para>dstumbler is the packaged tool that allows for access point discovery and
<para>The program <command>dstumbler</command> is the packaged tool that allows for access point discovery and
signal to noise ratio graphing. If you are having a hard time getting your access
point up and running, dstumbler may help you get started.</para>
point up and running, <command>dstumbler</command> may help you get started.</para>
<para>To test your wireless network security, you may choose to use dweputils to
help you determine if wep is the right solution to your wireless security needs.</para>
<para>To test your wireless network security, you may choose to use <quote>dweputils</quote> (<command>dwepcrack</command>, <command>dwepdump</command> and <command>dwepkeygen</command>) to
help you determine if WEP is the right solution to your wireless security needs.</para>
</sect4>
@ -726,8 +726,8 @@ wi0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
<title>wicontrol, ancontrol, raycontrol</title>
<para>These are the tools you 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 wi0 interface. If you had a Cisco wireless device, it would come
up as an0, and therefore you would use &man.ancontrol.8;.<para>
wireless card is a <devicename>wi0</devicename> interface. If you had a Cisco wireless device, it would come
up as <devicename>an0</devicename>, and therefore you would use &man.ancontrol.8;.<para>
</sect4>