os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Squeeze multiple <screen> lines into one <screen> element.

Browse source 
Add <hostid> and missing <para> tags.
This commit is contained in:
Martin Heinen 2003-01-06 16:24:12 +00:00
parent 788fd752e8
commit 8805eefc3f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=15558
1 changed files with 22 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

43
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -316,14 +316,14 @@ host2.example.com link#1 UC 0 0
</tgroup>
</informaltable>
<para>A common question is <quote>Why (or how) would we set the T1-GW to
be the default gateway for Local1, rather than the ISP server it is
<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>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 T1-GW machine, so there
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>
@ -555,17 +555,17 @@ wi0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
<para>Now that you have the bridging stuff done, we need to tell the FreeBSD
kernel which interfaces to bridge together. We do that by using &man.sysctl.8;:</para>
<screen>&prompt.root; <userinput>sysctl net.link.ether.bridge=1</userinput></screen>
<screen>&prompt.root; <userinput>sysctl net.link.ether.bridge_cfg="wi0 xl0"</userinput></screen>
<screen>&prompt.root; <userinput>sysctl net.inet.ip.forwarding=1</userinput></screen>
<screen>&prompt.root; <userinput>sysctl net.link.ether.bridge=1</userinput>
&prompt.root; <userinput>sysctl net.link.ether.bridge_cfg="wi0 xl0"</userinput>
&prompt.root; <userinput>sysctl net.inet.ip.forwarding=1</userinput></screen>
<para>Now it is time for the wireless card setup.</para>
<para>The following commands will set the card into BSS mode (turning it
into an access point):</para>
<screen>&prompt.root; <userinput>wicontrol -s "FreeBSD AP" -t 3 -n "my_net"</userinput></screen>
<screen>&prompt.root; <userinput>ifconfig wi0 inet up ssid my_net mediaopt hostap</userinput></screen>
<screen>&prompt.root; <userinput>wicontrol -p 6</userinput></screen>
<screen>&prompt.root; <userinput>wicontrol -s "FreeBSD AP" -t 3 -n "my_net"</userinput>
&prompt.root; <userinput>ifconfig wi0 inet up ssid my_net mediaopt hostap</userinput>
&prompt.root; <userinput>wicontrol -p 6</userinput></screen>
<para>The first &man.wicontrol.8; command tells FreeBSD that the name of this access point
is <literal>FreeBSD AP</literal> by using the <option>-s</option> flag, to use auto rate selection at the
@ -644,11 +644,11 @@ wi0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
just as if you were connected using a standard wired connection.</para>
<para>If you are experiencing problems with your wireless connection, check to make
sure that your are associated (connected) to the access point:
sure that your are associated (connected) to the access point:</para>
<screen>&prompt.root; <userinput>ifconfig wi0</userinput></screen>
should return some information, and you should see:</para>
<para>should return some information, and you should see:</para>
<screen>status: associated</screen>
<para>If it does not show associated, then you may be out of range of the access point, do not have
@ -6435,11 +6435,11 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<para>Here is a typical example on setting up a &man.gif.4; tunnel:</para>
<screen>&prompt.root; <userinput>ifconfig gif0 create</userinput></screen>
<screen>&prompt.root; <userinput>ifconfig gif0</userinput></screen>
<screen>gif0: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1280</screen>
<screen>&prompt.root; <userinput>ifconfig gif0 tunnel MY_IPv4_ADDR HIS_IPv4_ADDR</userinput></screen>
<screen>&prompt.root; <userinput>ifconfig gif0 inet6 alias MY_ASSIGNED_IPv6_TUNNEL_ENDPOINT_ADDR</userinput></screen>
<screen>&prompt.root; <userinput>ifconfig gif0 create</userinput>
&prompt.root; <userinput>ifconfig gif0</userinput>
gif0: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1280
&prompt.root; <userinput>ifconfig gif0 tunnel <replaceable>MY_IPv4_ADDR</replaceable> <replaceable>HIS_IPv4_ADDR</replaceable></userinput>
&prompt.root; <userinput>ifconfig gif0 inet6 alias <replaceable>MY_ASSIGNED_IPv6_TUNNEL_ENDPOINT_ADDR</replaceable></userinput></screen>
<para>Replace the capitalized words by the information you received from the
upstream 6bone node.</para>
@ -6455,16 +6455,17 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<para>By now setting up a route to your 6bone uplink should be rather
straightforward:</para>
<screen>&prompt.root; <userinput>route add -inet6 default -interface gif0</userinput></screen>
<screen>&prompt.root; <userinput>ping6 -n MY_UPLINK</userinput></screen>
<screen>&prompt.root; <userinput>traceroute6 www.jp.freebsd.org</userinput></screen>
<programlisting>(3ffe:505:2008:1:2a0:24ff:fe57:e561) from 3ffe:8060:100::40:2, 30 hops max, 12 byte packets
<screen>&prompt.root; <userinput>route add -inet6 default -interface gif0</userinput>
&prompt.root; <userinput>ping6 -n <replaceable>MY_UPLINK</replaceable></userinput></screen>
<screen>&prompt.root; <userinput>traceroute6 www.jp.freebsd.org</userinput>
(3ffe:505:2008:1:2a0:24ff:fe57:e561) from 3ffe:8060:100::40:2, 30 hops max, 12 byte packets
1 atnet-meta6 14.147 ms 15.499 ms 24.319 ms
2 6bone-gw2-ATNET-NT.ipv6.tilab.com 103.408 ms 95.072 ms *
3 3ffe:1831:0:ffff::4 138.645 ms 134.437 ms 144.257 ms
4 3ffe:1810:0:6:290:27ff:fe79:7677 282.975 ms 278.666 ms 292.811 ms
5 3ffe:1800:0:ff00::4 400.131 ms 396.324 ms 394.769 ms
6 3ffe:1800:0:3:290:27ff:fe14:cdee 394.712 ms 397.19 ms 394.102 ms</programlisting>
6 3ffe:1800:0:3:290:27ff:fe14:cdee 394.712 ms 397.19 ms 394.102 ms</screen>
<para>This output will differ from machine to machine. By now you should be
able to reach the IPv6 site <ulink url="http://www.kame.net">www.kame.net</ulink>