Add hostid tags for IP addresses and netmasks.
Approved by: alex (mentor)
This commit is contained in:
Martin Heinen
parent
a764f33664
commit
e06a5c36e5
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=14619
4 changed files with 36 additions and 36 deletions
|
|
@ -4056,7 +4056,7 @@ Internet.
|
|||
trafficked, fast name server, enabling this may be worthwhile.
|
||||
</para>
|
||||
|
||||
<warning><para>127.0.0.1 will <emphasis>not</emphasis> work here.
|
||||
<warning><para><hostid role="ipaddr">127.0.0.1</hostid> will <emphasis>not</emphasis> work here.
|
||||
Change this IP address to a name server at your uplink.</para>
|
||||
</warning>
|
||||
|
||||
|
|
@ -4356,9 +4356,9 @@ mail IN A 3.2.1.10
|
|||
<para>
|
||||
The A record indicates machine names. As seen above,
|
||||
<hostid>ns1.example.org</hostid> would resolve to
|
||||
3.2.1.2. Again, the origin symbol, <literal>@</literal>, is
|
||||
<hostid role="ipaddr">3.2.1.2</hostid>. Again, the origin symbol, <literal>@</literal>, is
|
||||
used here, thus meaning <hostid>example.org</hostid>
|
||||
would resolve to <hostid>3.2.1.30</hostid>.
|
||||
would resolve to <hostid role="ipaddr">3.2.1.30</hostid>.
|
||||
</para>
|
||||
|
||||
<programlisting>
|
||||
|
|
@ -4368,7 +4368,7 @@ www IN CNAME @</programlisting>
|
|||
The canonical name record is usually used for giving aliases
|
||||
to a machine. In the example, <hostid>www</hostid> is
|
||||
aliased to the machine addressed to the origin, or
|
||||
<hostid>example.org</hostid> (3.2.1.30).
|
||||
<hostid>example.org</hostid> (<hostid role="ipaddr">3.2.1.30</hostid>).
|
||||
<varname>CNAME</varname>s can be used to provide alias
|
||||
hostnames, or round robin one hostname among multiple
|
||||
machines.
|
||||
|
|
@ -5127,10 +5127,10 @@ natd_flags=""</programlisting>
|
|||
<ulink url="ftp://ftp.isi.edu/in-notes/rfc1918.txt">RFC 1918</ulink>
|
||||
and have a default gateway of the natd machine's internal IP address.</para>
|
||||
|
||||
<para>For example, client a and b behind the LAN have IP addresses of 192.168.0.2
|
||||
and 192.168.0.3, while the natd machine's LAN interface has an IP address of
|
||||
192.168.0.1. Client a and b's default gateway must be set to that of
|
||||
the natd machine, 192.168.0.1. The natd machine's external, or
|
||||
<para>For example, client a and b behind the LAN have IP addresses of <hostid role="ipaddr">192.168.0.2</hostid>
|
||||
and <hostid role="ipaddr">192.168.0.3</hostid>, while the natd machine's LAN interface has an IP address of
|
||||
<hostid role="ipaddr">192.168.0.1</hostid>. Client a and b's default gateway must be set to that of
|
||||
the natd machine, <hostid role="ipaddr">192.168.0.1</hostid>. The natd machine's external, or
|
||||
Internet interface does not require any special modification for natd
|
||||
to work.</para>
|
||||
</sect2>
|
||||
|
|
@ -5187,9 +5187,9 @@ natd_flags=""</programlisting>
|
|||
packets from the LAN clients with the proper external IP address and redirects
|
||||
all traffic incoming on that particular IP address back to the specific LAN
|
||||
client. This is also known as static NAT. For example, the IP addresses
|
||||
128.1.1.1, 128.1.1.2, and 128.1.1.3 belong to the natd gateway
|
||||
machine. 128.1.1.1 can be used as the natd gateway machine's external
|
||||
IP address, while 128.1.1.2 and 128.1.1.3 are forwarded back to LAN
|
||||
<hostid role="ipaddr">128.1.1.1</hostid>, <hostid role="ipaddr">128.1.1.2</hostid>, and <hostid role="ipaddr">128.1.1.3</hostid> belong to the natd gateway
|
||||
machine. <hostid role="ipaddr">128.1.1.1</hostid> can be used as the natd gateway machine's external
|
||||
IP address, while <hostid role="ipaddr">128.1.1.2</hostid> and <hostid role="ipaddr">128.1.1.3</hostid> are forwarded back to LAN
|
||||
clients A and B.</para>
|
||||
|
||||
<para>The -redirect_address syntax is as follows:</para>
|
||||
|
|
@ -5916,7 +5916,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Running out of addresses. Today this is not so much of a concern
|
||||
anymore since private address spaces (10.0.0.0/8, 192.168.0.0/24,
|
||||
anymore since private address spaces (<hostid role="ipaddr">10.0.0.0/8</hostid>, <hostid role="ipaddr">192.168.0.0/24</hostid>,
|
||||
etc.) and natd address translation are being employed.</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -6045,17 +6045,17 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
|
|||
<title>Reading IPv6 Addresses</title>
|
||||
<para>The canonical form is represented as: x:x:x:x:x:x:x:x, each
|
||||
<quote>x</quote> being a 16 Bit hex value. For example
|
||||
FEBC:A574:382B:23C1:AA49:4592:4EFE:9982</para>
|
||||
<hostid role="ip6addr">FEBC:A574:382B:23C1:AA49:4592:4EFE:9982</hostid></para>
|
||||
|
||||
<para>Often an address will have long substrings of all zeros therefore each
|
||||
such substring can be abbreviated by <quote>::</quote>. For example fe80::1
|
||||
corresponds to the canonical form fe80:0000:0000:0000:0000:0000:0000:0001</para>
|
||||
such substring can be abbreviated by <quote>::</quote>. For example <hostid role="ip6addr">fe80::1</hostid>
|
||||
corresponds to the canonical form <hostid role="ip6addr">fe80:0000:0000:0000:0000:0000:0000:0001</hostid></para>
|
||||
|
||||
<para>A third form is to write the last 32 Bit part in the well known (decimal)
|
||||
IPv4 style with dots <quote>.</quote> as separators. For example 2002::10.0.0.1
|
||||
IPv4 style with dots <quote>.</quote> as separators. For example <hostid role="ip6addr">2002::10.0.0.1</hostid>
|
||||
corresponds to the (hexadecimal) canonical representation
|
||||
2002:0000:0000:0000:0000:0000:000a:0001 which in turn is equivalent to
|
||||
writing 2002::a:1</para>
|
||||
<hostid role="ip6addr">2002:0000:0000:0000:0000:0000:000a:0001</hostid> which in turn is equivalent to
|
||||
writing <hostid role="ip6addr">2002::a:1</hostid></para>
|
||||
|
||||
<para>By now the reader should be able to understand the following:</para>
|
||||
|
||||
|
|
@ -6068,7 +6068,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
|
|||
media: Ethernet autoselect (100baseTX )
|
||||
status: active</programlisting>
|
||||
|
||||
<para>fe80::200:21ff:fe03:8e1%rl0 is an auto configured link-local address. It
|
||||
<para><hostid role="ip6addr">fe80::200:21ff:fe03:8e1%rl0</hostid> is an auto configured link-local address. It
|
||||
includes the enscrambled Ethernet MAC as part of the auto configuration.</para>
|
||||
|
||||
<para>For further information on the structure of IPv6 addresses see RFC2373</para>
|
||||
|
|
|
|||
|
|
@ -570,22 +570,22 @@ tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500</screen>
|
|||
|
||||
<listitem>
|
||||
<para>The card has an Internet (<literal>inet</literal>)
|
||||
address (in this case 192.168.1.3).</para>
|
||||
address (in this case <hostid role="ipaddr">192.168.1.3</hostid>).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>It has a valid subnet mask (<literal>netmask</literal>;
|
||||
0xffffff00 is the same as 255.255.255.0).</para>
|
||||
<hostid role="netmask">0xffffff00</hostid> is the same as <hostid role="netmask">255.255.255.0</hostid>).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>It has a valid broadcast address (in this case,
|
||||
192.168.1.255).</para>
|
||||
<hostid role="ipaddr">192.168.1.255</hostid>).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>The MAC address of the card (<literal>ether</literal>)
|
||||
is 00:a0:cc:da:da:da</para>
|
||||
is <hostid role="mac">00:a0:cc:da:da:da</hostid></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -698,7 +698,7 @@ PING 192.168.1.2 (192.168.1.2): 56 data bytes
|
|||
round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
|
||||
|
||||
<para>You could also use the machine name instead of
|
||||
<literal>192.168.1.2</literal> if you have set up the
|
||||
<hostid role="ipaddr">192.168.1.2</hostid> if you have set up the
|
||||
<filename>/etc/hosts</filename> file.</para>
|
||||
</sect3>
|
||||
|
||||
|
|
@ -841,10 +841,10 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
|
|||
|
||||
<para>For example, consider the case where the
|
||||
<devicename>fxp0</devicename> interface is
|
||||
connected to two networks, the 10.1.1.0 network with a netmask
|
||||
of 255.255.255.0 and the 202.0.75.16 network with a netmask of
|
||||
255.255.255.240. We want the system to appear at 10.1.1.1
|
||||
through 10.1.1.5 and at 202.0.75.17 through 202.0.75.20.</para>
|
||||
connected to two networks, the <hostid role="ipaddr">10.1.1.0</hostid> network with a netmask
|
||||
of <hostid role="netmask">255.255.255.0</hostid> and the <hostid role="ipaddr">202.0.75.16</hostid> network with a netmask of
|
||||
<hostid role="netmask">255.255.255.240</hostid>. We want the system to appear at <hostid role="ipaddr">10.1.1.1</hostid>
|
||||
through <hostid role="ipaddr">10.1.1.5</hostid> and at <hostid role="ipaddr">202.0.75.17</hostid> through <hostid role="ipaddr">202.0.75.20</hostid>.</para>
|
||||
|
||||
<para>The following entries configure the adapter correctly for
|
||||
this arrangement:</para>
|
||||
|
|
|
|||
|
|
@ -3012,7 +3012,7 @@ installation menus to try and retry whichever operations have failed.
|
|||
<listitem>
|
||||
<para>IP address of your local DNS server. There is no local
|
||||
DNS server on this private local area network so the IP
|
||||
address of the provider's DNS server (208.163.10.2) was
|
||||
address of the provider's DNS server (<hostid role="ipaddr">208.163.10.2</hostid>) was
|
||||
used.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
|
@ -3022,7 +3022,7 @@ installation menus to try and retry whichever operations have failed.
|
|||
|
||||
<listitem>
|
||||
<para>The IP address to be used for this interface was
|
||||
192.168.0.1</para>
|
||||
<hostid role="ipaddr">192.168.0.1</hostid></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -3031,9 +3031,9 @@ installation menus to try and retry whichever operations have failed.
|
|||
|
||||
<listitem>
|
||||
<para>The address block being used for this local area
|
||||
network is a Class C block (192.168.0.0 -
|
||||
192.168.255.255). The default netmask is for a Class C
|
||||
network (255.255.255.0).</para>
|
||||
network is a Class C block (<hostid role="ipaddr">192.168.0.0</hostid> -
|
||||
<hostid role="ipaddr">192.168.255.255</hostid>). The default netmask is for a Class C
|
||||
network (<hostid role="netmask">255.255.255.0</hostid>).</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
|
|||
|
|
@ -2305,9 +2305,9 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
|||
<para>A valid hostname may be specified in place of the IP address.
|
||||
<option><replaceable>mask-bits</replaceable></option> is a decimal
|
||||
number representing how many bits in the address mask should be set.
|
||||
e.g. specifying <literal>192.216.222.1/24</literal> will create a
|
||||
e.g. specifying <hostid role="netmask">192.216.222.1/24</hostid> will create a
|
||||
mask which will allow any address in a class C subnet (in this case,
|
||||
192.216.222) to be matched.
|
||||
<hostid role="ipaddr">192.216.222</hostid>) to be matched.
|
||||
<option><replaceable>mask-pattern</replaceable></option> is an IP
|
||||
address which will be logically AND'ed with the address given. The
|
||||
keyword <literal>any</literal> may be used to specify <quote>any IP
|
||||
|
|
@ -2821,7 +2821,7 @@ options IPSEC_ESP #IP security (crypto; define w/IPSEC)</progr
|
|||
<title>Transport Mode Example with IPv4</title>
|
||||
|
||||
<para>Let us setup security association to deploy a secure channel
|
||||
between HOST A (10.2.3.4) and HOST B (10.6.7.8). Here we show a little
|
||||
between HOST A (<hostid role="ipaddr">10.2.3.4</hostid>) and HOST B (<hostid role="ipaddr">10.6.7.8</hostid>). Here we show a little
|
||||
complicated example. From HOST A to HOST B, only old AH is used.
|
||||
From HOST B to HOST A, new AH and new ESP are combined.</para>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue