doc-el commit 1022:9947f38d88e2 - Replaced english text of 'adva...

freebsd-doc-el at lists.hellug.gr freebsd-doc-el at lists.hellug.gr
Sun Nov 9 06:50:07 EET 2008


changeset: 1022:9947f38d88e2
user:      Manolis Kiagias <sonicy at otenet.gr>
date:      2008-11-06 17:15 +0200
details:   http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=9947f38d88e2

description:
	Replaced english text of 'advanced-networking' with rev. 1.414 (no changes in synopsis)

diffstat:

1 file changed, 1015 insertions(+), 179 deletions(-)
el_GR.ISO8859-7/books/handbook/advanced-networking/chapter.sgml | 1194 ++++++++--

diffs (truncated from 1375 to 300 lines):

diff -r c7fcededf6cd -r 9947f38d88e2 el_GR.ISO8859-7/books/handbook/advanced-networking/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/advanced-networking/chapter.sgml	Thu Nov 06 17:10:43 2008 +0200
+++ b/el_GR.ISO8859-7/books/handbook/advanced-networking/chapter.sgml	Thu Nov 06 17:15:05 2008 +0200
@@ -7,7 +7,7 @@
   $FreeBSD: doc/el_GR.ISO8859-7/books/handbook/advanced-networking/chapter.sgml,v 1.2 2008/01/14 14:19:43 keramida Exp $
 
   %SOURCE%	en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
-  %SRCID%	1.1
+  %SRCID%	1.414
 
 -->
 
@@ -666,6 +666,17 @@
 	<filename>/etc/mrouted.conf</filename>.  More details on
 	multicast configuration may be found in the manual page for
 	&man.mrouted.8;.</para>
+
+      <note>
+	<para>As of &os;&nbsp;7.0 the &man.mrouted.8; multicast routing daemon
+	  has been removed from the base system.  It implements the
+	  <acronym>DVMRP</acronym> multicast routing protocol, which has
+	  largely been replaced by &man.pim.4; in many multicast
+	  installations.  The related &man.map-mbone.8; and
+	  &man.mrinfo.8; utilities have also been removed.  These programs
+	  are now available in the &os; Ports&nbsp;Collection as
+	  <filename role="package">net/mrouted</filename>.</para>
+      </note>
     </sect2>
   </sect1>
 
@@ -830,9 +841,18 @@
 
 	<para>With a device driver configured you need to also bring
 	  in the 802.11 networking support required by the driver.
-	  For the &man.ath.4; driver this is at least the &man.wlan.4;
-	  module; this module is automatically loaded with the
-	  wireless device driver.  With that you will need the modules
+	  For the &man.ath.4; driver these are at least the &man.wlan.4;,
+	  <literal>wlan_scan_ap</literal> and
+	  <literal>wlan_scan_sta</literal>
+	  modules; the &man.wlan.4; module is automatically loaded with the
+	  wireless device driver, the remaining modules must be loaded
+	  at boot time via the <filename>/boot/loader.conf</filename>
+	  file:</para>
+
+	<programlisting>wlan_scan_ap_load="YES"
+wlan_scan_sta_load="YES"</programlisting>
+
+	<para>With that you will need the modules
 	  that implement cryptographic support for the security
 	  protocols you intend to use.  These are intended to be
 	  dynamically loaded on demand by the &man.wlan.4; module but
@@ -866,6 +886,8 @@
 device ath_hal           # Atheros Hardware Access Layer
 device ath_rate_sample   # John Bicket's SampleRate control algorithm.
 device wlan              # 802.11 support (Required)
+device wlan_scan_ap      # 802.11 AP mode scanning
+device wlan_scan_sta     # 802.11 STA mode scanning
 device wlan_wep          # WEP crypto support for 802.11 devices
 device wlan_ccmp         # AES-CCMP crypto support for 802.11 devices
 device wlan_tkip         # TKIP and Michael crypto support for 802.11 devices</programlisting>
@@ -910,8 +932,8 @@
 
 	  <screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable> up scan</userinput>
 SSID            BSSID              CHAN RATE  S:N   INT CAPS
-dlinkap         00:13:46:49:41:76    6   54M 29:0   100 EPS  WPA WME
-freebsdap       00:11:95:c3:0d:ac    1   54M 22:0   100 EPS  WPA</screen>
+dlinkap         00:13:46:49:41:76    6   54M 29:3   100 EPS  WPA WME
+freebsdap       00:11:95:c3:0d:ac    1   54M 22:1   100 EPS  WPA</screen>
 
 	  <note>
 	    <para>You must mark the interface <option>up</option>
@@ -1152,7 +1174,7 @@
 	      parameters you have set up for selecting an access
 	      point:</para>
 
-	    <programlisting>ifconfig_ath0="inet <replaceable>192.168.1.100</replaceable> netmask <replaceable>255.255.255.0</replaceable> ssid <replaceable>your_ssid_here</replaceable>"</programlisting>
+	    <programlisting>ifconfig_ath0="ssid <replaceable>your_ssid_here</replaceable> inet <replaceable>192.168.1.100</replaceable> netmask <replaceable>255.255.255.0</replaceable>"</programlisting>
 	  </sect5>
 
 	<sect4 id="network-wireless-wpa">
@@ -1644,15 +1666,18 @@
 	  <para>WEP can be set up with
 	    <command>ifconfig</command>:</para>
 
-	  <screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable> inet <replaceable>192.168.1.100</replaceable> netmask <replaceable>255.255.255.0</replaceable> ssid my_net \
-	    wepmode on weptxkey 3 wepkey 3:0x3456789012</userinput></screen>
+	  <screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable> ssid my_net wepmode on weptxkey 3 wepkey 3:0x3456789012 \
+	    inet <replaceable>192.168.1.100</replaceable> netmask <replaceable>255.255.255.0</replaceable></userinput></screen>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>The <literal>weptxkey</literal> means which WEP
 		key will be used in the transmission.  Here we used the
 		third key.  This must match the setting in the access
-		point.</para>
+		point.  If you do not have any idea of what is the key
+		used by the access point, you should try to use
+		<literal>1</literal> (i.e., the first key) for this
+		value.</para>
 	    </listitem>
 
 	    <listitem>
@@ -1707,7 +1732,7 @@
 
       <para>On the box <hostid>A</hostid>:</para>
 
-      <screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable> inet <replaceable>192.168.0.1</replaceable> netmask <replaceable>255.255.255.0</replaceable> ssid <replaceable>freebsdap</replaceable> mediaopt adhoc</userinput>
+      <screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable> ssid <replaceable>freebsdap</replaceable> mediaopt adhoc inet <replaceable>192.168.0.1</replaceable> netmask <replaceable>255.255.255.0</replaceable></userinput>
 &prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable></userinput>
   ath0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
 	  inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
@@ -1726,14 +1751,14 @@
 
       <screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable> up scan</userinput>
   SSID            BSSID              CHAN RATE  S:N   INT CAPS
-  freebsdap       02:11:95:c3:0d:ac    2   54M 19:0   100 IS</screen>
+  freebsdap       02:11:95:c3:0d:ac    2   54M 19:3   100 IS</screen>
 
       <para>The <literal>I</literal> in the output confirms the
 	machine <hostid>A</hostid> is in ad-hoc mode.  We just have to
 	configure <hostid>B</hostid> with a different IP
 	address:</para>
 
-      <screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable> inet <replaceable>192.168.0.2</replaceable> netmask <replaceable>255.255.255.0</replaceable> ssid <replaceable>freebsdap</replaceable> mediaopt adhoc</userinput>
+      <screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable> ssid <replaceable>freebsdap</replaceable> mediaopt adhoc inet <replaceable>192.168.0.2</replaceable> netmask <replaceable>255.255.255.0</replaceable></userinput>
 &prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable></userinput>
   ath0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
 	  inet6 fe80::211:95ff:fed5:4362%ath0 prefixlen 64 scopeid 0x1
@@ -1748,6 +1773,305 @@
 	    ready to exchange informations.</para>
     </sect2>
 
+    <sect2 id="network-wireless-ap">
+      <title>&os; Host Access Points</title>
+
+      <para>&os; can act as an Access Point (AP) which eliminates the
+	need to buy a hardware AP or run an ad-hoc network.  This can be
+	particularly useful when your &os; machine is acting as a
+	gateway to another network (e.g., the Internet).</para>
+
+      <sect3 id="network-wireless-ap-basic">
+	<title>Basic Settings</title>
+
+	<para>Before configuring your &os; machine as an AP, the
+	  kernel must be configured with the appropriate wireless
+	  networking support for your wireless card.  You also have to
+	  add the support for the security protocols you intend to
+	  use.  For more details, see <xref
+	  linkend="network-wireless-basic">.</para>
+
+	<note>
+	  <para>The use of the NDIS driver wrapper and the &windows;
+	    drivers do not allow currently the AP operation.  Only
+	    native &os; wireless drivers support AP mode.</para>
+	</note>
+
+	<para>Once the wireless networking support is loaded, you can
+	  check if your wireless device supports the host-based access
+	  point mode (also know as hostap mode):</para>
+
+	<screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable> list caps</userinput>
+ath0=783ed0f&lt;WEP,TKIP,AES,AES_CCM,IBSS,HOSTAP,AHDEMO,TXPMGT,SHSLOT,SHPREAMBLE,MONITOR,TKIPMIC,WPA1,WPA2,BURST,WME&gt;</screen>
+
+	<para>This output displays the card capabilities; the
+	  <literal>HOSTAP</literal> word confirms this wireless card
+	  can act as an Access Point.  Various supported ciphers are
+	  also mentioned: WEP, TKIP, WPA2, etc., these informations
+	  are important to know what security protocols could be set
+	  on the Access Point.</para>
+
+	<para>The wireless device can now be put into hostap mode and
+	  configured with the correct SSID and IP address:</para>
+
+	<screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable> ssid <replaceable>freebsdap</replaceable> mode 11g mediaopt hostap</userinput> inet <replaceable>192.168.0.1</replaceable> netmask <replaceable>255.255.255.0</replaceable></screen>
+
+	<para>Use again <command>ifconfig</command> to see the status
+	  of the <devicename>ath0</devicename> interface:</para>
+
+	<screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable></userinput>
+  ath0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
+	  inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
+	  inet6 fe80::211:95ff:fec3:dac%ath0 prefixlen 64 scopeid 0x4
+	  ether 00:11:95:c3:0d:ac
+	  media: IEEE 802.11 Wireless Ethernet autoselect mode 11g &lt;hostap&gt;
+	  status: associated
+	  ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac
+	  authmode OPEN privacy OFF txpowmax 38 bmiss 7 protmode CTS burst dtimperiod 1 bintval 100</screen>
+
+	<para>The <literal>hostap</literal> parameter indicates the
+	  interface is running in the host-based access point
+	  mode.</para>
+
+	<para>The interface configuration can be done automatically at
+	  boot time by adding the following line to
+	  <filename>/etc/rc.conf</filename>:</para>
+
+	<programlisting>ifconfig_ath0="ssid <replaceable>freebsdap</replaceable> mode 11g mediaopt hostap inet <replaceable>192.168.0.1</replaceable> netmask <replaceable>255.255.255.0</replaceable>"</programlisting>
+      </sect3>
+
+      <sect3>
+	<title>Host-based Access Point without Authentication or
+	  Encryption</title>
+
+	<para>Although it is not recommended to run an AP without any
+	  authentication or encryption, this is a simple way to check
+	  if your AP is working.  This configuration is also important
+	  for debugging client issues.</para>
+
+	<para>Once the AP configured as previously shown, it is
+	  possible from another wireless machine to initiate a scan to
+	  find the AP:</para>
+
+	<screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable> up scan</userinput>
+SSID            BSSID              CHAN RATE  S:N   INT CAPS
+freebsdap       00:11:95:c3:0d:ac    1   54M 22:1   100 ES</screen>
+
+	<para>The client machine found the Access Point and can be
+	  associated with it:</para>
+
+	<screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable> ssid <replaceable>freebsdap</replaceable> inet <replaceable>192.168.0.2</replaceable> netmask <replaceable>255.255.255.0</replaceable></userinput>
+&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable></userinput>
+  ath0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
+	  inet6 fe80::211:95ff:fed5:4362%ath0 prefixlen 64 scopeid 0x1
+	  inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
+	  ether 00:11:95:d5:43:62
+	  media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps)
+	  status: associated
+	  ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac
+	  authmode OPEN privacy OFF txpowmax 36 protmode CTS bintval 100</screen>
+      </sect3>
+
+      <sect3>
+	<title>WPA Host-based Access Point</title>
+
+	<para>This section will focus on setting up &os; Access Point
+	  using the WPA security protocol.  More details regarding WPA
+	  and the configuration of WPA-based wireless clients can be
+	  found in the <xref linkend="network-wireless-wpa">.</para>
+
+	<para>The <application>hostapd</application> daemon is used to
+	  deal with client authentication and keys management on the
+	  WPA enabled Access Point.</para>
+
+	<para>In the following, all the configuration operations will
+	  be performed on the &os; machine acting as AP.  Once the
+	  AP is correctly working, <application>hostapd</application>
+	  should be automatically enabled at boot with the following
+	  line in <filename>/etc/rc.conf</filename>:</para>
+
+	<programlisting>hostapd_enable="YES"</programlisting>
+
+	<para>Before trying to configure
+	  <application>hostapd</application>, be sure you have done
+	  the basic settings introduced in the <xref
+	  linkend="network-wireless-ap-basic">.</para>
+
+	<sect4>
+	  <title>WPA-PSK</title>
+
+	  <para>WPA-PSK is intended for small networks where the use
+	    of an backend authentication server is not possible or
+	    desired.</para>
+
+	  <para>The configuration is done in the
+	    <filename>/etc/hostapd.conf</filename> file:</para>
+
+	  <programlisting>interface=ath0 <co id="co-ap-wpapsk-iface">
+debug=1 <co id="co-ap-wpapsk-dbug">
+ctrl_interface=/var/run/hostapd <co id="co-ap-wpapsk-ciface">
+ctrl_interface_group=wheel <co id="co-ap-wpapsk-cifacegrp">
+ssid=freebsdap <co id="co-ap-wpapsk-ssid">
+wpa=1 <co id="co-ap-wpapsk-wpa">
+wpa_passphrase=freebsdmall <co id="co-ap-wpapsk-pass">
+wpa_key_mgmt=WPA-PSK <co id="co-ap-wpapsk-kmgmt">
+wpa_pairwise=CCMP TKIP <co id="co-ap-wpapsk-pwise"></programlisting>
+
+	  <calloutlist>
+	    <callout arearefs="co-ap-wpapsk-iface">
+	      <para>This field indicates the wireless interface used
+		for the Access Point.</para>
+	    </callout>
+
+	    <callout arearefs="co-ap-wpapsk-dbug">
+	      <para>This field sets the level of verbosity during the
+		execution of <application>hostapd</application>.  A
+		value of <literal>1</literal> represents the minimal
+		level.</para>
+	    </callout>
+
+	    <callout arearefs="co-ap-wpapsk-ciface">
+	      <para>The <literal>ctrl_interface</literal> field gives
+		the pathname of the directory used by
+		<application>hostapd</application> to stores its
+		domain socket files for the communication with
+		external programs such as &man.hostapd.cli.8;.  The
+		default value is used here.</para>
+	    </callout>
+
+	    <callout arearefs="co-ap-wpapsk-cifacegrp">




More information about the Freebsd-doc-el mailing list