Clean up some punctuation hair I noticed.
<code> seems to be not-liked by our HTML conversion right now, so I've switched over to <tscreen><verb> sections which should accomplish the same effect (and also look consistent with other examples).
This commit is contained in:
Jordan K. Hubbard
parent
04ce9ce98f
commit
87e55266d8
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=1074
2 changed files with 110 additions and 118 deletions
|
|
@ -1,5 +1,5 @@
|
|||
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
|
||||
<!-- $Id: ppp.sgml,v 1.2 1997-01-19 15:39:16 jkh Exp $ -->
|
||||
<!-- $Id: ppp.sgml,v 1.3 1997-01-21 05:49:54 jkh Exp $ -->
|
||||
|
||||
<article>
|
||||
|
||||
|
|
@ -8,7 +8,7 @@
|
|||
url="mailto:SimsS@IBM.NET"
|
||||
name="<SimsS@IBM.NET>"></tt>
|
||||
|
||||
<date>$Date: 1997-01-19 15:39:16 $
|
||||
<date>$Date: 1997-01-21 05:49:54 $
|
||||
<abstract>
|
||||
This is a step-by-step guide for configuring FreeBSD systems to act as
|
||||
a dial-up router/gateway in a Local Area Environment. All entries may
|
||||
|
|
@ -146,7 +146,7 @@ information to prevent trouble in subsequent steps.
|
|||
|
||||
<p>It's possible that the FreeBSD host name was specified and saved
|
||||
when the system was initially installed. To verify that it was, enter
|
||||
the following command at a prompt,:<p>
|
||||
the following command at a prompt:<p>
|
||||
<tscreen><verb>
|
||||
# hostname
|
||||
</verb></tscreen>
|
||||
|
|
@ -168,12 +168,11 @@ probably see 'myname.my.domain` as a response. You'll need to edit
|
|||
|
||||
<sect2><heading>Configuring the FreeBSD Host Name</heading>
|
||||
|
||||
<p><em><bf>*** Reminder: You must be logged in as 'root' to edit the
|
||||
<p><em><bf>Reminder: You must be logged in as 'root' to edit the
|
||||
system configuration files!</bf></em>
|
||||
|
||||
<it><bf>*** CAUTION: If you mangle the system configuration files,
|
||||
chances are your system WILL NOT BOOT correctly! Be
|
||||
careful!</bf></it>
|
||||
<em><bf>CAUTION: If you mangle the system configuration files,
|
||||
chances are your system WILL NOT BOOT correctly! Be careful!</bf></em>
|
||||
|
||||
<p>The configuration file that specifies the FreeBSD system's host
|
||||
name when the system boots is in <tt>/etc/sysconfig</tt>. Use the
|
||||
|
|
@ -231,10 +230,10 @@ FreeBSD system (Ethernet and others), enter the following command:
|
|||
# ifconfig -a
|
||||
</verb></tscreen>
|
||||
(In layman's terms: "Show me the <BF/I/nter<BF/F/ace <BF/CONFIG/uration
|
||||
for my network devices".)
|
||||
for my network devices.")
|
||||
|
||||
An example:
|
||||
<code>
|
||||
<p>An example:
|
||||
<tscreen><verb>
|
||||
# ifconfig -a
|
||||
ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu
|
||||
1500
|
||||
|
|
@ -247,13 +246,14 @@ An example:
|
|||
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
|
||||
inet 127.0.0.1 netmask 0xff000000
|
||||
# _
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
|
||||
<p>In this example, the following devices were displayed:<p>
|
||||
<tt/ed0:/ The Ethernet Interface<p>
|
||||
<tt/lp0:/ The Parallel Port Interface (ignored in this guide)<p>
|
||||
<tt/tun0:/ The "tunnel" device; <em/This is the one ppp uses!/<p>
|
||||
<tt/tun0:/ The "tunnel" device; <em/This is the one user-mode ppp uses!/<p>
|
||||
<tt/sl0:/ The SL/IP device (ignored in this guide)<p>
|
||||
<tt/ppp0:/ Another PPP device (ignored in this guide)<p>
|
||||
<tt/ppp0:/ Another PPP device (for kernel ppp; ignored in this guide)<p>
|
||||
<tt/lo0:/ The "Loopback" device (ignored in this guide)<p>
|
||||
|
||||
In this example, the 'ed0' device is up and running. The key
|
||||
|
|
@ -267,10 +267,10 @@ indicators are:
|
|||
</enum>
|
||||
|
||||
<p>If the line for the Ethernet card had shown something similar to:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
ed0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
|
||||
ether 01:02:03:04:05:06
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
then the Ethernet card hasn't been configured yet.
|
||||
|
||||
<p>If the configuration for the Ethernet interface is correct you can
|
||||
|
|
@ -279,13 +279,11 @@ Otherwise, proceed with the next section.
|
|||
<sect2>
|
||||
<heading>Configuring your Ethernet Interface</heading>
|
||||
|
||||
<p><em><bf>*** Reminder: You must be logged in as 'root' to edit the
|
||||
system
|
||||
configuration files!</bf></em>
|
||||
<p><em><bf>Reminder: You must be logged in as 'root' to edit the
|
||||
system configuration files!</bf></em>
|
||||
|
||||
<it><bf>*** CAUTION: If you mangle the system configuration files,
|
||||
chances are your system WILL NOT BOOT correctly! Be
|
||||
careful!</bf></it>
|
||||
<em><bf>CAUTION: If you mangle the system configuration files,
|
||||
chances are your system WILL NOT BOOT correctly! Be careful!</bf></em>
|
||||
|
||||
<p>The configuration file that specifies settings for the network
|
||||
interfaces when the system boots is in <tt>/etc/sysconfig</tt>. Use
|
||||
|
|
@ -317,8 +315,8 @@ network_interfaces="lo0 ed0"
|
|||
("lo0")
|
||||
and the Ethernet device ("<tt/ed0/")!
|
||||
|
||||
<p>*** Reminder: If your Ethernet card isn't named '<tt/ed0/', specify
|
||||
the correct device name here instead.
|
||||
<p><em><bf> Reminder: If your Ethernet card isn't named '<tt/ed0/', specify
|
||||
the correct device name here instead.</bf></em>
|
||||
|
||||
<p>If you performed the installation of FreeBSD over a network
|
||||
connection then the '<tt/network_interfaces=/' line may already
|
||||
|
|
@ -411,12 +409,11 @@ gateway=YES
|
|||
|
||||
and exit the editor (saving the changes!).
|
||||
|
||||
<p>*** NOTE: This line may already be set to '<tt/gateway=YES/' if IP
|
||||
forwarding was enabled when the FreeBSD system was installed.
|
||||
<p><em><bf>NOTE: This line may already be set to '<tt/gateway=YES/' if IP
|
||||
forwarding was enabled when the FreeBSD system was installed.</bf></em>
|
||||
|
||||
<sect1>
|
||||
<heading>Creating the List of other LAN
|
||||
Hosts(<tt>/etc/hosts</tt>)</heading>
|
||||
<heading>Creating the List of other LAN Hosts(<tt>/etc/hosts</tt>)</heading>
|
||||
|
||||
<p>The final step in configuring the LAN side of the FreeBSD system is
|
||||
to create a list of the names and TCP/IP addresses of the various
|
||||
|
|
@ -436,13 +433,13 @@ configuration example in Section 3.2.)
|
|||
the comments along the way; there's some good information there!) and
|
||||
enter (assuming our sample network) the following IP addresses and
|
||||
host names:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
192.168.1.1 curly curly.my.domain # FreeBSD System
|
||||
192.168.1.2 larry larry.my.domain # Windows '95 System
|
||||
192.168.1.3 moe moe.my.domain # Windows for Workgroups
|
||||
System
|
||||
192.168.1.4 shemp shemp.my.domain # Windows NT System
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
|
||||
<p>(No changes are needed to the line for the '<tt>127.0.0.1
|
||||
localhost</tt>' entry.)
|
||||
|
|
@ -477,14 +474,14 @@ interfaces.
|
|||
</verb></tscreen>
|
||||
|
||||
<p>You should see:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
# ping localhost
|
||||
PING localhost.my.domain. (127.0.0.1): 56 data bytes
|
||||
64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.219 ms
|
||||
64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.287 ms
|
||||
64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.214 m
|
||||
[...]
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
messages scroll by until you hit Ctrl-C to stop the madness.
|
||||
|
||||
<sect2>
|
||||
|
|
@ -497,14 +494,14 @@ messages scroll by until you hit Ctrl-C to stop the madness.
|
|||
</verb></tscreen>
|
||||
|
||||
You should see:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
# ping curly
|
||||
PING curly.my.domain. (192.168.1.1): 56 data bytes
|
||||
64 bytes from 192.168.1.1: icmp_seq=0 ttl=255 time=0.219 ms
|
||||
64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=0.200 ms
|
||||
64 bytes from 192.168.1.1: icmp_seq=2 ttl=255 time=0.187 ms
|
||||
[...]
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
messages.
|
||||
|
||||
<p>One important thing to look at in these two examples is that the
|
||||
|
|
@ -605,7 +602,7 @@ dial-out connection working.
|
|||
|
||||
<p>Below is the /etc/ppp/ppp.conf file that we'll be using to provide a
|
||||
dial-out Internet gateway for our example LAN:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
################################################################
|
||||
# PPP Configuration File ('/etc/ppp/ppp.conf')
|
||||
#
|
||||
|
|
@ -657,7 +654,7 @@ set ifaddr 127.1.1.1/0 127.2.2.2/0 255.255.255.0
|
|||
add 0 0 127.2.2.2
|
||||
################################################################
|
||||
# End of /etc/ppp/ppp.conf
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
This file, taken verbatim from a working system, has three relevant
|
||||
configuration sections:
|
||||
|
||||
|
|
@ -684,8 +681,7 @@ Under FreeBSD the '<tt>/dev/cuaa0</tt>' device is the same port that's
|
|||
known as "<tt>COM1:</tt>" under DOS, Windows, Windows 95, etc....
|
||||
|
||||
<p>If your modem is on <tt>COM2:</tt> you should specify
|
||||
'<tt>/dev/cua01</tt>;, <tt>COM3:</tt>
|
||||
would be '<tt>/dev/cua02</tt>'.
|
||||
'<tt>/dev/cua01</tt>; <tt>COM3:</tt> would be '<tt>/dev/cua02</tt>'.
|
||||
|
||||
<tscreen><verb>
|
||||
set speed 57600
|
||||
|
|
@ -962,9 +958,9 @@ This last line tells the PPP program that it should add a default
|
|||
route for IP traffic that points to the (fake) IP address of the ISP's
|
||||
system.
|
||||
|
||||
<em>*** Note: If you used an ISP-specified address instead of
|
||||
<em><bf>Note: If you used an ISP-specified address instead of
|
||||
<tt>127.2.2.2</tt> on the preceeding line, use the same number here
|
||||
instead of <tt>127.2.2.2</tt></em>.
|
||||
instead of <tt>127.2.2.2</tt></bf></em>.
|
||||
|
||||
<p>By adding this "fake" route for IP traffic, the PPP program can,
|
||||
while idle:
|
||||
|
|
@ -996,7 +992,7 @@ install a new default route that points the actual IP address of the
|
|||
remote end (discovered during the dial-up connection setup).
|
||||
|
||||
A representative '<tt>/etc/ppp/ppp.linkup</tt>' file:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
#########################################################################=
|
||||
|
||||
# PPP Link Up File ('/etc/ppp/ppp.linkup')
|
||||
|
|
@ -1031,7 +1027,7 @@ MYADDR:
|
|||
add 0 0 HISADDR
|
||||
########################################################################
|
||||
# End of /etc/ppp/ppp.linkup
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
Notice that there is a section in this file named "demand:", identical
|
||||
to the configuration name used in the '<tt>/etc/ppp/ppp.conf</tt>'
|
||||
file. This section instructs the PPP program that once a link is
|
||||
|
|
@ -1047,8 +1043,8 @@ established using this configuration, it must:
|
|||
Dial-on-Demand configurations) execute the "delete ALL" and "add 0 0
|
||||
HISADDR" commands in <tt>/etc/ppp/ppp.linkup</tt>.
|
||||
|
||||
<p><bf><em>This is the mechanism that controls the actual on-demand
|
||||
configuration of the link.</em></bf>
|
||||
<p><em><bf>This is the mechanism that controls the actual on-demand
|
||||
configuration of the link.</bf></em>
|
||||
|
||||
<p>All configurations not explicitly named in
|
||||
<tt>/etc/ppp/ppp.linkup</tt> will use whatever commands are in the
|
||||
|
|
@ -1473,7 +1469,7 @@ Esentially, it tells the Name Server:
|
|||
|
||||
<p>Using the '<tt/ee/' editor, create a
|
||||
<tt>/etc/namedb/named.boot</tt> with the following contents:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
; boot file for mini-name server
|
||||
|
||||
directory /etc/namedb
|
||||
|
|
@ -1482,14 +1478,14 @@ directory /etc/namedb
|
|||
|
||||
cache . named.root
|
||||
primary my.domain. mydomain.db
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
<p>Lines that begin with a semi-colon are comments. The significant
|
||||
lines in this file are:
|
||||
<itemize>
|
||||
<item><tt>directory /etc/namedb</tt>
|
||||
<p>Tells the Name Server where to find the configuration files
|
||||
referenced in the remaining sections of
|
||||
the '<tt>/etc/namedb/named.boot</tt>' file.
|
||||
referenced in the remaining sections of the
|
||||
'<tt>/etc/namedb/named.boot</tt>' file.
|
||||
<item><tt>cache . named.root</tt>
|
||||
<p>Tells the Name Server that the list of "Top-Level" DNS servers for
|
||||
the Internet can be found in a file called '<tt>named.root</tt>'.
|
||||
|
|
@ -1516,7 +1512,7 @@ refer to the <tt/named/ manpage.</em>
|
|||
|
||||
<p>The <tt>/etc/namedb/mydomain.db</tt> file for our minimal DNS
|
||||
server has the following contents:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
@ IN SOA my.domain. root.my.domain. (
|
||||
961230 ; Serial
|
||||
3600 ; Refresh
|
||||
|
|
@ -1540,7 +1536,7 @@ $ORIGIN 1.168.192.IN-ADDR.ARPA
|
|||
$ORIGIN 0.0.127.IN-ADDR.ARPA
|
||||
IN NS curly.my.domain.
|
||||
1 IN PTR localhost.my.domain.
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
<p>In simple terms, this file declares that the local DNS server is:
|
||||
<itemize>
|
||||
<item>The Start of Authority for ("SOA") for a domain called
|
||||
|
|
@ -1566,37 +1562,37 @@ changing a single line in '<tt>/etc/sysconfig</tt>' as follows:
|
|||
|
||||
<p> Using the '<tt/ee/' editor, load <tt>/etc/sysconfig</tt>. Scroll
|
||||
down approximately 200 lines until you come to the section that says:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
---
|
||||
# Set to appropriate flags for named, if you have a full-time
|
||||
# connection to the Internet.
|
||||
# For most hosts, flags should be "-b /etc/namedb/named.boot"
|
||||
namedflags="NO"
|
||||
---
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
Change this section to read:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
---
|
||||
# Set to appropriate flags for named, if you have a full-time
|
||||
# connection to the Internet.
|
||||
# For most hosts, flags should be "-b /etc/namedb/named.boot"
|
||||
namedflags="-b /etc/namedb/named.boot"
|
||||
---
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
Save the file and reboot.
|
||||
|
||||
Alternatively, start the Name Server daemon by entering the following
|
||||
command:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
# named -b /etc/namedb/named.boot
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
|
||||
<p>Whenever you modify any of the files in <tt>/etc/namedb</tt> you'll
|
||||
need to kick-start the Name Server process to make it pick up the
|
||||
modifications. This is performed with the following system command:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
# kill -HUP `cat /var/run/named.pid`
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
|
||||
<sect1>
|
||||
<heading>Playing with PPP filters</heading>
|
||||
|
|
@ -1634,7 +1630,7 @@ What follows is a snippet from an operating system which provides a
|
|||
good foundation for "normal" Internet operations while preventing PPP
|
||||
from pumping <em/all/ data over the dial-up connection. Comments
|
||||
briefly describe the logic of each rule set:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
#
|
||||
# KeepAlive filters
|
||||
# Don't keep Alive with ICMP,DNS and RIP packet
|
||||
|
|
@ -1719,7 +1715,7 @@ briefly describe the logic of each rule set:
|
|||
#
|
||||
# If none of above rules matches, then packet is blocked.
|
||||
#-------
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
<p>Up to 20 distinct filtering rules can be applied to each class of
|
||||
filter. Rules in each class are number sequentially from 0 to 20
|
||||
<em/but none of the rules for a particular filter class take affect
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
|
||||
<!-- $Id: ppp.sgml,v 1.2 1997-01-19 15:39:16 jkh Exp $ -->
|
||||
<!-- $Id: ppp.sgml,v 1.3 1997-01-21 05:49:54 jkh Exp $ -->
|
||||
|
||||
<article>
|
||||
|
||||
|
|
@ -8,7 +8,7 @@
|
|||
url="mailto:SimsS@IBM.NET"
|
||||
name="<SimsS@IBM.NET>"></tt>
|
||||
|
||||
<date>$Date: 1997-01-19 15:39:16 $
|
||||
<date>$Date: 1997-01-21 05:49:54 $
|
||||
<abstract>
|
||||
This is a step-by-step guide for configuring FreeBSD systems to act as
|
||||
a dial-up router/gateway in a Local Area Environment. All entries may
|
||||
|
|
@ -146,7 +146,7 @@ information to prevent trouble in subsequent steps.
|
|||
|
||||
<p>It's possible that the FreeBSD host name was specified and saved
|
||||
when the system was initially installed. To verify that it was, enter
|
||||
the following command at a prompt,:<p>
|
||||
the following command at a prompt:<p>
|
||||
<tscreen><verb>
|
||||
# hostname
|
||||
</verb></tscreen>
|
||||
|
|
@ -168,12 +168,11 @@ probably see 'myname.my.domain` as a response. You'll need to edit
|
|||
|
||||
<sect2><heading>Configuring the FreeBSD Host Name</heading>
|
||||
|
||||
<p><em><bf>*** Reminder: You must be logged in as 'root' to edit the
|
||||
<p><em><bf>Reminder: You must be logged in as 'root' to edit the
|
||||
system configuration files!</bf></em>
|
||||
|
||||
<it><bf>*** CAUTION: If you mangle the system configuration files,
|
||||
chances are your system WILL NOT BOOT correctly! Be
|
||||
careful!</bf></it>
|
||||
<em><bf>CAUTION: If you mangle the system configuration files,
|
||||
chances are your system WILL NOT BOOT correctly! Be careful!</bf></em>
|
||||
|
||||
<p>The configuration file that specifies the FreeBSD system's host
|
||||
name when the system boots is in <tt>/etc/sysconfig</tt>. Use the
|
||||
|
|
@ -231,10 +230,10 @@ FreeBSD system (Ethernet and others), enter the following command:
|
|||
# ifconfig -a
|
||||
</verb></tscreen>
|
||||
(In layman's terms: "Show me the <BF/I/nter<BF/F/ace <BF/CONFIG/uration
|
||||
for my network devices".)
|
||||
for my network devices.")
|
||||
|
||||
An example:
|
||||
<code>
|
||||
<p>An example:
|
||||
<tscreen><verb>
|
||||
# ifconfig -a
|
||||
ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu
|
||||
1500
|
||||
|
|
@ -247,13 +246,14 @@ An example:
|
|||
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
|
||||
inet 127.0.0.1 netmask 0xff000000
|
||||
# _
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
|
||||
<p>In this example, the following devices were displayed:<p>
|
||||
<tt/ed0:/ The Ethernet Interface<p>
|
||||
<tt/lp0:/ The Parallel Port Interface (ignored in this guide)<p>
|
||||
<tt/tun0:/ The "tunnel" device; <em/This is the one ppp uses!/<p>
|
||||
<tt/tun0:/ The "tunnel" device; <em/This is the one user-mode ppp uses!/<p>
|
||||
<tt/sl0:/ The SL/IP device (ignored in this guide)<p>
|
||||
<tt/ppp0:/ Another PPP device (ignored in this guide)<p>
|
||||
<tt/ppp0:/ Another PPP device (for kernel ppp; ignored in this guide)<p>
|
||||
<tt/lo0:/ The "Loopback" device (ignored in this guide)<p>
|
||||
|
||||
In this example, the 'ed0' device is up and running. The key
|
||||
|
|
@ -267,10 +267,10 @@ indicators are:
|
|||
</enum>
|
||||
|
||||
<p>If the line for the Ethernet card had shown something similar to:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
ed0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
|
||||
ether 01:02:03:04:05:06
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
then the Ethernet card hasn't been configured yet.
|
||||
|
||||
<p>If the configuration for the Ethernet interface is correct you can
|
||||
|
|
@ -279,13 +279,11 @@ Otherwise, proceed with the next section.
|
|||
<sect2>
|
||||
<heading>Configuring your Ethernet Interface</heading>
|
||||
|
||||
<p><em><bf>*** Reminder: You must be logged in as 'root' to edit the
|
||||
system
|
||||
configuration files!</bf></em>
|
||||
<p><em><bf>Reminder: You must be logged in as 'root' to edit the
|
||||
system configuration files!</bf></em>
|
||||
|
||||
<it><bf>*** CAUTION: If you mangle the system configuration files,
|
||||
chances are your system WILL NOT BOOT correctly! Be
|
||||
careful!</bf></it>
|
||||
<em><bf>CAUTION: If you mangle the system configuration files,
|
||||
chances are your system WILL NOT BOOT correctly! Be careful!</bf></em>
|
||||
|
||||
<p>The configuration file that specifies settings for the network
|
||||
interfaces when the system boots is in <tt>/etc/sysconfig</tt>. Use
|
||||
|
|
@ -317,8 +315,8 @@ network_interfaces="lo0 ed0"
|
|||
("lo0")
|
||||
and the Ethernet device ("<tt/ed0/")!
|
||||
|
||||
<p>*** Reminder: If your Ethernet card isn't named '<tt/ed0/', specify
|
||||
the correct device name here instead.
|
||||
<p><em><bf> Reminder: If your Ethernet card isn't named '<tt/ed0/', specify
|
||||
the correct device name here instead.</bf></em>
|
||||
|
||||
<p>If you performed the installation of FreeBSD over a network
|
||||
connection then the '<tt/network_interfaces=/' line may already
|
||||
|
|
@ -411,12 +409,11 @@ gateway=YES
|
|||
|
||||
and exit the editor (saving the changes!).
|
||||
|
||||
<p>*** NOTE: This line may already be set to '<tt/gateway=YES/' if IP
|
||||
forwarding was enabled when the FreeBSD system was installed.
|
||||
<p><em><bf>NOTE: This line may already be set to '<tt/gateway=YES/' if IP
|
||||
forwarding was enabled when the FreeBSD system was installed.</bf></em>
|
||||
|
||||
<sect1>
|
||||
<heading>Creating the List of other LAN
|
||||
Hosts(<tt>/etc/hosts</tt>)</heading>
|
||||
<heading>Creating the List of other LAN Hosts(<tt>/etc/hosts</tt>)</heading>
|
||||
|
||||
<p>The final step in configuring the LAN side of the FreeBSD system is
|
||||
to create a list of the names and TCP/IP addresses of the various
|
||||
|
|
@ -436,13 +433,13 @@ configuration example in Section 3.2.)
|
|||
the comments along the way; there's some good information there!) and
|
||||
enter (assuming our sample network) the following IP addresses and
|
||||
host names:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
192.168.1.1 curly curly.my.domain # FreeBSD System
|
||||
192.168.1.2 larry larry.my.domain # Windows '95 System
|
||||
192.168.1.3 moe moe.my.domain # Windows for Workgroups
|
||||
System
|
||||
192.168.1.4 shemp shemp.my.domain # Windows NT System
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
|
||||
<p>(No changes are needed to the line for the '<tt>127.0.0.1
|
||||
localhost</tt>' entry.)
|
||||
|
|
@ -477,14 +474,14 @@ interfaces.
|
|||
</verb></tscreen>
|
||||
|
||||
<p>You should see:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
# ping localhost
|
||||
PING localhost.my.domain. (127.0.0.1): 56 data bytes
|
||||
64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.219 ms
|
||||
64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.287 ms
|
||||
64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=0.214 m
|
||||
[...]
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
messages scroll by until you hit Ctrl-C to stop the madness.
|
||||
|
||||
<sect2>
|
||||
|
|
@ -497,14 +494,14 @@ messages scroll by until you hit Ctrl-C to stop the madness.
|
|||
</verb></tscreen>
|
||||
|
||||
You should see:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
# ping curly
|
||||
PING curly.my.domain. (192.168.1.1): 56 data bytes
|
||||
64 bytes from 192.168.1.1: icmp_seq=0 ttl=255 time=0.219 ms
|
||||
64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=0.200 ms
|
||||
64 bytes from 192.168.1.1: icmp_seq=2 ttl=255 time=0.187 ms
|
||||
[...]
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
messages.
|
||||
|
||||
<p>One important thing to look at in these two examples is that the
|
||||
|
|
@ -605,7 +602,7 @@ dial-out connection working.
|
|||
|
||||
<p>Below is the /etc/ppp/ppp.conf file that we'll be using to provide a
|
||||
dial-out Internet gateway for our example LAN:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
################################################################
|
||||
# PPP Configuration File ('/etc/ppp/ppp.conf')
|
||||
#
|
||||
|
|
@ -657,7 +654,7 @@ set ifaddr 127.1.1.1/0 127.2.2.2/0 255.255.255.0
|
|||
add 0 0 127.2.2.2
|
||||
################################################################
|
||||
# End of /etc/ppp/ppp.conf
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
This file, taken verbatim from a working system, has three relevant
|
||||
configuration sections:
|
||||
|
||||
|
|
@ -684,8 +681,7 @@ Under FreeBSD the '<tt>/dev/cuaa0</tt>' device is the same port that's
|
|||
known as "<tt>COM1:</tt>" under DOS, Windows, Windows 95, etc....
|
||||
|
||||
<p>If your modem is on <tt>COM2:</tt> you should specify
|
||||
'<tt>/dev/cua01</tt>;, <tt>COM3:</tt>
|
||||
would be '<tt>/dev/cua02</tt>'.
|
||||
'<tt>/dev/cua01</tt>; <tt>COM3:</tt> would be '<tt>/dev/cua02</tt>'.
|
||||
|
||||
<tscreen><verb>
|
||||
set speed 57600
|
||||
|
|
@ -962,9 +958,9 @@ This last line tells the PPP program that it should add a default
|
|||
route for IP traffic that points to the (fake) IP address of the ISP's
|
||||
system.
|
||||
|
||||
<em>*** Note: If you used an ISP-specified address instead of
|
||||
<em><bf>Note: If you used an ISP-specified address instead of
|
||||
<tt>127.2.2.2</tt> on the preceeding line, use the same number here
|
||||
instead of <tt>127.2.2.2</tt></em>.
|
||||
instead of <tt>127.2.2.2</tt></bf></em>.
|
||||
|
||||
<p>By adding this "fake" route for IP traffic, the PPP program can,
|
||||
while idle:
|
||||
|
|
@ -996,7 +992,7 @@ install a new default route that points the actual IP address of the
|
|||
remote end (discovered during the dial-up connection setup).
|
||||
|
||||
A representative '<tt>/etc/ppp/ppp.linkup</tt>' file:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
#########################################################################=
|
||||
|
||||
# PPP Link Up File ('/etc/ppp/ppp.linkup')
|
||||
|
|
@ -1031,7 +1027,7 @@ MYADDR:
|
|||
add 0 0 HISADDR
|
||||
########################################################################
|
||||
# End of /etc/ppp/ppp.linkup
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
Notice that there is a section in this file named "demand:", identical
|
||||
to the configuration name used in the '<tt>/etc/ppp/ppp.conf</tt>'
|
||||
file. This section instructs the PPP program that once a link is
|
||||
|
|
@ -1047,8 +1043,8 @@ established using this configuration, it must:
|
|||
Dial-on-Demand configurations) execute the "delete ALL" and "add 0 0
|
||||
HISADDR" commands in <tt>/etc/ppp/ppp.linkup</tt>.
|
||||
|
||||
<p><bf><em>This is the mechanism that controls the actual on-demand
|
||||
configuration of the link.</em></bf>
|
||||
<p><em><bf>This is the mechanism that controls the actual on-demand
|
||||
configuration of the link.</bf></em>
|
||||
|
||||
<p>All configurations not explicitly named in
|
||||
<tt>/etc/ppp/ppp.linkup</tt> will use whatever commands are in the
|
||||
|
|
@ -1473,7 +1469,7 @@ Esentially, it tells the Name Server:
|
|||
|
||||
<p>Using the '<tt/ee/' editor, create a
|
||||
<tt>/etc/namedb/named.boot</tt> with the following contents:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
; boot file for mini-name server
|
||||
|
||||
directory /etc/namedb
|
||||
|
|
@ -1482,14 +1478,14 @@ directory /etc/namedb
|
|||
|
||||
cache . named.root
|
||||
primary my.domain. mydomain.db
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
<p>Lines that begin with a semi-colon are comments. The significant
|
||||
lines in this file are:
|
||||
<itemize>
|
||||
<item><tt>directory /etc/namedb</tt>
|
||||
<p>Tells the Name Server where to find the configuration files
|
||||
referenced in the remaining sections of
|
||||
the '<tt>/etc/namedb/named.boot</tt>' file.
|
||||
referenced in the remaining sections of the
|
||||
'<tt>/etc/namedb/named.boot</tt>' file.
|
||||
<item><tt>cache . named.root</tt>
|
||||
<p>Tells the Name Server that the list of "Top-Level" DNS servers for
|
||||
the Internet can be found in a file called '<tt>named.root</tt>'.
|
||||
|
|
@ -1516,7 +1512,7 @@ refer to the <tt/named/ manpage.</em>
|
|||
|
||||
<p>The <tt>/etc/namedb/mydomain.db</tt> file for our minimal DNS
|
||||
server has the following contents:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
@ IN SOA my.domain. root.my.domain. (
|
||||
961230 ; Serial
|
||||
3600 ; Refresh
|
||||
|
|
@ -1540,7 +1536,7 @@ $ORIGIN 1.168.192.IN-ADDR.ARPA
|
|||
$ORIGIN 0.0.127.IN-ADDR.ARPA
|
||||
IN NS curly.my.domain.
|
||||
1 IN PTR localhost.my.domain.
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
<p>In simple terms, this file declares that the local DNS server is:
|
||||
<itemize>
|
||||
<item>The Start of Authority for ("SOA") for a domain called
|
||||
|
|
@ -1566,37 +1562,37 @@ changing a single line in '<tt>/etc/sysconfig</tt>' as follows:
|
|||
|
||||
<p> Using the '<tt/ee/' editor, load <tt>/etc/sysconfig</tt>. Scroll
|
||||
down approximately 200 lines until you come to the section that says:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
---
|
||||
# Set to appropriate flags for named, if you have a full-time
|
||||
# connection to the Internet.
|
||||
# For most hosts, flags should be "-b /etc/namedb/named.boot"
|
||||
namedflags="NO"
|
||||
---
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
Change this section to read:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
---
|
||||
# Set to appropriate flags for named, if you have a full-time
|
||||
# connection to the Internet.
|
||||
# For most hosts, flags should be "-b /etc/namedb/named.boot"
|
||||
namedflags="-b /etc/namedb/named.boot"
|
||||
---
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
Save the file and reboot.
|
||||
|
||||
Alternatively, start the Name Server daemon by entering the following
|
||||
command:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
# named -b /etc/namedb/named.boot
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
|
||||
<p>Whenever you modify any of the files in <tt>/etc/namedb</tt> you'll
|
||||
need to kick-start the Name Server process to make it pick up the
|
||||
modifications. This is performed with the following system command:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
# kill -HUP `cat /var/run/named.pid`
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
|
||||
<sect1>
|
||||
<heading>Playing with PPP filters</heading>
|
||||
|
|
@ -1634,7 +1630,7 @@ What follows is a snippet from an operating system which provides a
|
|||
good foundation for "normal" Internet operations while preventing PPP
|
||||
from pumping <em/all/ data over the dial-up connection. Comments
|
||||
briefly describe the logic of each rule set:
|
||||
<code>
|
||||
<tscreen><verb>
|
||||
#
|
||||
# KeepAlive filters
|
||||
# Don't keep Alive with ICMP,DNS and RIP packet
|
||||
|
|
@ -1719,7 +1715,7 @@ briefly describe the logic of each rule set:
|
|||
#
|
||||
# If none of above rules matches, then packet is blocked.
|
||||
#-------
|
||||
</code>
|
||||
</verb></tscreen>
|
||||
<p>Up to 20 distinct filtering rules can be applied to each class of
|
||||
filter. Rules in each class are number sequentially from 0 to 20
|
||||
<em/but none of the rules for a particular filter class take affect
|
||||
|
|
|
|||
Loading…
Reference in a new issue