From sradvan at fedoraproject.org Wed Jun 10 16:01:25 2015 Content-Type: multipart/mixed; boundary="===============1895831905236319986==" MIME-Version: 1.0 From: sradvan To: docs-commits at lists.fedoraproject.org Subject: r143 - community/trunk/en-US Date: Wed, 30 Jun 2010 23:27:47 +0000 Message-ID: <20100630232747.D34C8120277@lists.fedorahosted.org> --===============1895831905236319986== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- community/trunk/en-US/Communication.xml (rev 0) +++ community/trunk/en-US/Communication.xml 2010-06-30 23:27:45 UTC (rev 14= 3) @@ -0,0 +1,97 @@ + + + + + Wireless Communication + + stuff = + +
+Connection Modes + + Clients typically connect in one of two modes: adhoc or infrastructure. Adhoc mode involves stations co= mmunicating directly with each other without the need for a central point t= o manage communications. This is also known as peer-to-peer mode. The defau= lt and most common mode is known as Infrastructure mode. Infrastructure mod= e uses a Wireless Access Point (WAP), which is a central device that manage= s transmissions between clients. Refer to the following for more details on= Access Points: + + + + + + + + From Wikipedia.org: + In computer networking, a wireless access point (WAP) is a d= evice that allows wireless communication devices to connect to a wireless n= etwork using Wi-Fi, Bluetooth or related standards. The WAP usually connect= s to a wired network, and can relay data between the wireless devices (such= as computers or printers) and wired devices on the network. + + + Access points commonly found in home environments provide different fe= atures from those found in business or corporate settings. Consumer-level W= APs are often integrated into broadband gateways, and multiple functions ca= n be served from a single device. These functions typically include a switc= h 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 antenna diversity. WAPs often have= a built-in web interface for their configuration which can be accessed by = a web browser. = + + = +
+
+Channels + + 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 FC= C defines eleven (11) channels. What this means is that you can configure y= our wireless adapter and access point to operate on slightly different freq= uencies than other networks in your area, to avoid interference and congest= ion. Each of these channels cover a frequency range of 22MHz; in other word= s, 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. + + +IEE 802.11b and 802.11g Channel Frequencies</t= itle> +<tgroup cols=3D'2' align=3D'left' colsep=3D'4' rowsep=3D'4'> +<colspec colname=3D'c1'/> +<colspec colnum=3D'2' colname=3D'c2'/> +<thead> +<row> + <entry namest=3D"c1" nameend=3D"c1" align=3D"left">Channel number</entry> + <entry namest=3D"c2" nameend=3D"c2" align=3D"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 ta= ke 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 e= ach 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 knowle= dge when you have wireless congestion issues; for example, in an apartment = building with three wireless networks near each other, you can avoid conges= tion by getting the networks to run on channels that are sufficiently separ= ated 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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- 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=3D"chap-Wireless_Guide-Hardware_And_Communication"> - <title>Hardware And Communication + + Hardware This chapter gives an overview of some of the hardware available for = wireless LANs, the role they play, and further details about their operatio= n. @@ -91,91 +91,4 @@ -
-Connection Modes - - Clients typically connect in one of two modes: adhoc or infrastructure. Adhoc mode involves stations co= mmunicating directly with each other without the need for a central point t= o manage communications. This is also known as peer-to-peer mode. The defau= lt and most common mode is known as Infrastructure mode. Infrastructure mod= e uses a Wireless Access Point (WAP), which is a central device that manage= s transmissions between clients. Refer to the following for more details on= Access Points: - - - - - - - - From Wikipedia.org: - In computer networking, a wireless access point (WAP) is a d= evice that allows wireless communication devices to connect to a wireless n= etwork using Wi-Fi, Bluetooth or related standards. The WAP usually connect= s to a wired network, and can relay data between the wireless devices (such= as computers or printers) and wired devices on the network. - - - Access points commonly found in home environments provide different fe= atures from those found in business or corporate settings. Consumer-level W= APs are often integrated into broadband gateways, and multiple functions ca= n be served from a single device. These functions typically include a switc= h 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 antenna diversity. WAPs often have= a built-in web interface for their configuration which can be accessed by = a web browser. = - - = -
-
-Channels - - 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 FC= C defines eleven (11) channels. What this means is that you can configure y= our wireless adapter and access point to operate on slightly different freq= uencies than other networks in your area, to avoid interference and congest= ion. Each of these channels cover a frequency range of 22MHz; in other word= s, 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. - - -
IEE 802.11b and 802.11g Channel Frequencies</t= itle> -<tgroup cols=3D'2' align=3D'left' colsep=3D'4' rowsep=3D'4'> -<colspec colname=3D'c1'/> -<colspec colnum=3D'2' colname=3D'c2'/> -<thead> -<row> - <entry namest=3D"c1" nameend=3D"c1" align=3D"left">Channel number</entry> - <entry namest=3D"c2" nameend=3D"c2" align=3D"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 ta= ke 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 e= ach 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 knowle= dge when you have wireless congestion issues; for example, in an apartment = building with three wireless networks near each other, you can avoid conges= tion by getting the networks to run on channels that are sufficiently separ= ated 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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- community/trunk/en-US/Wireless_Guide.xml 2010-06-30 01:19:47 UTC (rev 1= 42) +++ community/trunk/en-US/Wireless_Guide.xml 2010-06-30 23:27:45 UTC (rev 1= 43) @@ -8,7 +8,8 @@ <xi:include href=3D"Introduction.xml" xmlns:xi=3D"http://www.w3.org/2001/= XInclude" /> <xi:include href=3D"Standards.xml" xmlns:xi=3D"http://www.w3.org/2001/XIn= clude" /> <xi:include href=3D"Hardware.xml" xmlns:xi=3D"http://www.w3.org/2001/XInc= lude" /> - <xi:include href=3D"Security.xml" xmlns:xi=3D"http://www.w3.org/2001/XI= nclude" /> + <xi:include href=3D"Communication.xml" xmlns:xi=3D"http://www.w3.org/2001= /XInclude" /> + <xi:include href=3D"Security.xml" xmlns:xi=3D"http://www.w3.org/2001/XInc= lude" /> <xi:include href=3D"Fedora_Wireless.xml" xmlns:xi=3D"http://www.w3.org/20= 01/XInclude" /> <xi:include href=3D"Other_Wireless.xml" xmlns:xi=3D"http://www.w3.org/200= 1/XInclude" /> <xi:include href=3D"Resources.xml" xmlns:xi=3D"http://www.w3.org/2001/XIn= clude" /> --===============1895831905236319986==--