View | Details | Raw Unified | Return to bug 54610
Collapse All | Expand All

(-)chapter.sgml (+21 lines)
Lines 362-367 Link Here
362
      </informaltable>
362
      </informaltable>
363
    </sect2>
363
    </sect2>
364
364
365
	<sect2>
366
		<title>Manipulate routing tables</title>
367
		<indexterm><primary>manipulate routing tables</primary></indexterm>
368
		<para>Although it is normally not needed, as there is the
369
&man.routed.8; daemon for routing table management, it is in some cases very
370
useful to be able to dynamically define or manipulate the routing tables on the
371
command line. This is achieved via the &man.route.8; command. 
372
For example, if you want to set the default route to a
373
specific ip adress, you do this by using the add parameter of the route
374
command:</para>
375
	<screen>&prompt.root;<userinput>route add default 192.168.0.1</userinput>
376
	add net default: gateway 192.168.0.1</screen>
377
	
378
379
	<para>Additional manipulation of the routing table is done via the
380
<command>change</command> and <command>delete</command> parameters. Use
381
<command>flush</command> to clear the whole routing table.
382
	To receive specific information about how packages to a certain destination get
383
	routed, there is the <command>get</command> parameter.
384
	</sect2>
385
365
    <sect2>
386
    <sect2>
366
      <title>Dual Homed Hosts</title>
387
      <title>Dual Homed Hosts</title>
367
      <indexterm><primary>dual homed hosts</primary></indexterm>
388
      <indexterm><primary>dual homed hosts</primary></indexterm>

Return to bug 54610