PERFORCE change 136888 for review

[Gabor Pali]

http://perforce.freebsd.org/chv.cgi?CH=136888

Change 136888 by pgj at disznohal on 2008/03/05 06:04:42

	Add initial Hungarian translation of Chapter 29: Advanced Networking.

Affected files ...

.. //depot/projects/docproj_hu/books/handbook/advanced-networking/chapter.sgml#4 edit

Differences ...

==== //depot/projects/docproj_hu/books/handbook/advanced-networking/chapter.sgml#4 (text+ko) ====

@@ -4,75 +4,99 @@
      $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.404 2007/12/20 22:21:44 gabor Exp $
 -->
 
-<chapter id="advanced-networking">
-  <title>Advanced Networking</title>
+<!-- The FreeBSD Hungarian Documentation Project
+     Translated by: PALI, Gabor <pgj at FreeBSD.org>
+     Original Revision: 1.404                     -->
+
+<chapter id="advanced-networking" lang="hu">
+  <title>Egy&eacute;b halad&oacute; h&aacute;l&oacute;zati
+    t&eacute;m&aacute;k</title>
 
   <sect1 id="advanced-networking-synopsis">
-    <title>Synopsis</title>
+    <title>&Aacute;ttekint&eacute;s</title>
 
-    <para>This chapter will cover a number of advanced networking
-      topics.</para>
+    <para>Ebben a fejezetben sz&aacute;mos komolyabb
+      h&aacute;l&oacute;zati t&eacute;m&aacute;t fogunk
+      t&aacute;rgyalni.</para>
 
-    <para>After reading this chapter, you will know:</para>
+    <para>A fejezet elolvas&aacute;sa sor&aacute;n
+      megismerj&uuml;k:</para>
 
     <itemizedlist>
       <listitem>
-	<para>The basics of gateways and routes.</para>
+	<para>az &aacute;tj&aacute;r&oacute;k &eacute;s az
+	  &uacute;tv&aacute;laszt&aacute;s alapjait</para>
       </listitem>
 
       <listitem>
-	<para>How to set up IEEE 802.11 and &bluetooth; devices.</para>
+	<para>hogyan &aacute;ll&iacute;tsunk be IEEE 802.11 &eacute;s
+	  &bluetooth; eszk&ouml;z&ouml;ket</para>
       </listitem>
 
       <listitem>
-	<para>How to make FreeBSD act as a bridge.</para>
+	<para>a &os; seg&iacute;ts&eacute;g&eacute;vel hogyan tudunk
+	  k&eacute;t h&aacute;l&oacute;zatot &ouml;sszek&ouml;tni
+	  h&aacute;l&oacute;zati hidakon kereszt&uuml;l</para>
       </listitem>
 
       <listitem>
-	<para>How to set up network booting on a diskless machine.</para>
+	<para>hogyan ind&iacute;tsuk h&aacute;l&oacute;zatr&oacute;l egy
+	  lemez n&eacute;lk&uuml;li g&eacute;pet</para>
       </listitem>
 
       <listitem>
-	<para>How to set up network address translation.</para>
+	<para>hogyan &aacute;ll&iacute;tsunk be h&aacute;l&oacute;zati
+	  c&iacute;mford&iacute;t&aacute;st</para>
       </listitem>
 
       <listitem>
-	<para>How to connect two computers via PLIP.</para>
+	<para>hogyan kapcsoljunk &ouml;ssze k&eacute;t
+	  sz&aacute;m&iacute;t&oacute;g&eacute;pet PLIP
+	  haszn&aacute;lat&aacute;val</para>
       </listitem>
 
       <listitem>
-	<para>How to set up IPv6 on a FreeBSD machine.</para>
+	<para>hogyan &aacute;ll&iacute;tsuk be az IPv6
+	  haszn&aacute;lat&aacute;t egy &os;-s g&eacute;pen</para>
       </listitem>
 
       <listitem>
-	<para>How to configure ATM.</para>
+	<para>hogyan &aacute;ll&iacute;tsuk be az ATM
+	  haszn&aacute;lat&aacute;t</para>
       </listitem>
 
       <listitem>
-	<para>How to enable and utilize the features of CARP, the
-	  Common Access Redundancy Protocol in &os;</para>
+	<para>hogyan enged&eacute;lyezz&uuml;k &eacute;s
+	  haszn&aacute;ljuk ki a K&ouml;z&ouml;s c&iacute;mredundancia
+	  protokollt &os;-ben</para>
       </listitem>
     </itemizedlist>
 
-    <para>Before reading this chapter, you should:</para>
+    <para>A fejezet elolvas&aacute;s&aacute;hoz aj&aacute;nlott:</para>
 
     <itemizedlist>
       <listitem>
-	<para>Understand the basics of the <filename>/etc/rc</filename> scripts.</para>
+	<para>az <filename>/etc/rc</filename> k&ouml;nyvt&aacute;rban
+	  tal&aacute;lhat&oacute; szkriptek
+	  m&#251;k&ouml;d&eacute;s&eacute;nek ismerete</para>
       </listitem>
 
       <listitem>
-	<para>Be familiar with basic network terminology.</para>
+	<para>az alapvet&#245; h&aacute;l&oacute;zati fogalmak
+	  ismerete</para>
       </listitem>
 
       <listitem>
-        <para>Know how to configure and install a new FreeBSD kernel
-          (<xref linkend="kernelconfig">).</para>
+	<para>egy &uacute;j &os; rendszermag
+	  be&aacute;ll&iacute;t&aacute;s&aacute;nak &eacute;s
+	  telep&iacute;t&eacute;s&eacute;nek ismerete (<xref
+	  linkend="kernelconfig">)</para>
       </listitem>
 
       <listitem>
-      <para>Know how to install additional third-party
-        software (<xref linkend="ports">).</para>
+	<para>a k&uuml;ls&#245; fejleszt&eacute;s&#251; szoftverek
+	  telep&iacute;t&eacute;s&eacute;nek ismerete (<xref
+	  linkend="ports">)</para>
       </listitem>
 
     </itemizedlist>
@@ -81,40 +105,53 @@
   <sect1 id="network-routing">
     <sect1info>
       <authorgroup>
-        <author>
-          <firstname>Coranth</firstname>
-      	  <surname>Gryphon</surname>
-	  <contrib>Contributed by </contrib>
-        </author>
+	<author>
+	  <firstname>Coranth</firstname>
+	  <surname>Gryphon</surname>
+	  <contrib>K&eacute;sz&iacute;tette: </contrib>
+	</author>
       </authorgroup>
     </sect1info>
-    <title>Gateways and Routes</title>
+
+    <title>&Aacute;tj&aacute;r&oacute;k &eacute;s az
+      &uacute;tv&aacute;laszt&aacute;s</title>
+
+    <indexterm><primary>&uacute;tv&aacute;laszt&aacute;s</primary></indexterm>
+    <indexterm><primary>&aacute;tj&aacute;r&oacute;</primary></indexterm>
+    <indexterm><primary>alh&aacute;l&oacute;zat</primary></indexterm>
 
-    <indexterm><primary>routing</primary></indexterm>
-    <indexterm><primary>gateway</primary></indexterm>
-    <indexterm><primary>subnet</primary></indexterm>
-    <para>For one machine to be able to find another over a network,
-      there must be a mechanism in place to describe how to get from
-      one to the other.  This is called
-      <firstterm>routing</firstterm>.  A <quote>route</quote> is a
-      defined pair of addresses: a <quote>destination</quote> and a
-      <quote>gateway</quote>.  The pair indicates that if you are
-      trying to get to this <emphasis>destination</emphasis>,
-      communicate through this <emphasis>gateway</emphasis>.  There
-      are three types of destinations: individual hosts, subnets, and
-      <quote>default</quote>.  The <quote>default route</quote> is
-      used if none of the other routes apply.  We will talk a little
-      bit more about default routes later on.  There are also three
-      types of gateways: individual hosts, interfaces (also called
-      <quote>links</quote>), and Ethernet hardware addresses (MAC
-      addresses).
-    </para>
+    <para>Egy g&eacute;p egy m&aacute;sikat &uacute;gy tud
+      megtal&aacute;lni a h&aacute;l&oacute;zaton, ha erre l&eacute;tezik
+      egy olyan mechanizmus, amely le&iacute;rja, hogyan tudunk eljutni
+      az egyikt&#245;l a m&aacute;sikig.  Ezt h&iacute;vjuk
+      <firstterm>&uacute;tv&aacute;laszt&aacute;snak</firstterm>
+      (routing).  Az <quote>&uacute;tvonal</quote> (route) c&iacute;mek
+      egy p&aacute;rjak&eacute;nt adhat&oacute; meg, egy
+      <quote>c&eacute;llal</quote> (destination) &eacute;s egy
+      <quote>&aacute;tj&aacute;r&oacute;val</quote> (gateway).  Ez a
+      p&aacute;ros mondja meg, hogy ha el akarjuk &eacute;rni ezt a
+      <emphasis>c&eacute;lt</emphasis>, akkor ezen az
+      <emphasis>&aacute;tj&aacute;r&oacute;n</emphasis> kell
+      tov&aacute;bbhaladnunk.  A c&eacute;loknak h&aacute;rom
+      t&iacute;pusa lehet: egy&eacute;ni g&eacute;pek,
+      alh&aacute;l&oacute;zatok &eacute;s az
+      <quote>alap&eacute;rtelmezett</quote>.  Az
+      <quote>alap&eacute;rtelmezett &uacute;tvonalat</quote> (default
+      route) abban az esetben alkalmazzuk, ha semelyik m&aacute;s
+      &uacute;tvonal nem megfelel&#245;.  Az alap&eacute;rtelmezett
+      &uacute;tvonalakr&oacute;l a k&eacute;s&#245;bbiekben m&eacute;g
+      besz&eacute;lni fogunk.  H&aacute;rom t&iacute;pusa van az
+      &aacute;tj&aacute;r&oacute;knak: egy&eacute;ni g&eacute;pek,
+      fel&uuml;letek (avagy <quote>linkek</quote>) &eacute;s a hardveres
+      Ethernet c&iacute;mek (MAC-c&iacute;mek).</para>
 
     <sect2>
-      <title>An Example</title>
+      <title>P&eacute;lda</title>
 
-      <para>To illustrate different aspects of routing, we will use the
-	following example from <command>netstat</command>:</para>
+      <para>Az &uacute;tv&aacute;laszt&aacute;s
+	k&uuml;l&ouml;nb&ouml;z&#245; ter&uuml;leteit a
+	k&ouml;vetkez&#245; <command>netstat</command> parancs
+	alapj&aacute;n fogjuk bemutatni:</para>
 
       <screen>&prompt.user; <userinput>netstat -r</userinput>
 Routing tables
@@ -131,76 +168,110 @@
 host2.example.com link#1             UC          0        0
 224              link#1             UC          0        0</screen>
 
-      <indexterm><primary>default route</primary></indexterm>
-      <para>The first two lines specify the default route (which we
-	will cover in the <link linkend="network-routing-default">next
-	  section</link>) and the <hostid>localhost</hostid> route.</para>
+      <indexterm><primary>alap&eacute;rtelmezett
+	&uacute;tvonal</primary></indexterm>
+
+      <para>Az els&#245; k&eacute;t sorban az alap&eacute;rtelmezett
+	&uacute;tvonalat (amir&#245;l r&eacute;szleteiben majd a <link
+	linkend="network-routing-default">k&ouml;vetkez&#245;
+	szakaszban</link> fogunk sz&oacute;lni) &eacute;s a
+	<hostid>localhost</hostid> &uacute;tvonal&aacute;t
+	l&aacute;thatjuk.</para>
+
+      <indexterm><primary>visszahurkolt
+	eszk&ouml;z</primary></indexterm>
 
-      <indexterm><primary>loopback device</primary></indexterm>
-      <para>The interface (<literal>Netif</literal> column) that this
-	routing table specifies to use for
-	<literal>localhost</literal> is <devicename>lo0</devicename>,
-	also known as the loopback device.  This says to keep all
-	traffic for this destination internal, rather than sending it
-	out over the LAN, since it will only end up back where it
-	started.</para>
+      <para>A <hostid>localhost</hostid> c&iacute;mhez az
+	&uacute;tv&aacute;laszt&aacute;si t&aacute;bl&aacute;zatban a
+	<devicename>lo0</devicename> eszk&ouml;z tartozik (a
+	<literal>Netif</literal> oszlopban), amit visszahurkolt
+	eszk&ouml;znek (loopback device) is neveznek.  Ez arra
+	utas&iacute;tja a rendszert, hogy az ide k&uuml;ld&ouml;tt
+	csomagokat ne k&uuml;ldje kereszt&uuml;l a helyi
+	h&aacute;l&oacute;zaton, hanem csak ezen a bels&#245;
+	fel&uuml;leten, mivel &uacute;gyis oda jutnak vissza, ahonnan
+	indultak.</para>
 
       <indexterm>
-        <primary>Ethernet</primary>
-        <secondary>MAC address</secondary>
+	<primary>Ethernet</primary>
+	<secondary>MAC-c&iacute;m</secondary>
       </indexterm>
-      <para>The next thing that stands out are the addresses beginning
-	with <hostid role="mac">0:e0:</hostid>.  These are Ethernet
-	hardware addresses, which are also known as MAC addresses.
-	FreeBSD will automatically identify any hosts
-	(<hostid>test0</hostid> in the example) on the local Ethernet
-	and add a route for that host, directly to it over the
-	Ethernet interface, <devicename>ed0</devicename>.  There is
-	also a timeout (<literal>Expire</literal> column) associated
-	with this type of route, which is used if we fail to hear from
-	the host in a specific amount of time.  When this happens, the
-	route to this host will be automatically deleted.  These hosts
-	are identified using a mechanism known as RIP (Routing
-	Information Protocol), which figures out routes to local hosts
-	based upon a shortest path determination.</para>
+
+      <para>A t&aacute;bl&aacute;zatban a k&ouml;vetkez&#245; sor egy
+	<hostid role="mac">0:e0</hostid> kezdet&#251; c&iacute;met
+	tartalmaz.  Ez egy hardveres Ethernet-c&iacute;m, m&aacute;s
+	n&eacute;ven MAC-c&iacute;m.  A &os; mag&aacute;t&oacute;l
+	k&eacute;pes beazonos&iacute;tani tetsz&#245;leges g&eacute;pet
+	(ebben a p&eacute;ld&aacute;ban a <hostid>test0</hostid>
+	g&eacute;pet) a helyi Ethernetes h&aacute;l&oacute;zaton
+	&eacute;s felvenni hozz&aacute; egy &uacute;tvonalat,
+	k&ouml;zvetlen&uuml;l az <devicename>ed0</devicename> Ethernetes
+	csatol&oacute;fel&uuml;leten kereszt&uuml;l.  Ehhez a
+	t&iacute;pus&uacute; &uacute;tvonalhoz tartozik m&eacute;g egy
+	lej&aacute;rati id&#245; is (a <literal>Expire</literal>
+	oszlop), ami akkor kap szerepet, ha ennyi id&#245;
+	eltelt&eacute;vel nem kapunk semmilyen h&iacute;rt a
+	g&eacute;pr&#245;l.  Amikor ilyen t&ouml;rt&eacute;nik, az
+	g&eacute;phez eddig nyilv&aacute;ntartott &uacute;tvonal
+	automatikusan t&ouml;rl&#245;dik.  Ezek a g&eacute;pek a RIP
+	(&uacute;tvonal-inform&aacute;ci&oacute;s protokoll, Routing
+	Information Protocol) nev&#251; mechanizmuson kereszt&uuml;l
+	azonos&iacute;t&oacute;dnak, mely a legr&ouml;videbb &uacute;t
+	kisz&aacute;m&iacute;t&aacute;sa alapj&aacute;n hat&aacute;rozza
+	meg a helyi g&eacute;pekhez vezet&#245; &uacute;tvonalat.</para>
+
+      <indexterm><primary>alh&aacute;l&oacute;zat</primary></indexterm>
 
-      <indexterm><primary>subnet</primary></indexterm>
-      <para>FreeBSD will also add subnet routes for the local subnet (<hostid
-	  role="ipaddr">10.20.30.255</hostid> is the broadcast address for the
-	subnet <hostid role="ipaddr">10.20.30</hostid>, and <hostid
-	  role="domainname">example.com</hostid> is the domain name associated
-	with that subnet).  The designation <literal>link#1</literal> refers
-	to the first Ethernet card in the machine.  You will notice no
-	additional interface is specified for those.</para>
+      <para>A &os; a helyi alh&aacute;l&oacute;zat (<hostid
+	role="ipaddr">10.20.30.255</hostid> &eacute;s <hostid
+	role="domainname">example.com</hostid>, az
+	alh&aacute;l&oacute;zathoz tartoz&oacute; n&eacute;v)
+	eset&eacute;ben is felvesz &uacute;tvonalakat.  A
+	<literal>link#1</literal> megnevez&eacute;s a g&eacute;pben
+	tal&aacute;lhat&oacute; els&#245; Ethernet-k&aacute;rty&aacute;t
+	jel&ouml;li.  Megfigyelhetj&uuml;k, hogy rajta k&iacute;v&uuml;l
+	nincs is t&ouml;bb fel&uuml;lete.</para>
 
-      <para>Both of these groups (local network hosts and local subnets) have
-	their routes automatically configured by a daemon called
-	<application>routed</application>.  If this is not run, then only
-	routes which are statically defined (i.e. entered explicitly) will
-	exist.</para>
+      <para>Mindegyik csoport (a helyi h&aacute;l&oacute;zati
+	g&eacute;pek &eacute;s a helyi alh&aacute;l&oacute;zatokatok)
+	&uacute;tvonalait a <application>routed</application> nev&#251;
+	d&eacute;mon tartja automatikusan karban.  Ha ez nem fut, akkor
+	csak a statikusan defini&aacute;lt (vagyis az el&#245;re
+	megadott) &uacute;tvonalak fognak l&eacute;tezni.</para>
 
-      <para>The <literal>host1</literal> line refers to our host, which it
-	knows by Ethernet address.  Since we are the sending host, FreeBSD
-	knows to use the loopback interface (<devicename>lo0</devicename>)
-	rather than sending it out over the Ethernet interface.</para>
+      <para>A <literal>host1</literal> sor a saj&aacute;t
+	g&eacute;p&uuml;nkre vonatkozik, amit az Ethernet-c&iacute;me
+	szerint ismer&uuml;nk.  Mivel mi vagyunk k&uuml;ld&#245;
+	g&eacute;p, a &os; tudni fogja, hogy ilyenkor az Ethernetes
+	fel&uuml;let helyett a visszahurkolt eszk&ouml;zt
+	(<devicename>lo0</devicename>) kell haszn&aacute;lnia.</para>
 
-      <para>The two <literal>host2</literal> lines are an example of
-	what happens when we use an &man.ifconfig.8; alias (see the
-	section on Ethernet for reasons why we would do this).  The
-	<literal>=&gt;</literal> symbol after the
-	<devicename>lo0</devicename> interface says that not only are
-	we using the loopback (since this address also refers to the
-	local host), but specifically it is an alias.  Such routes
-	only show up on the host that supports the alias; all other
-	hosts on the local network will simply have a
-	<literal>link#1</literal> line for such routes.</para>
+      <para>A k&eacute;t <literal>host2</literal> sor arra mutat
+	p&eacute;ld&aacute;t, amikor az &man.ifconfig.8; paranccsal
+	&aacute;lneveket hozunk l&eacute;tre (ennek konkr&eacute;t okait
+	ld.  az Ethernetr&#245;l sz&oacute;l&oacute; r&eacute;szben).  A
+	<devicename>lo0</devicename> fel&uuml;let neve ut&aacute;n
+	szerepl&#245; <literal>=&gt;</literal> szimb&oacute;lum azt
+	jelzi, hogy ez nem csak egy visszahurkolt fel&uuml;let (mivel a
+	c&iacute;me szint&eacute;n a helyi g&eacute;pre mutat), hanem a
+	fel&uuml;let egy m&aacute;sik neve.  Ilyen &uacute;tvonalak csak
+	az &aacute;lneveket ismer&#245; g&eacute;pekn&eacute;l jelennek
+	meg.  A helyi h&aacute;l&oacute;zaton minden m&aacute;s
+	g&eacute;pn&eacute;l egyszer&#251;en csak a
+	<literal>link#1</literal> jelenik meg az ilyen &uacute;tvonalak
+	eset&eacute;ben.</para>
 
-      <para>The final line (destination subnet <hostid role="ipaddr">224</hostid>) deals
-	with multicasting, which will be covered in another section.</para>
+      <para>Az utols&oacute; sor (a <hostid role="ipaddr">224</hostid>
+	c&eacute;llal rendelkez&#245; alh&aacute;l&oacute;zat) a
+	t&ouml;bbesk&uuml;ld&eacute;sre (multicasting) szolg&aacute;l,
+	ezzel egy m&aacute;sik szakaszban foglalkozunk.</para>
 
-      <para>Finally, various attributes of each route can be seen in
-	the <literal>Flags</literal> column.  Below is a short table
-	of some of these flags and their meanings:</para>
+      <para>V&eacute;gezet&uuml;l az &uacute;tvonalakhoz tartoz&oacute;
+	k&uuml;l&ouml;nf&eacute;le tulajdons&aacute;gok a
+	<literal>Flags</literal> oszlopban l&aacute;that&oacute;ak.  Az
+	al&aacute;bbi r&ouml;vid t&aacute;bl&aacute;zatban
+	&ouml;sszefoglaltunk k&ouml;z&uuml;l&uuml;k
+	n&eacute;h&aacute;nyat:</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
@@ -210,75 +281,100 @@
 	  <tbody>
 	    <row>
 	      <entry>U</entry>
-	      <entry>Up: The route is active.</entry>
+	      <entry>Up: az &uacute;tvonal akt&iacute;v</entry>
 	    </row>
 
 	    <row>
 	      <entry>H</entry>
-	      <entry>Host: The route destination is a single host.</entry>
+	      <entry>Host: az &uacute;tvonal egyetlen g&eacute;pre
+		mutat</entry>
 	    </row>
 
 	    <row>
 	      <entry>G</entry>
-	      <entry>Gateway: Send anything for this destination on to this
-		remote system, which will figure out from there where to send
-		it.</entry>
+	      <entry>Gateway: az adott c&eacute;l fel&eacute; ezen a
+		g&eacute;pen kereszt&uuml;l k&uuml;ldj&uuml;nk, ami majd
+		kital&aacute;lja, hogy merre k&uuml;ldje
+		tov&aacute;bb</entry>
 	    </row>
 
 	    <row>
 	      <entry>S</entry>
-	      <entry>Static: This route was configured manually, not
-		automatically generated by the system.</entry>
+	      <entry>Static: ez az &uacute;tvonal statikus, nem a
+		rendszer hozta l&eacute;tre automatikusan</entry>
 	    </row>
 
 	    <row>
 	      <entry>C</entry>
-	      <entry>Clone: Generates a new route based upon this route for
-		machines we connect to.  This type of route is normally used
-		for local networks.</entry>
+	      <entry>Clone: ebb&#245;l az &uacute;tvonalb&oacute;l
+		sz&aacute;rmaztatunk &uacute;j &uacute;tvonalat azokhoz a
+		g&eacute;pekhez, amikhez csatlakozunk.  Ilyen
+		&uacute;tvonalakat &aacute;ltal&aacute;ban a helyi
+		h&aacute;l&oacute;zatokban tal&aacute;lhatunk</entry>
 	    </row>
 
 	    <row>
 	      <entry>W</entry>
-	      <entry>WasCloned: Indicated a route that was auto-configured
-		based upon a local area network (Clone) route.</entry>
+	      <entry>WasCloned: azt jelzi, hogy ezt az &uacute;tvonalat
+		egy helyi h&aacute;l&oacute;zatra mutat&oacute;
+		(kl&oacute;n, avagy Clone t&iacute;pus&uacute;)
+		&uacute;tvonal alapj&aacute;n hoztuk l&eacute;tre
+		automatikusan</entry>
 	    </row>
 
 	    <row>
 	      <entry>L</entry>
-	      <entry>Link: Route involves references to Ethernet
-		hardware.</entry>
+	      <entry>Link: az &uacute;tvonal Ethernetes hardverhez
+		kapcsol&oacute;dik</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
+
     </sect2>
 
     <sect2 id="network-routing-default">
-      <title>Default Routes</title>
+      <title>Alap&eacute;rtelmezett &uacute;tvonalak</title>
+
+      <indexterm><primary>alap&eacute;rtelmezett
+	&uacute;tvonal</primary></indexterm>
 
-      <indexterm><primary>default route</primary></indexterm>
-      <para>When the local system needs to make a connection to a remote host,
-	it checks the routing table to determine if a known path exists.  If
-	the remote host falls into a subnet that we know how to reach (Cloned
-	routes), then the system checks to see if it can connect along that
-	interface.</para>
+      <para>Amikor a helyi rendszernek fel kell vennie a kapcsolatot egy
+	t&aacute;voli g&eacute;ppel, ellen&#245;rzi az
+	&uacute;tv&aacute;laszt&aacute;si t&aacute;bl&aacute;zatban,
+	hogy l&eacute;tezik-e m&aacute;r hozz&aacute; valamilyen
+	&uacute;tvonal.  Ha a t&aacute;voli g&eacute;p egy olyan
+	alh&aacute;l&oacute;zatba esik, amit m&aacute;r el tudunk
+	&eacute;rni (kl&oacute;nozott &uacute;tvonalak), akkor a
+	rendszer megn&eacute;zi, hogy a hozz&aacute;tartoz&oacute;
+	fel&uuml;leten k&eacute;pes-e kapcsolatot
+	l&eacute;tes&iacute;teni.</para>
 
-      <para>If all known paths fail, the system has one last option: the
-	<quote>default</quote> route.  This route is a special type of gateway
-	route (usually the only one present in the system), and is always
-	marked with a <literal>c</literal> in the flags field.  For hosts on a
-	local area network, this gateway is set to whatever machine has a
-	direct connection to the outside world (whether via PPP link,
-	DSL, cable modem, T1, or another network interface).</para>
+      <para>Ha minden ismert &uacute;tvonal cs&#245;d&ouml;t mond, akkor
+	a rendszer&uuml;nknek marad m&eacute;g egy utols&oacute;
+	es&eacute;lye: az <quote>alap&eacute;rtelmezett</quote>
+	&uacute;tvonal haszn&aacute;lata.  Ez az &uacute;tvonal egy
+	speci&aacute;lis &aacute;tj&aacute;r&oacute; &uacute;tvonal
+	(amib&#245;l &aacute;ltal&aacute;ban csak egyetlen egy
+	l&eacute;tezik a rendszerben) &eacute;s tulajdons&aacute;gai
+	k&ouml;z&ouml;tt mindig szerepel a <literal>c</literal>.  A
+	helyi h&aacute;l&oacute;zat g&eacute;pei k&ouml;z&uuml;l ez az
+	&aacute;tj&aacute;r&oacute; az legyen, amelyik
+	k&ouml;zvetlen&uuml;l kapcsol&oacute;dik a k&uuml;ls&#245;
+	vil&aacute;ghoz (PPP &ouml;sszek&ouml;ttet&eacute;ssel, DSL,
+	k&aacute;belmodem, T1 vagy b&aacute;rmilyen m&aacute;s
+	h&aacute;l&oacute;zati fel&uuml;leten kereszt&uuml;l).</para>
 
-      <para>If you are configuring the default route for a machine which
-	itself is functioning as the gateway to the outside world, then the
-	default route will be the gateway machine at your Internet Service
-	Provider's (ISP) site.</para>
+      <para>Amikor pedig mag&aacute;t a k&uuml;ls&#245; vil&aacute;g
+	fel&eacute; &aacute;tj&aacute;r&oacute;k&eacute;nt
+	szolg&aacute;l&oacute; g&eacute;pet &aacute;ll&iacute;tjuk be,
+	az alap&eacute;rtelmezett &uacute;tvonal az internet
+	szolg&aacute;ltat&oacute;nk &aacute;ltal megadott g&eacute;p
+	c&iacute;me lesz.</para>
 
-      <para>Let us look at an example of default routes.  This is a common
-	configuration:</para>
+      <para>Vegy&uuml;nk egy p&eacute;ld&aacute;t az
+	alap&eacute;rtelmezett &uacute;tvonalakra.  Egy tipikus
+	konfigur&aacute;ci&oacute;:</para>
 
       <mediaobject>
 	<imageobject>
@@ -287,165 +383,236 @@
 
 	<textobject>
 	  <literallayout class="monospaced">
-[Local2]  &lt;--ether--&gt;  [Local1]  &lt;--PPP--&gt; [ISP-Serv]  &lt;--ether--&gt;  [T1-GW]
+[Helyi2]  &lt;--ether--&gt;  [Helyi1]  &lt;--PPP--&gt; [ Szolg. ]  &lt;--ether--&gt;  [T1-&Aacute;J]
       </literallayout>
 	</textobject>
       </mediaobject>
 
-      <para>The hosts <hostid>Local1</hostid> and
-	<hostid>Local2</hostid> are at your site.
-	<hostid>Local1</hostid> is connected to an ISP via a dial up
-	PPP connection.  This PPP server computer is connected through
-	a local area network to another gateway computer through an
-	external interface to the ISPs Internet feed.</para>
+      <para>A <hostid>Helyi1</hostid> &eacute;s <hostid>Helyi2</hostid>
+	g&eacute;pek a h&aacute;l&oacute;zatunk tagjai.  A
+	<hostid>Helyi1</hostid> az internet szolg&aacute;ltat&oacute;t
+	&eacute;ri el egy bet&aacute;rcs&aacute;z&oacute;s PPP
+	kapcsolaton kereszt&uuml;l.  A PPP szerver a k&uuml;ls&#245;
+	fel&uuml;let&eacute;n kereszt&uuml;l a helyi
+	h&aacute;l&oacute;zaton pedig egy m&aacute;sik
+	&aacute;tj&aacute;r&oacute;hoz csatlakozik.</para>
 
-      <para>The default routes for each of your machines will be:</para>
+      <para>Az egyes g&eacute;pek alap&eacute;rtelmezett
+	&uacute;tvonalai &iacute;gy alakulnak:</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="3">
 	  <thead>
 	    <row>
-	      <entry>Host</entry>
-	      <entry>Default Gateway</entry>
-	      <entry>Interface</entry>
+	      <entry>G&eacute;p</entry>
+	      <entry>Alap&eacute;rtelmezett
+		&aacute;tj&aacute;r&oacute;</entry>
+	      <entry>Fel&uuml;let</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
-	      <entry>Local2</entry>
-	      <entry>Local1</entry>
+	      <entry>Helyi2</entry>
+	      <entry>Helyi1</entry>
 	      <entry>Ethernet</entry>
 	    </row>
 
 	    <row>
-	      <entry>Local1</entry>
-	      <entry>T1-GW</entry>
+	      <entry>Helyi1</entry>
+	      <entry>T1-&Aacute;J</entry>
 	      <entry>PPP</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
-      <para>A common question is <quote>Why (or how) would we set
-	the <hostid>T1-GW</hostid> to be the default gateway for
-	<hostid>Local1</hostid>, rather than the ISP server it is
-	connected to?</quote>.</para>
+      <para>Gyakran felmer&uuml;l a k&eacute;rd&eacute;s, hogy
+	<quote>Mi&eacute;rt (&eacute;s hogy-hogy) a
+	<hostid>T1-&Aacute;J</hostid> a <hostid>Helyi1</hostid>
+	g&eacute;p sz&aacute;m&aacute;ra az alap&eacute;rtelmezett
+	&aacute;tj&aacute;r&oacute; &eacute;s nem a
+	szolg&aacute;ltat&oacute; azon szervere, amihez
+	csatlakozott?</quote></para>
 
-      <para>Remember, since the PPP interface is using an address on the ISP's
-	local network for your side of the connection, routes for any other
-	machines on the ISP's local network will be automatically generated.
-	Hence, you will already know how to reach the <hostid>T1-GW</hostid>
-	machine, so there is no need for the intermediate step
-	of sending traffic to the ISP server.</para>
+      <para>Ne felejts&uuml;k el, hogy a PPP fel&uuml;let a
+	szolg&aacute;ltat&oacute; helyi h&aacute;l&oacute;zat&aacute;ban a
+	mi r&eacute;sz&uuml;nkre kap c&iacute;met, &eacute;s a itt az
+	&ouml;sszes t&ouml;bbi g&eacute;phez tartoz&oacute;
+	&uacute;tvonal automatikusan l&eacute;trej&ouml;n.  Emiatt
+	m&aacute;r eleve el tudjuk &eacute;rni a
+	<hostid>T1-&Aacute;J</hostid> g&eacute;pet, ez&eacute;rt amikor
+	a szolg&aacute;ltat&oacute;n kereszt&uuml;l k&uuml;ld&uuml;nk,
+	nincs sz&uuml;ks&eacute;g&uuml;nk egy tov&aacute;bbi
+	l&eacute;pcs&#245;re.</para>
 
-      <para>It is common to use the address <hostid
-	  role="ipaddr">X.X.X.1</hostid> as the gateway address for your local
-	network.  So (using the same example), if your local class-C address
-	space was <hostid role="ipaddr">10.20.30</hostid> and your ISP was
-	using <hostid role="ipaddr">10.9.9</hostid> then the default routes
-	would be:</para>
+      <para>&Aacute;ltal&aacute;ban a <hostid
+	role="ipaddr">X.X.X.1</hostid> c&iacute;met szokt&aacute;k a helyi
+	h&aacute;l&oacute;zat &aacute;tj&aacute;r&oacute;j&aacute;nak
+	kiosztani.  Ez&eacute;rt (az el&#245;bbi p&eacute;ld&aacute;t
+	&uacute;jrahasznos&iacute;tva) ha a helyi
+	h&aacute;l&oacute;zatunkon a C oszt&aacute;ly&uacute; <hostid
+	role="ipaddr">10.20.30</hostid> c&iacute;mtartom&aacute;nyt
+	haszn&aacute;ljuk, &eacute;s a szolg&aacute;ltat&oacute;nkhoz a
+	<hostid role="ipaddr">10.9.9</hostid> c&iacute;mtartom&aacute;ny
+	tartozik, akkor az alap&eacute;rtelmezett &uacute;tvonalak a
+	k&ouml;vetkez&#245;k lesznek:</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
-	      <entry>Host</entry>
-	      <entry>Default Route</entry>
+	      <entry>G&eacute;p</entry>
+	      <entry>Alap&eacute;rtelmezett &uacute;tvonal</entry>
 	    </row>
 	  </thead>
 	  <tbody>
 	    <row>
-	      <entry>Local2 (10.20.30.2)</entry>
-	      <entry>Local1 (10.20.30.1)</entry>
+	      <entry>Helyi2 (10.20.30.2)</entry>
+	      <entry>Helyi1 (10.20.30.1)</entry>
 	    </row>
 	    <row>
-	      <entry>Local1 (10.20.30.1, 10.9.9.30)</entry>
-	      <entry>T1-GW (10.9.9.1)</entry>
+	      <entry>Helyi1 (10.20.30.1, 10.9.9.30)</entry>
+	      <entry>T1-&Aacute;J (10.9.9.1)</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
-      <para>You can easily define the default route via the
-	<filename>/etc/rc.conf</filename> file.  In our example, on the
-	<hostid>Local2</hostid> machine, we added the following line
-	in <filename>/etc/rc.conf</filename>:</para>
+      <para>Az <filename>/etc/rc.conf</filename>
+	&aacute;llom&aacute;nyon kereszt&uuml;l k&ouml;nnyen meg tudjuk
+	adni az alap&eacute;rtelmezett &uacute;tvonalat.  A
+	p&eacute;ld&aacute;nkban a <hostid>Helyi2</hostid> g&eacute;p
+	<filename>/etc/rc.conf</filename>
+	&aacute;llom&aacute;ny&aacute;ba kell felvenn&uuml;nk a
+	k&ouml;vetkez&#245; sort:</para>
 
       <programlisting>defaultrouter="10.20.30.1"</programlisting>
 
-      <para>It is also possible to do it directly from the command
-	line with the &man.route.8; command:</para>
+      <para>De a &man.route.8; parancs haszn&aacute;lat&aacute;val
+	ak&aacute;r k&ouml;zvetlen&uuml;l is megtehetj&uuml;k
+	mindezt:</para>
 
       <screen>&prompt.root; <userinput>route add default 10.20.30.1</userinput></screen>
 
-      <para>For more information on manual manipulation of network
-	routing tables, consult &man.route.8; manual page.</para>
+      <para>A h&aacute;l&oacute;zati &uacute;tv&aacute;laszt&aacute;si
+	t&aacute;bl&aacute;zatok k&eacute;zzel t&ouml;rt&eacute;n&#245;
+	m&oacute;dos&iacute;t&aacute;s&aacute;r&oacute;l a &man.route.8;
+	man oldalon olvashatunk b&#245;vebben.</para>
+
     </sect2>
 
     <sect2>
-      <title>Dual Homed Hosts</title>
-      <indexterm><primary>dual homed hosts</primary></indexterm>
-      <para>There is one other type of configuration that we should cover, and
-	that is a host that sits on two different networks.  Technically, any
-	machine functioning as a gateway (in the example above, using a PPP
-	connection) counts as a dual-homed host.  But the term is really only
-	used to refer to a machine that sits on two local-area
-	networks.</para>
+      <title>Kett&#245;s h&aacute;l&oacute;zat&uacute;
+	g&eacute;pek</title>
+
+      <indexterm><primary>kett&#245;s h&aacute;l&oacute;zat&uacute;
+	g&eacute;pek</primary></indexterm>
+
+      <para>Egy m&aacute;sik t&iacute;pus&uacute;
+	konfigur&aacute;ci&oacute;r&oacute;l is sz&oacute;t kell
+	ejten&uuml;nk, ahol a g&eacute;p egyszerre k&eacute;t
+	h&aacute;l&oacute;zatnak is tagja.  Gyakorlatilag az
+	&aacute;tj&aacute;r&oacute;k&eacute;nt &uuml;zemel&#245;
+	sz&aacute;m&iacute;t&oacute;g&eacute;pek (mint mondjuk az, ami a
+	fenti p&eacute;ld&aacute;ban PPP kapcsolattal csatlakozott)
+	ilyen kett&#245;s h&aacute;l&oacute;zat&uacute; g&eacute;pnek
+	tekinthet&#245;ek.  De ez a kifejez&eacute;s
+	igaz&aacute;b&oacute;l csak azokra az esetekre illik, ahol a
+	g&eacute;p egyszerre k&eacute;t helyi h&aacute;l&oacute;zatban
+	is megjelenik.</para>
+
+      <para>Az egyik esetben a g&eacute;pben k&eacute;t
+	Ethernet-k&aacute;rtya tal&aacute;lhat&oacute;, melyek mindegyike
+	birtokol egy-egy h&aacute;l&oacute;zati c&iacute;met az egyes
+	alh&aacute;l&oacute;zatokon.  De el&#245;fordulhat az is, hogy a
+	g&eacute;p&uuml;nkben csup&aacute;n egyetlen
+	Ethernet-k&aacute;rtya van &eacute;s az &man.ifconfig.8;
+	seg&iacute;ts&eacute;g&eacute;vel &aacute;lneveket hoztunk
+	l&eacute;tre hozz&aacute;.  Az el&#245;bbi
+	&aacute;ltal&aacute;ban k&eacute;t fizikailag
+	elk&uuml;l&ouml;n&ouml;l&#245; Ethernet alap&uacute;
+	h&aacute;l&oacute;zat eset&eacute;ben t&ouml;rt&eacute;nik,
+	m&iacute;g az ut&oacute;bbin&aacute;l csak egyetlen fizikai
+	h&aacute;l&oacute;zati szegmensr&#245;l van sz&oacute;, ami
+	viszont logikailag k&eacute;t k&uuml;l&ouml;n
+	alh&aacute;l&oacute;zatot tartalmaz.</para>
 
-      <para>In one case, the machine has two Ethernet cards, each
-	having an address on the separate subnets.  Alternately, the
-	machine may only have one Ethernet card, and be using
-	&man.ifconfig.8; aliasing.  The former is used if two
-	physically separate Ethernet networks are in use, the latter
-	if there is one physical network segment, but two logically
-	separate subnets.</para>
+      <para>Ak&aacute;rmelyiket is vessz&uuml;k, az
+	&uacute;tv&aacute;laszt&aacute;si t&aacute;bl&aacute;zatok
+	&uacute;gy j&ouml;nnek l&eacute;tre, hogy a g&eacute;p a
+	m&aacute;sik alh&aacute;l&oacute;zat fel&eacute;
+	&aacute;tj&aacute;r&oacute;k&eacute;nt (bej&ouml;v&#245;
+	&uacute;tvonalk&eacute;nt) lesz nyilv&aacute;ntartva.  Ebben a
+	konfigur&aacute;ci&oacute;ban a g&eacute;p a k&eacute;t
+	alh&aacute;l&oacute;zat k&ouml;z&ouml;tt
+	&uacute;tv&aacute;laszt&oacute;k&eacute;nt fog
+	tev&eacute;kenykedni, &eacute;s gyakran valamelyik vagy
+	&eacute;ppen mind a k&eacute;t ir&aacute;nyba be kell
+	&aacute;ll&iacute;tanunk valamilyen csomagsz&#251;r&eacute;st
+	vagy t&#251;zfalaz&aacute;st.</para>
 
-      <para>Either way, routing tables are set up so that each subnet knows
-	that this machine is the defined gateway (inbound route) to the other
-	subnet.  This configuration, with the machine acting as a router
-	between the two subnets, is often used when we need to implement
-	packet filtering or firewall security in either or both
-	directions.</para>
+      <para>Ha azt szeretn&eacute;nk, hogy ez a g&eacute;p a k&eacute;t
+	fel&uuml;let k&ouml;z&ouml;tt tov&aacute;bb&iacute;tson
+	csomagokat, akkor a &os;-ben k&uuml;l&ouml;n enged&eacute;lyezni
+	kell ezt a lehet&#245;s&eacute;get.  A k&ouml;vetkez&#245;
+	szakaszban ennek r&eacute;szleteit t&aacute;rjuk fel.</para>
 
-      <para>If you want this machine to actually forward packets
-        between the two interfaces, you need to tell FreeBSD to enable
-        this ability.  See the next section for more details on how
-	to do this.</para>
     </sect2>
 
     <sect2 id="network-dedicated-router">
-      <title>Building a Router</title>
+      <title>Az &uacute;tv&aacute;laszt&oacute;k
+	be&aacute;ll&iacute;t&aacute;sa</title>
+
+      <indexterm><primary>&uacute;tv&aacute;laszt&oacute;</primary></indexterm>
 
-      <indexterm><primary>router</primary></indexterm>
+      <para>A h&aacute;l&oacute;zati &uacute;tv&aacute;laszt&oacute; nem
+	csin&aacute;l m&aacute;st, csak tov&aacute;bbk&uuml;ldi az egyik
+	fel&uuml;let&eacute;n be&eacute;rkez&#245; csomagokat egy
+	m&aacute;sik fel&uuml;let&eacute;re.  Az internetes
+	szabv&aacute;nyok &eacute;s a sok&eacute;ves m&eacute;rn&ouml;ki
+	tapasztalat azonban nem engedik, hogy a &os; projekt
+	alap&eacute;rtelmez&eacute;s szerint is
+	el&eacute;rhet&#245;v&eacute; tegye ezt a &os; rendszerekben.
+	Ezt a lehet&#245;s&eacute;get az al&aacute;bbi
+	v&aacute;ltoz&oacute; <literal>YES</literal>
+	&eacute;rt&eacute;k&#251;re
+	&aacute;ll&iacute;t&aacute;s&aacute;val lehet
+	enged&eacute;lyezni az &man.rc.conf.5;
+	&aacute;llom&aacute;nyban:</para>
 
-      <para>A network router is simply a system that forwards packets
-	from one interface to another.  Internet standards and good
-	engineering practice prevent the FreeBSD Project from enabling
-	this by default in FreeBSD.  You can enable this feature by
-	changing the following variable to <literal>YES</literal> in
-	&man.rc.conf.5;:</para>
+      <programlisting>gateway_enable=YES          # Ez legyen YES, ha &aacute;tj&aacute;r&oacute;k&eacute;nt akarunk &uuml;zemelni</programlisting>
 
-      <programlisting>gateway_enable=YES          # Set to YES if this host will be a gateway</programlisting>
+      <para>Ezzel l&eacute;nyeg&eacute;ben a
+	<varname>net.inet.ip.forwarding</varname> &man.sysctl.8;
+	v&aacute;ltoz&oacute; &eacute;rt&eacute;k&eacute;t
+	&aacute;ll&iacute;tjuk <literal>1</literal>-re.  Ha
+	valami&eacute;rt egy id&#245;re sz&uuml;neteltetni akarjuk a
+	csomagok tov&aacute;bbk&uuml;ld&eacute;s&eacute;t, akkor
+	&aacute;ll&iacute;tsuk a v&aacute;ltoz&oacute;t
+	&eacute;rt&eacute;k&eacute;t <literal>0</literal>-ra.</para>
 
-      <para>This option will set the &man.sysctl.8; variable
-	<varname>net.inet.ip.forwarding</varname> to
-	<literal>1</literal>.  If you should need to stop routing
-	temporarily, you can reset this to <literal>0</literal> temporarily.</para>
+      <para>Az &uacute;j &uacute;tv&aacute;laszt&oacute;nak nem
+	&aacute;rt arr&oacute;l sem tudnia, hogy merre
+	tov&aacute;bb&iacute;tsa a forgalmat.  Ha el&eacute;g
+	egyszer&#251; a h&aacute;l&oacute;zatunk, akkor ak&aacute;r
+	statikus &uacute;tvonalakat is haszn&aacute;lhatunk.  A &os;
+	alapb&oacute;l tartalmazza a BSD-k eset&eacute;n
+	szabv&aacute;nyos &man.routed.8; &uacute;tv&aacute;laszt&oacute;
+	d&eacute;mont, ami a RIP (v1 &eacute;s v2) valamint az IRDP
+	megold&aacute;sokat ismeri.  A BGP v4, OSPF v2 &eacute;s a
+	t&ouml;bbi fejlettebb &uacute;tv&aacute;laszt&aacute;si
+	protokoll a <filename role="package">net/zebra</filename>
+	csomagban &eacute;rhet&#245; el.  Az ett&#245;l bonyolultabb
+	h&aacute;l&oacute;zati &uacute;tv&aacute;laszt&aacute;si
+	feladatokhoz olyan kereskedelmi term&eacute;kek is
+	el&eacute;rhet&#245;ek, mint mondjuk a
+	<application>&gated;</application>.</para>
 
-      <para>Your new router will need routes to know where to send the
-	traffic.  If your network is simple enough you can use static
-	routes.  FreeBSD also comes with the standard BSD routing
-	daemon &man.routed.8;, which speaks RIP (both version 1 and
-	version 2) and IRDP.  Support for BGP v4, OSPF v2, and other
-	sophisticated routing protocols is available with the
-	<filename role="package">net/zebra</filename> package.
-	Commercial products such as <application>&gated;</application> are also available for more
-	complex network routing solutions.</para>
+      <indexterm><primary>BGP</primary></indexterm>
+      <indexterm><primary>RIP</primary></indexterm>
+      <indexterm><primary>OSPF</primary></indexterm>
 
-<indexterm><primary>BGP</primary></indexterm>
-<indexterm><primary>RIP</primary></indexterm>
-<indexterm><primary>OSPF</primary></indexterm>
     </sect2>
 
     <sect2>
@@ -454,17 +621,19 @@
 	  <author>
 	    <firstname>Al</firstname>
 	    <surname>Hoang</surname>
-	    <contrib>Contributed by </contrib>
+	    <contrib>&Iacute;rta: </contrib>
 	  </author>
 	</authorgroup>
       </sect2info>
-      <!-- Feb 2004 -->
-      <title>Setting Up Static Routes</title>
+
+      <title>Statikus &uacute;tvonalak
+	be&aacute;ll&iacute;t&aacute;sa</title>
 
       <sect3>
-	<title>Manual Configuration</title>
+	<title>Manu&aacute;lis konfigur&aacute;ci&oacute;</title>
 
-	<para>Let us assume we have a network as follows:</para>
+	<para>Tegy&uuml;k fel, hogy h&aacute;l&oacute;zatunk a
+	  k&ouml;vetkez&#245;:</para>
 
 	<mediaobject>
 	  <imageobject>
@@ -474,45 +643,52 @@
 	  <textobject>
 	<literallayout class="monospaced">
     INTERNET
-      | (10.0.0.1/24) Default Router to Internet
+      | (10.0.0.1/24) alap&eacute;rtelmezett &aacute;tj&aacute;r&oacute; az internetre
       |
-      |Interface xl0
+      |az xl0 fel&uuml;let
       |10.0.0.10/24
    +------+
-   |      | RouterA
-   |      | (FreeBSD gateway)
+   |      | A-utvalaszto
+   |      | (FreeBSD &aacute;tj&aacute;r&oacute;)
    +------+
-      | Interface xl1
+      | az xl1 fel&uuml;let
       | 192.168.1.1/24
       |
   +--------------------------------+
-   Internal Net 1      | 192.168.1.2/24
+   1. bels&#245; h&aacute;l&oacute;zat    | 192.168.1.2/24
                        |
                    +------+
-                   |      | RouterB
+                   |      | B-utvalaszto
                    |      |
                    +------+
                        | 192.168.2.1/24
                        |
-                     Internal Net 2
+                     2. bels&#245; h&aacute;l&oacute;zat
 	</literallayout>
 	  </textobject>
 	</mediaobject>
 
-	<para>In this scenario, <hostid>RouterA</hostid> is our &os;
-	  machine that is acting as a router to the rest of the
-	  Internet.  It has a default route set to <hostid
-	  role="ipaddr">10.0.0.1</hostid> which allows it to connect
-	  with the outside world.  We will assume that
-	  <hostid>RouterB</hostid> is already configured properly and
-	  knows how to get wherever it needs to go.  (This is simple
-	  in this picture.  Just add a default route on
-	  <hostid>RouterB</hostid> using <hostid
-	  role="ipaddr">192.168.1.1</hostid> as the gateway.)</para>
+	<para>Ebben a forgat&oacute;k&ouml;nyvben az
+	  <hostid>A-utvalaszto</hostid> a mi &os;-s g&eacute;p&uuml;nk,
+	  ami az internet fel&eacute; vezet&#245;
+	  &uacute;tv&aacute;laszt&oacute; szerep&eacute;t
+	  j&aacute;tssza.  Sz&aacute;m&aacute;ra az
+	  alap&eacute;rtelmezett &uacute;tvonal a <hostid
+	  role="ipaddr">10.0.0.1</hostid>, amin kereszt&uuml;l a
+	  k&uuml;ls&#245; vil&aacute;got tudja el&eacute;rni.
+	  Felt&eacute;telezz&uuml;k, hogy a
+	  <hostid>B-utvalaszto</hostid>-t m&aacute;r eleve j&oacute;l
+	  &aacute;ll&iacute;tottuk be, tudja merre kell mennie.  (A
+	  k&eacute;p alapj&aacute;n egyszer&#251;: csak vegy&uuml;nk fel
+	  egy alap&eacute;rtelmezett &uacute;tvonalat a
+	  <hostid>B-utvalaszto</hostid> g&eacute;phez, ahol &iacute;gy a
+	  <hostid role="ipaddr">192.168.1.1</hostid> lesz az
+	  &aacute;tj&aacute;r&oacute;.)</para>
 
-	<para>If we look at the routing table for
-	  <hostid>RouterA</hostid> we would see something like the
-	  following:</para>
+	<para>Ha megn&eacute;zz&uuml;k most az
+	  <hostid>A-utvalaszto</hostid> &uacute;tv&aacute;laszt&aacute;si
+	  t&aacute;bl&aacute;zat&aacute;t, akkor nagyj&aacute;b&oacute;l
+	  a k&ouml;vetkez&#245;ket fogjuk l&aacute;tni:</para>
 
 	<screen>&prompt.user; <userinput>netstat -nr</userinput>
 Routing tables
@@ -524,139 +700,223 @@
 10.0.0/24          link#1             UC          0        0    xl0
 192.168.1/24       link#2             UC          0        0    xl1</screen>
 
-	<para>With the current routing table  <hostid>RouterA</hostid>
-	  will not be able to reach our Internal Net 2.  It does not
-	  have a route for <hostid
-	  role="ipaddr">192.168.2.0/24</hostid>.  One way to alleviate
-	  this is to manually add the route.  The following command
-	  would add the Internal Net 2 network to
-	  <hostid>RouterA</hostid>'s routing table using <hostid
-	  role="ipaddr">192.168.1.2</hostid> as the next hop:</para>
+	<para>Az <hostid>A-utvalaszto</hostid>
+	  &uacute;tv&aacute;laszt&aacute;si t&aacute;bl&aacute;zata
+	  alapj&aacute;n jelen helyzetben nem lehet el&eacute;rni a 2.
+	  bels&#245; h&aacute;l&oacute;zatot.  Nincs olyan
+	  &uacute;tvonal, ami a <hostid
+	  role="ipaddr">192.168.2.0/24</hostid> alh&aacute;l&oacute;zat
+	  fel&eacute; vezetne.  Ezt p&eacute;ld&aacute;ul &uacute;gy
+	  tudjuk megoldani, ha manu&aacute;lisan felvessz&uuml;k ezt az
+	  &uacute;tvonalat.  Az al&aacute;bbi paranccsal
+	  hozz&aacute;adjuk a 2.  bels&#245; h&aacute;l&oacute;zat
+	  el&eacute;r&eacute;s&eacute;t az <hostid>A-utvalaszto</hostid>
+	  &uacute;tv&aacute;laszt&aacute;si
+	  t&aacute;bl&aacute;zat&aacute;hoz, ahol a <hostid
+	  role="ipaddr">192.168.1.2</hostid> lesz a k&ouml;vetkez&#245;
+	  ugr&aacute;si pont (next hop):</para>
 
 	<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
+	<para>Most m&aacute;r az <hostid>A-utvalaszto</hostid>
+	  b&aacute;rmelyik g&eacute;pet k&eacute;pes el&eacute;rni a
 	  <hostid role="ipaddr">192.168.2.0/24</hostid>
-	  network.</para>
+	  h&aacute;l&oacute;zaton.</para>
+
       </sect3>
 
       <sect3>
-	<title>Persistent Configuration</title>
+	<title>R&ouml;gz&iacute;tett konfigur&aacute;ci&oacute;</title>
 
-	<para>The above example is perfect for configuring a static
-	  route on a running system.  However, one problem is that the
-	  routing information will not persist if you reboot your &os;

>>> TRUNCATED FOR MAIL (1000 lines) <<<