r143 - community/trunk/en-US
sradvan at fedoraproject.org
sradvan at fedoraproject.org
Wed Jun 30 23:27:47 UTC 2010
Author: sradvan
Date: 2010-06-30 23:27:45 +0000 (Wed, 30 Jun 2010)
New Revision: 143
Added:
community/trunk/en-US/Communication.xml
Modified:
community/trunk/en-US/Hardware.xml
community/trunk/en-US/Wireless_Guide.xml
Log:
add Communication.xml and move adhoc/master content to it
Added: community/trunk/en-US/Communication.xml
===================================================================
--- community/trunk/en-US/Communication.xml (rev 0)
+++ community/trunk/en-US/Communication.xml 2010-06-30 23:27:45 UTC (rev 143)
@@ -0,0 +1,97 @@
+<?xml version='1.0'?>
+<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<chapter id="chap-Wireless_Guide-Communication">
+ <title>Wireless Communication</title>
+ <para>
+ stuff
+ </para>
+<section id="sect-Wireless_Guide-Hardware-Connection_Modes">
+<title>Connection Modes</title>
+ <para>
+ Clients typically connect in one of two modes: <emphasis>adhoc</emphasis> or <emphasis>infrastructure</emphasis>. Adhoc mode involves stations communicating directly with each other without the need for a central point to manage communications. This is also known as peer-to-peer mode. The default and most common mode is known as Infrastructure mode. Infrastructure mode uses a Wireless Access Point (WAP), which is a central device that manages transmissions between clients. Refer to the following for more details on Access Points:
+ </para>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="./images/access_point.png" format="PNG" />
+ </imageobject>
+ </mediaobject>
+ <para>
+ From <ulink url="http://en.wikipedia.org/wiki/Wireless_access_point">Wikipedia.org</ulink>:
+ <emphasis>In computer networking, a wireless access point (WAP) is a device that allows wireless communication devices to connect to a wireless network using Wi-Fi, Bluetooth or related standards. The WAP usually connects to a wired network, and can relay data between the wireless devices (such as computers or printers) and wired devices on the network.</emphasis>
+ </para>
+ <para>
+ Access points commonly found in home environments provide different features from those found in business or corporate settings. Consumer-level WAPs are often integrated into broadband gateways, and multiple functions can be served from a single device. These functions typically include a switch for wired access, routing functionality, a broadband modem, and a network firewall. Usually an omnidirectional antenna is used, or multiple antennas, a scheme known as <emphasis>antenna diversity</emphasis>. WAPs often have a built-in web interface for their configuration which can be accessed by a web browser.
+ </para>
+
+</section>
+<section id="sect-Wireless_Guide-Hardware-Channels">
+<title>Channels</title>
+ <para>
+ 802.11b and 802.11g (the most common) devices are usually referred to as operating at 2.4GHz (gigahertz). In fact, the signals for these devices can operate on one of eleven (11) distinct channels within the 2.4GHz band. Some regions allow operation in thirteen (13) channels, however the U.S FCC defines eleven (11) channels. What this means is that you can configure your wireless adapter and access point to operate on slightly different frequencies than other networks in your area, to avoid interference and congestion. Each of these channels cover a frequency range of 22MHz; in other words, a device operating in each of these channels can operate at up to 11MHz on either side of the "center" frequencies listed in the following table.
+ </para>
+
+<table frame='all'><title>IEE 802.11b and 802.11g Channel Frequencies</title>
+<tgroup cols='2' align='left' colsep='4' rowsep='4'>
+<colspec colname='c1'/>
+<colspec colnum='2' colname='c2'/>
+<thead>
+<row>
+ <entry namest="c1" nameend="c1" align="left">Channel number</entry>
+ <entry namest="c2" nameend="c2" align="left">Center Frequency (GHz)</entry>
+</row>
+</thead>
+<tbody>
+<row>
+ <entry>1</entry>
+ <entry>2.412</entry>
+</row>
+<row>
+ <entry>2</entry>
+ <entry>2.417</entry>
+</row>
+<row>
+ <entry>3</entry>
+ <entry>2.422</entry>
+</row>
+<row>
+ <entry>4</entry>
+ <entry>2.427</entry>
+</row>
+<row>
+ <entry>5</entry>
+ <entry>2.432</entry>
+</row>
+<row>
+ <entry>6</entry>
+ <entry>2.437</entry>
+</row>
+<row>
+ <entry>7</entry>
+ <entry>2.442</entry>
+</row>
+<row>
+ <entry>8</entry>
+ <entry>2.447</entry>
+</row>
+<row>
+ <entry>9</entry>
+ <entry>2.452</entry>
+</row>
+<row>
+ <entry>10</entry>
+ <entry>2.457</entry>
+</row>
+<row>
+ <entry>11</entry>
+ <entry>2.452</entry>
+</row>
+</tbody>
+</tgroup>
+</table>
+ <para>
+ If we study the frequencies used in these eleven (11) channels, and take into account that each channel can operate in 11MHz ranges either side (+/-) of its center frequency, the channels 1, 6 and 11 never overlap with each other. Channels that are separated by at least five other channels (or at least 2.5MHz) do not overlap. You can use this important piece of knowledge when you have wireless congestion issues; for example, in an apartment building with three wireless networks near each other, you can avoid congestion by getting the networks to run on channels that are sufficiently separated from each other, such as 1, 6 and 11. A heavily congested area may not provide the freedom to do this, however it is a useful thing to remember.
+ </para>
+</section>
+</chapter>
Modified: community/trunk/en-US/Hardware.xml
===================================================================
--- community/trunk/en-US/Hardware.xml 2010-06-30 01:19:47 UTC (rev 142)
+++ community/trunk/en-US/Hardware.xml 2010-06-30 23:27:45 UTC (rev 143)
@@ -2,8 +2,8 @@
<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<chapter id="chap-Wireless_Guide-Hardware_And_Communication">
- <title>Hardware And Communication</title>
+<chapter id="chap-Wireless_Guide-Hardware">
+ <title>Hardware</title>
<para>
This chapter gives an overview of some of the hardware available for wireless LANs, the role they play, and further details about their operation.
</para>
@@ -91,91 +91,4 @@
</listitem>
</itemizedlist>
</section>
-<section id="sect-Wireless_Guide-Hardware-Connection_Modes">
-<title>Connection Modes</title>
- <para>
- Clients typically connect in one of two modes: <emphasis>adhoc</emphasis> or <emphasis>infrastructure</emphasis>. Adhoc mode involves stations communicating directly with each other without the need for a central point to manage communications. This is also known as peer-to-peer mode. The default and most common mode is known as Infrastructure mode. Infrastructure mode uses a Wireless Access Point (WAP), which is a central device that manages transmissions between clients. Refer to the following for more details on Access Points:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/access_point.png" format="PNG" />
- </imageobject>
- </mediaobject>
- <para>
- From <ulink url="http://en.wikipedia.org/wiki/Wireless_access_point">Wikipedia.org</ulink>:
- <emphasis>In computer networking, a wireless access point (WAP) is a device that allows wireless communication devices to connect to a wireless network using Wi-Fi, Bluetooth or related standards. The WAP usually connects to a wired network, and can relay data between the wireless devices (such as computers or printers) and wired devices on the network.</emphasis>
- </para>
- <para>
- Access points commonly found in home environments provide different features from those found in business or corporate settings. Consumer-level WAPs are often integrated into broadband gateways, and multiple functions can be served from a single device. These functions typically include a switch for wired access, routing functionality, a broadband modem, and a network firewall. Usually an omnidirectional antenna is used, or multiple antennas, a scheme known as <emphasis>antenna diversity</emphasis>. WAPs often have a built-in web interface for their configuration which can be accessed by a web browser.
- </para>
-
-</section>
-<section id="sect-Wireless_Guide-Hardware-Channels">
-<title>Channels</title>
- <para>
- 802.11b and 802.11g (the most common) devices are usually referred to as operating at 2.4GHz (gigahertz). In fact, the signals for these devices can operate on one of eleven (11) distinct channels within the 2.4GHz band. Some regions allow operation in thirteen (13) channels, however the U.S FCC defines eleven (11) channels. What this means is that you can configure your wireless adapter and access point to operate on slightly different frequencies than other networks in your area, to avoid interference and congestion. Each of these channels cover a frequency range of 22MHz; in other words, a device operating in each of these channels can operate at up to 11MHz on either side of the "center" frequencies listed in the following table.
- </para>
-
-<table frame='all'><title>IEE 802.11b and 802.11g Channel Frequencies</title>
-<tgroup cols='2' align='left' colsep='4' rowsep='4'>
-<colspec colname='c1'/>
-<colspec colnum='2' colname='c2'/>
-<thead>
-<row>
- <entry namest="c1" nameend="c1" align="left">Channel number</entry>
- <entry namest="c2" nameend="c2" align="left">Center Frequency (GHz)</entry>
-</row>
-</thead>
-<tbody>
-<row>
- <entry>1</entry>
- <entry>2.412</entry>
-</row>
-<row>
- <entry>2</entry>
- <entry>2.417</entry>
-</row>
-<row>
- <entry>3</entry>
- <entry>2.422</entry>
-</row>
-<row>
- <entry>4</entry>
- <entry>2.427</entry>
-</row>
-<row>
- <entry>5</entry>
- <entry>2.432</entry>
-</row>
-<row>
- <entry>6</entry>
- <entry>2.437</entry>
-</row>
-<row>
- <entry>7</entry>
- <entry>2.442</entry>
-</row>
-<row>
- <entry>8</entry>
- <entry>2.447</entry>
-</row>
-<row>
- <entry>9</entry>
- <entry>2.452</entry>
-</row>
-<row>
- <entry>10</entry>
- <entry>2.457</entry>
-</row>
-<row>
- <entry>11</entry>
- <entry>2.452</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
- <para>
- If we study the frequencies used in these eleven (11) channels, and take into account that each channel can operate in 11MHz ranges either side (+/-) of its center frequency, the channels 1, 6 and 11 never overlap with each other. Channels that are separated by at least five other channels (or at least 2.5MHz) do not overlap. You can use this important piece of knowledge when you have wireless congestion issues; for example, in an apartment building with three wireless networks near each other, you can avoid congestion by getting the networks to run on channels that are sufficiently separated from each other, such as 1, 6 and 11. A heavily congested area may not provide the freedom to do this, however it is a useful thing to remember.
- </para>
-</section>
</chapter>
Modified: community/trunk/en-US/Wireless_Guide.xml
===================================================================
--- community/trunk/en-US/Wireless_Guide.xml 2010-06-30 01:19:47 UTC (rev 142)
+++ community/trunk/en-US/Wireless_Guide.xml 2010-06-30 23:27:45 UTC (rev 143)
@@ -8,7 +8,8 @@
<xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Standards.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Hardware.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Security.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Communication.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Security.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Fedora_Wireless.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Other_Wireless.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Resources.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
More information about the docs-commits
mailing list