From e06a5c36e5c28dcb757dff7c9a0d4c5f2235fdd7 Mon Sep 17 00:00:00 2001 From: Martin Heinen Date: Sun, 13 Oct 2002 18:17:34 +0000 Subject: [PATCH] Add hostid tags for IP addresses and netmasks. Approved by: alex (mentor) --- .../handbook/advanced-networking/chapter.sgml | 38 +++++++++---------- .../books/handbook/config/chapter.sgml | 18 ++++----- .../books/handbook/install/chapter.sgml | 10 ++--- .../books/handbook/security/chapter.sgml | 6 +-- 4 files changed, 36 insertions(+), 36 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml index 77d1fffc34..745e910c46 100644 --- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml @@ -4056,7 +4056,7 @@ Internet. trafficked, fast name server, enabling this may be worthwhile. - 127.0.0.1 will not work here. + 127.0.0.1 will not work here. Change this IP address to a name server at your uplink. @@ -4356,9 +4356,9 @@ mail IN A 3.2.1.10 The A record indicates machine names. As seen above, ns1.example.org would resolve to - 3.2.1.2. Again, the origin symbol, @, is + 3.2.1.2. Again, the origin symbol, @, is used here, thus meaning example.org - would resolve to 3.2.1.30. + would resolve to 3.2.1.30. @@ -4368,7 +4368,7 @@ www IN CNAME @ The canonical name record is usually used for giving aliases to a machine. In the example, www is aliased to the machine addressed to the origin, or - example.org (3.2.1.30). + example.org (3.2.1.30). CNAMEs can be used to provide alias hostnames, or round robin one hostname among multiple machines. @@ -5127,10 +5127,10 @@ natd_flags="" RFC 1918 and have a default gateway of the natd machine's internal IP address. - 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 + 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 Internet interface does not require any special modification for natd to work. @@ -5187,9 +5187,9 @@ natd_flags="" 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 + 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 clients A and B. The -redirect_address syntax is as follows: @@ -5916,7 +5916,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms 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 (10.0.0.0/8, 192.168.0.0/24, etc.) and natd address translation are being employed. @@ -6045,17 +6045,17 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms Reading IPv6 Addresses The canonical form is represented as: x:x:x:x:x:x:x:x, each x being a 16 Bit hex value. For example - FEBC:A574:382B:23C1:AA49:4592:4EFE:9982 + FEBC:A574:382B:23C1:AA49:4592:4EFE:9982 Often an address will have long substrings of all zeros therefore each - such substring can be abbreviated by ::. For example fe80::1 - corresponds to the canonical form fe80:0000:0000:0000:0000:0000:0000:0001 + such substring can be abbreviated by ::. For example fe80::1 + corresponds to the canonical form fe80:0000:0000:0000:0000:0000:0000:0001 A third form is to write the last 32 Bit part in the well known (decimal) - IPv4 style with dots . as separators. For example 2002::10.0.0.1 + IPv4 style with dots . as separators. For example 2002::10.0.0.1 corresponds to the (hexadecimal) canonical representation - 2002:0000:0000:0000:0000:0000:000a:0001 which in turn is equivalent to - writing 2002::a:1 + 2002:0000:0000:0000:0000:0000:000a:0001 which in turn is equivalent to + writing 2002::a:1 By now the reader should be able to understand the following: @@ -6068,7 +6068,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms media: Ethernet autoselect (100baseTX ) status: active - fe80::200:21ff:fe03:8e1%rl0 is an auto configured link-local address. It + fe80::200:21ff:fe03:8e1%rl0 is an auto configured link-local address. It includes the enscrambled Ethernet MAC as part of the auto configuration. For further information on the structure of IPv6 addresses see RFC2373 diff --git a/en_US.ISO8859-1/books/handbook/config/chapter.sgml b/en_US.ISO8859-1/books/handbook/config/chapter.sgml index 1936680ceb..af627150b8 100644 --- a/en_US.ISO8859-1/books/handbook/config/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/config/chapter.sgml @@ -570,22 +570,22 @@ tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 The card has an Internet (inet) - address (in this case 192.168.1.3). + address (in this case 192.168.1.3). It has a valid subnet mask (netmask; - 0xffffff00 is the same as 255.255.255.0). + 0xffffff00 is the same as 255.255.255.0). It has a valid broadcast address (in this case, - 192.168.1.255). + 192.168.1.255). The MAC address of the card (ether) - is 00:a0:cc:da:da:da + is 00:a0:cc:da:da:da @@ -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 You could also use the machine name instead of - 192.168.1.2 if you have set up the + 192.168.1.2 if you have set up the /etc/hosts file. @@ -841,10 +841,10 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms For example, consider the case where the fxp0 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. + 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. The following entries configure the adapter correctly for this arrangement: diff --git a/en_US.ISO8859-1/books/handbook/install/chapter.sgml b/en_US.ISO8859-1/books/handbook/install/chapter.sgml index 2ecb4e4b1f..75e44089c3 100644 --- a/en_US.ISO8859-1/books/handbook/install/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/install/chapter.sgml @@ -3012,7 +3012,7 @@ installation menus to try and retry whichever operations have failed. 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 (208.163.10.2) was used. @@ -3022,7 +3022,7 @@ installation menus to try and retry whichever operations have failed. The IP address to be used for this interface was - 192.168.0.1 + 192.168.0.1 @@ -3031,9 +3031,9 @@ installation menus to try and retry whichever operations have failed. 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). + 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). diff --git a/en_US.ISO8859-1/books/handbook/security/chapter.sgml b/en_US.ISO8859-1/books/handbook/security/chapter.sgml index 026acfe72a..8fc99f155e 100644 --- a/en_US.ISO8859-1/books/handbook/security/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/security/chapter.sgml @@ -2305,9 +2305,9 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995 A valid hostname may be specified in place of the IP address. is a decimal number representing how many bits in the address mask should be set. - e.g. specifying 192.216.222.1/24 will create a + e.g. specifying 192.216.222.1/24 will create a mask which will allow any address in a class C subnet (in this case, - 192.216.222) to be matched. + 192.216.222) to be matched. is an IP address which will be logically AND'ed with the address given. The keyword any may be used to specify any IP @@ -2821,7 +2821,7 @@ options IPSEC_ESP #IP security (crypto; define w/IPSEC)Transport Mode Example with IPv4 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 (10.2.3.4) and HOST B (10.6.7.8). 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.