mirror of https://github.com/tLDP/LDP
Unicode and DocBook XML corrections
files were declared with <?xml version="1.0" encoding="UTF-8"?> but were definitely not UTF-8; corrected and added Unicode BOM Linux-Networking.xml: fixed a doubly-closed </ulink> Overview.xml: there were several large pasted sections of text which contained characters understood to be markup; wrapped the entire sections in <![CDATA[ ]]> blocks; Protocols-Standards-Services.xml: closing </sect1> tags cannot have id="" on them: removed these; wrapped several email addresses with <email/> to allow validation; fixed tons of URLs with proper <ulink/> elements; wrapped a few pasted sections in <![CDATA[ ]]> blocks;
This commit is contained in:
Martin A. Brown
parent
265bdc7bdc
commit
ab2c7e21c5
|
|
@ -54,7 +54,7 @@ towards security is made. It was only intended to provide an overview of this su
|
|||
provide a means by which to extend one's knowledge of networking under Linux and other
|
||||
well established documents. For issues related to networking under Linux that are outside
|
||||
the scope of this document please consult the Linux Documentation Project,
|
||||
<ulink url="http://www.tldp.org"/>http://www.tldp.org</ulink>.
|
||||
<ulink url="http://www.tldp.org">http://www.tldp.org</ulink>.
|
||||
</para>
|
||||
</abstract>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,4 @@
|
|||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<sect1 id="Overview">
|
||||
|
||||
<title>Overview</title>
|
||||
|
|
@ -31,7 +32,7 @@ support under Linux.
|
|||
|
||||
<para>
|
||||
<screen>
|
||||
Orest Zborowski <obz@Kodak.com> produced the original BSD socket
|
||||
Orest Zborowski <email>obz@Kodak.com</email> produced the original BSD socket
|
||||
programming interface for the Linux kernel. This was a big step
|
||||
forward as it allowed many of the existing network applications to be
|
||||
ported to linux without serious modification.
|
||||
|
|
@ -99,8 +100,7 @@ Linux Networking HOWTO, http://tldp.org/HOWTO/NET3-4-HOWTO.html
|
|||
|
||||
<para>
|
||||
|
||||
|
||||
|
||||
<![CDATA[
|
||||
5.1.4. IP Addresses, an Explanation.
|
||||
|
||||
Internet Protocol Addresses are composed of four bytes. The convention
|
||||
|
|
@ -189,17 +189,17 @@ Linux Networking HOWTO, http://tldp.org/HOWTO/NET3-4-HOWTO.html
|
|||
and ask them for the following information:
|
||||
|
||||
|
||||
· Host IP Address
|
||||
· Host IP Address
|
||||
|
||||
· IP network address
|
||||
· IP network address
|
||||
|
||||
· IP broadcast address
|
||||
· IP broadcast address
|
||||
|
||||
· IP netmask
|
||||
· IP netmask
|
||||
|
||||
· Router address
|
||||
· Router address
|
||||
|
||||
· Domain Name Server Address
|
||||
· Domain Name Server Address
|
||||
|
||||
|
||||
You should then configure your linux network device with those
|
||||
|
|
@ -618,7 +618,7 @@ Linux Networking HOWTO, http://tldp.org/HOWTO/NET3-4-HOWTO.html
|
|||
I'm using:
|
||||
|
||||
|
||||
IP Routing is the process by which a host with multiple net
|
||||
IP Routing is the process by which a host with multiple net
|
||||
work connections decides where to deliver IP datagrams it
|
||||
has received.
|
||||
|
||||
|
|
@ -1739,14 +1739,14 @@ Linux Networking HOWTO, http://tldp.org/HOWTO/NET3-4-HOWTO.html
|
|||
| |
|
||||
- -
|
||||
|
||||
The diagram illustrates another possible reason to use IPIP encapsula
|
||||
The diagram illustrates another possible reason to use IPIP encapsula
|
||||
tion, virtual private networking. This example presupposes that you
|
||||
have two machines each with a simple dial up internet connection. Each
|
||||
host is allocated just a single IP address. Behind each of these
|
||||
machines are some private local area networks configured with reserved
|
||||
IP network addresses. Suppose that you want to allow any host on net
|
||||
work A to connect to any host on network B, just as if they were prop
|
||||
erly connected to the Internet with a network route. IPIP encapsula
|
||||
IP network addresses. Suppose that you want to allow any host on net
|
||||
work A to connect to any host on network B, just as if they were prop
|
||||
erly connected to the Internet with a network route. IPIP encapsula
|
||||
tion will allow you to do this. Note, encapsulation does not solve the
|
||||
problem of how you get the hosts on networks A and B to talk to any
|
||||
other on the Internet, you still need tricks like IP Masquerade for
|
||||
|
|
@ -2133,24 +2133,24 @@ In network terminology the word "point" is usually synonymous with "device".
|
|||
|
||||
Some interesting documents:
|
||||
|
||||
· Hardware HOWTO <http://metalab.unc.edu/mdw/HOWTO/Hardware-
|
||||
· Hardware HOWTO <http://metalab.unc.edu/mdw/HOWTO/Hardware-
|
||||
HOWTO.html>
|
||||
|
||||
· Ethernet HOWTO <http://metalab.unc.edu/mdw/HOWTO/Ethernet-
|
||||
· Ethernet HOWTO <http://metalab.unc.edu/mdw/HOWTO/Ethernet-
|
||||
HOWTO.html>
|
||||
|
||||
6.9. Authentication
|
||||
|
||||
There are also various ways of authenticating users in mixed networks.
|
||||
|
||||
· For Linux/Windows NT:http://www.mindware.com.au/ftp/smb-NT-
|
||||
· For Linux/Windows NT:http://www.mindware.com.au/ftp/smb-NT-
|
||||
verify.1.1.tar.gz
|
||||
|
||||
· The PAM (pluggable authentication module) which is a flexible
|
||||
· The PAM (pluggable authentication module) which is a flexible
|
||||
method of Unix authentication: PAM library
|
||||
<http://www.kernel.org/pub/linux/libs/pam/index.html>.
|
||||
|
||||
· Finally, LDAP in Linux
|
||||
· Finally, LDAP in Linux
|
||||
<http://www.umich.edu/~dirsvcs/ldap/index.html>
|
||||
|
||||
7. Remote execution of applications
|
||||
|
|
@ -2179,19 +2179,19 @@ In network terminology the word "point" is usually synonymous with "device".
|
|||
capabilities:
|
||||
|
||||
|
||||
· Linux is a true 32-bit multitasking operating system, robust and
|
||||
· Linux is a true 32-bit multitasking operating system, robust and
|
||||
capable enough to be used in organizations ranging from
|
||||
universities to large corporations.
|
||||
|
||||
· It runs on hardware ranging from low-end 386 boxes to massive
|
||||
· It runs on hardware ranging from low-end 386 boxes to massive
|
||||
ultra-parallel machines in research centres.
|
||||
|
||||
· Out-of-the-box versions are available for Intel, Sparc, and Alpha
|
||||
· Out-of-the-box versions are available for Intel, Sparc, and Alpha
|
||||
architectures, and experimental support exists for Power PC and
|
||||
embedded systems, among others such as SGI, Ultra Sparc, AP1000+,
|
||||
Strong ARM, and MIPS R3000/R4000.
|
||||
|
||||
· Finally, when it comes to networking, Linux is choice. Not only
|
||||
· Finally, when it comes to networking, Linux is choice. Not only
|
||||
because networking is tightly integrated with the OS itself and a
|
||||
plethora of applications is freely available, but for the
|
||||
robustness under heavy loads that can only be achieved after years
|
||||
|
|
@ -2286,8 +2286,9 @@ the sections below.
|
|||
drivers with protocol support.
|
||||
|
||||
|
||||
· WAN resources for Linux:
|
||||
· WAN resources for Linux:
|
||||
http://www.secretagent.com/networking/wan.html
|
||||
]]>
|
||||
|
||||
>Start Binh
|
||||
|
||||
|
|
@ -2496,4 +2497,4 @@ services offered by Linux include mail, news, WWW servers and many
|
|||
more that will be outlined further on in this document.
|
||||
</para>
|
||||
|
||||
</sect1 id="Internet">
|
||||
</sect1>
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<sect1 id="Protocols-Standards-Services">
|
||||
|
||||
<title>Protocols-and-Standards-Services</title>
|
||||
|
||||
<para>
|
||||
<![CDATA[
|
||||
IEEE (Institute of Electrical and Electronics Engineers) 802 Standards
|
||||
|
||||
802.1 Internetworking
|
||||
|
|
@ -17,10 +19,11 @@ IEEE (Institute of Electrical and Electronics Engineers) 802 Standards
|
|||
802.10 Network security
|
||||
802.11 Wireless Networking
|
||||
802.12 High-speed LANs
|
||||
]]>
|
||||
</para>
|
||||
|
||||
<AX25>
|
||||
|
||||
<para>
|
||||
<![CDATA[
|
||||
3.8. Amateur Radio
|
||||
|
||||
The Linux kernel has built-in support for amateur radio protocols.
|
||||
|
|
@ -33,8 +36,9 @@ IEEE (Institute of Electrical and Electronics Engineers) 802 Standards
|
|||
It is similar to X.25 level 2 in structure, with some extensions to
|
||||
make it more useful in the amateur radio environment.
|
||||
|
||||
· Amateur radio on Linux web site <http://radio.linux.org.au/>
|
||||
</AX25>
|
||||
· Amateur radio on Linux web site <http://radio.linux.org.au/>
|
||||
]]>
|
||||
</para>
|
||||
|
||||
NDIS and ODI
|
||||
|
||||
|
|
@ -101,7 +105,7 @@ as another Macintosh on the network.
|
|||
- http://www.umich.edu/~rsug/netatalk/
|
||||
- http://www.umich.edu/~rsug/netatalk/faq.html
|
||||
|
||||
</sect1 id="Appletalk">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="ARCnet">
|
||||
|
||||
|
|
@ -126,7 +130,7 @@ TCNS) support speeds of 20 Mbps and 100 Mbps, but have not really caught on.
|
|||
|
||||
- ARCnet HOWTO
|
||||
|
||||
</sect1 id="ARCnet">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="ATM">
|
||||
|
||||
|
|
@ -149,17 +153,17 @@ SVCs), IP over ATM, LAN emulation....
|
|||
</para>
|
||||
|
||||
<para>
|
||||
The Linux ATM-Linux home page is at, <http://lrcwww.epfl.ch/linux-atm/>
|
||||
The Linux ATM-Linux home page is at, <ulink url="http://lrcwww.epfl.ch/linux-atm/"/>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Werner Almesberger <werner.almesberger@lrc.di.epfl.ch> is managing a
|
||||
Werner Almesberger <email>werner.almesberger@lrc.di.epfl.ch</email> is managing a
|
||||
project to provide Asynchronous Transfer Mode support for Linux.
|
||||
Current information on the status of the project may be obtained from,
|
||||
http://lrcwww.epfl.ch
|
||||
</para>
|
||||
|
||||
</sect1 id="ATM">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="DDS-Switched56">
|
||||
|
||||
|
|
@ -181,7 +185,7 @@ on demand rather than continuously, and you are billed for the hours that
|
|||
you use it. ISDN has largely replaced Switched 56 for this purpose.
|
||||
</para>
|
||||
|
||||
</sect1 id="DDS-Switched56">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="DECnet">
|
||||
|
||||
|
|
@ -192,7 +196,7 @@ Support for DECnet is currently being worked on. You should expect it
|
|||
to appear in a late 2.1.* kernel.
|
||||
</para>
|
||||
|
||||
</sect1 id="DECnet">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="DLC">
|
||||
|
||||
|
|
@ -208,7 +212,7 @@ used by many network-aware printers such Hewlett-Packard's JetDirect
|
|||
interface.
|
||||
</para>
|
||||
|
||||
</sect1="DLC">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="EQL">
|
||||
|
||||
|
|
@ -221,7 +225,7 @@ it is cheaper to use multiple lower speed lines than to have one high
|
|||
speed line installed. In short, EQL is multiple line traffic equaliser.
|
||||
</para>
|
||||
|
||||
</sect1 id="EQL">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Ethernet">
|
||||
|
||||
|
|
@ -267,7 +271,7 @@ It is now often utilized as a more inexpensive option to Optic Fibre.
|
|||
|
||||
* Ethernet-Howto
|
||||
|
||||
</sect1 id="Ethernet">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="FDDI">
|
||||
|
||||
|
|
@ -297,7 +301,7 @@ disadvantage of FDDI is its high cost and the difficult in installing and
|
|||
maintaing fiber optic cable.
|
||||
</para>
|
||||
|
||||
</sect1 id="FDDI">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Frame-Relay">
|
||||
|
||||
|
|
@ -327,7 +331,7 @@ network using a Frame Relay Access Device (FRAD). The Linux Frame Relay
|
|||
supports IP over Frame Relay as described in RFC-1490.
|
||||
</para>
|
||||
|
||||
</sect1 id="Frame-Relay">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="NetBEUI">
|
||||
|
||||
|
|
@ -354,7 +358,7 @@ for some operating systems (such as Windows for Workgroups and Windows 95),
|
|||
Microsoft recommends TCP/IP over NetBEUI for most Windows NT networks.
|
||||
</para>
|
||||
|
||||
</sect1 id="NetBEUI">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="IPX">
|
||||
|
||||
|
|
@ -394,21 +398,21 @@ in the packet. Typical frame types used in NetWare networks
|
|||
Linux has a very clean IPX/SPX implementation, allowing it to be
|
||||
configured as an:
|
||||
|
||||
· IPX router
|
||||
· IPX bridge
|
||||
· NCP client and/or NCP Server (for sharing files)
|
||||
· Novell Print Client, Novell Print Server
|
||||
· IPX router
|
||||
· IPX bridge
|
||||
· NCP client and/or NCP Server (for sharing files)
|
||||
· Novell Print Client, Novell Print Server
|
||||
|
||||
And to:
|
||||
|
||||
· Enable PPP/IPX, allowing a Linux box to act as a PPP server/client
|
||||
· Perform IPX tunnelling through IP, allowing the connection of two
|
||||
· Enable PPP/IPX, allowing a Linux box to act as a PPP server/client
|
||||
· Perform IPX tunnelling through IP, allowing the connection of two
|
||||
IPX networks through an IP only link
|
||||
</para>
|
||||
|
||||
* IPX-SPX HOWTO
|
||||
|
||||
</sect1 id="IPX">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Leased-Line">
|
||||
|
||||
|
|
@ -457,7 +461,7 @@ OC-12 level would equate to a data transfer rate of 622 Mbps. OC-1 and
|
|||
OC-3 are the most commonly used SONET lines.
|
||||
</para>
|
||||
|
||||
</sect id="Leased-Line">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="PLIP">
|
||||
|
||||
|
|
@ -488,7 +492,7 @@ It uses a parallel port and a special cable, achieving speeds of
|
|||
- PLIP HOWTO
|
||||
- Networking HOWTO
|
||||
|
||||
</sect1 id="PLIP">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="PPP-and-SLIP">
|
||||
|
||||
|
|
@ -500,12 +504,12 @@ Protocol) and SLIP (Serial Line IP). PPP is the most popular
|
|||
way individual users access their ISPs (Internet Service
|
||||
Providers).
|
||||
|
||||
· Linux PPP HOWTO <http://metalab.unc.edu/mdw/HOWTO/PPP-HOWTO.html>
|
||||
· <ulink url="http://metalab.unc.edu/mdw/HOWTO/PPP-HOWTO.html">Linux PPP HOWTO</ulink>
|
||||
|
||||
· PPP/SLIP emulator <http://metalab.unc.edu/mdw/HOWTO/mini/SLIP-PPP-
|
||||
Emulator.html>
|
||||
· <ulink url="http://metalab.unc.edu/mdw/HOWTO/mini/SLIP-PPP-Emulator.html">PPP/SLIP emulator</ulink>
|
||||
</para>
|
||||
|
||||
</sect1 id="PPP-and-SLIP">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Token-Ring">
|
||||
|
||||
|
|
@ -551,7 +555,7 @@ problem. This makes Token Ring a reliable choice for networking.
|
|||
|
||||
- Token-Ring HOWTO
|
||||
|
||||
</sect1 id="Token-Ring">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="X25">
|
||||
|
||||
|
|
@ -585,7 +589,7 @@ provides error control and accouting for users of the network.
|
|||
|
||||
- X25 HOWTO
|
||||
|
||||
</sect1 id="X25">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="IPv6">
|
||||
|
||||
|
|
@ -593,6 +597,7 @@ provides error control and accouting for users of the network.
|
|||
|
||||
|
||||
<para>
|
||||
<![CDATA[
|
||||
2.1. What is IPv6?
|
||||
|
||||
IPv6, sometimes also referred to as IPng (IP Next Generation)
|
||||
|
|
@ -637,7 +642,7 @@ To-do: better time-line, more content...
|
|||
The first IPv6 related network code was added to the Linux kernel 2.1.8 in
|
||||
November 1996 by Pedro Roque. It was based on the BSD API:
|
||||
diff -u --recursive --new-file v2.1.7/linux/include/linux/in6.h
|
||||
¬ linux/include/linux/in6.h
|
||||
¬ linux/include/linux/in6.h
|
||||
--- v2.1.7/linux/include/linux/in6.h Thu Jan 1 02:00:00 1970
|
||||
+++ linux/include/linux/in6.h Sun Nov 3 11:04:42 1996
|
||||
@@ -0,0 +1,99 @@
|
||||
|
|
@ -685,8 +690,10 @@ development series 2.5.x to insert all of their current extensions into this
|
|||
development release. Hopefully the 2.6.x kernel series will contain a true
|
||||
and up-to-date IPv6 implementation.
|
||||
-----------------------------------------------------------------------------
|
||||
]]>
|
||||
</para>
|
||||
|
||||
</sect1 id="IPv6">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="STRIP">
|
||||
|
||||
|
|
@ -726,6 +733,7 @@ kernel compilation options are given below.
|
|||
|
||||
<para>
|
||||
<screen>
|
||||
<![CDATA[
|
||||
Kernel Compile Options:
|
||||
|
||||
Network device support --->
|
||||
|
|
@ -733,10 +741,11 @@ kernel compilation options are given below.
|
|||
....
|
||||
[*] Radio network interfaces
|
||||
< > STRIP (Metricom starmode radio IP)
|
||||
]]>
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
</sect1 id="STRIP">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="WaveLAN">
|
||||
|
||||
|
|
@ -754,9 +763,11 @@ You can get information on the Wavelan card from wavelan.com.
|
|||
|
||||
<para>
|
||||
Wavelan device names are `eth0', `eth1', etc.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
<![CDATA[
|
||||
Kernel Compile Options:
|
||||
|
||||
Network device support --->
|
||||
|
|
@ -765,10 +776,11 @@ Wavelan device names are `eth0', `eth1', etc.
|
|||
[*] Radio network interfaces
|
||||
....
|
||||
<*> WaveLAN support
|
||||
]]>
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
</sect1 id="WaveLAN">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="ISDN">
|
||||
|
||||
|
|
@ -822,11 +834,12 @@ commands). The possibilities range from simply using a terminal
|
|||
program to connections via HDLC (using included devices) to full
|
||||
connection to the Internet with PPP to audio applications.
|
||||
|
||||
· FAQ for isdn4linux: http://ww.isdn4linux.de/faq/
|
||||
· FAQ for isdn4linux: http://ww.isdn4linux.de/faq/
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<screen>
|
||||
<![CDATA[
|
||||
Kernel Compile Options:
|
||||
|
||||
ISDN subsystem --->
|
||||
|
|
@ -836,6 +849,7 @@ connection to the Internet with PPP to audio applications.
|
|||
< > ICN 2B and 4B support
|
||||
< > PCBIT-D support
|
||||
< > Teles/NICCY1016PC/Creatix support
|
||||
]]>
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
|
|
@ -845,9 +859,9 @@ of internal ISDN cards. These are those listed in the kernel
|
|||
configuration options:
|
||||
</para>
|
||||
|
||||
· ICN 2B and 4B
|
||||
· Octal PCBIT-D
|
||||
· Teles ISDN-cards and compatibles
|
||||
· ICN 2B and 4B
|
||||
· Octal PCBIT-D
|
||||
· Teles ISDN-cards and compatibles
|
||||
|
||||
<para>
|
||||
Some of these cards require software to be downloaded to them to make
|
||||
|
|
@ -870,7 +884,7 @@ modified version. Details of where to find it are available in the
|
|||
documentation referred to above.
|
||||
</para>
|
||||
|
||||
</sect1 id="ISDN">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="NIS">
|
||||
|
||||
|
|
@ -886,7 +900,7 @@ password entry existing on each machine; only the main database needs
|
|||
to be maintained.
|
||||
</para>
|
||||
|
||||
</sect1 id="NIS">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Services">
|
||||
|
||||
|
|
@ -895,7 +909,7 @@ to be maintained.
|
|||
<para>
|
||||
</para>
|
||||
|
||||
</sect1 id="Services">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Database">
|
||||
|
||||
|
|
@ -916,7 +930,7 @@ lacking transaction support (due to speed concerns), a future version of MySQL w
|
|||
|
||||
* Sybase Adaptive Server Anywhere for Linux HOWTO
|
||||
|
||||
</sect1 id="Database">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="DHCP">
|
||||
|
||||
|
|
@ -950,7 +964,7 @@ especially in large networks or networks which have lots of mobile users.
|
|||
Resources section at the end of the document). You can also read
|
||||
[32]http://web.syr.edu/~jmwobus/comfaqs/dhcp.faq.html.
|
||||
|
||||
</sect1 id="DHCP">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="DNS">
|
||||
|
||||
|
|
@ -958,7 +972,7 @@ especially in large networks or networks which have lots of mobile users.
|
|||
|
||||
Setting Up Your New Domain Mini-HOWTO.
|
||||
|
||||
</sect1 id="DNS">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="FTP">
|
||||
|
||||
|
|
@ -993,7 +1007,7 @@ some are text-based.
|
|||
|
||||
* FTP HOWTO
|
||||
|
||||
</sect1 id="FTP">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="LDAP">
|
||||
|
||||
|
|
@ -1006,7 +1020,7 @@ create LDAP databases, how to add, how to update and how to delete
|
|||
information on the directory. This paper is mostly based on the University of
|
||||
Michigan LDAP information pages and on the OpenLDAP Administrator's Guide.
|
||||
|
||||
</sect1 id="LDAP">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="NFS">
|
||||
|
||||
|
|
@ -1079,16 +1093,16 @@ Start the automounter. From now on, whenever you try to access the inexistent mo
|
|||
|
||||
NFS-related documents:
|
||||
|
||||
· http://metalab.unc.edu/mdw/HOWTO/mini/NFS-Root.html
|
||||
· http://metalab.unc.edu/mdw/HOWTO/mini/NFS-Root.html
|
||||
|
||||
· http://metalab.unc.edu/mdw/HOWTO/Diskless-HOWTO.html
|
||||
· http://metalab.unc.edu/mdw/HOWTO/Diskless-HOWTO.html
|
||||
|
||||
· http://metalab.unc.edu/mdw/HOWTO/mini/NFS-Root-Client-mini-
|
||||
· http://metalab.unc.edu/mdw/HOWTO/mini/NFS-Root-Client-mini-
|
||||
HOWTO/index.html
|
||||
|
||||
· http://www.redhat.com/support/docs/rhl/NFS-Tips/NFS-Tips.html
|
||||
· http://www.redhat.com/support/docs/rhl/NFS-Tips/NFS-Tips.html
|
||||
|
||||
· http://metalab.unc.edu/mdw/HOWTO/NFS-HOWTO.html
|
||||
· http://metalab.unc.edu/mdw/HOWTO/NFS-HOWTO.html
|
||||
|
||||
CODA can be found at: http://www.coda.cs.cmu.edu/
|
||||
|
||||
|
|
@ -1114,16 +1128,16 @@ Start the automounter. From now on, whenever you try to access the inexistent mo
|
|||
|
||||
NFS-related documents:
|
||||
|
||||
· http://metalab.unc.edu/mdw/HOWTO/mini/NFS-Root.html
|
||||
· http://metalab.unc.edu/mdw/HOWTO/mini/NFS-Root.html
|
||||
|
||||
· http://metalab.unc.edu/mdw/HOWTO/Diskless-HOWTO.html
|
||||
· http://metalab.unc.edu/mdw/HOWTO/Diskless-HOWTO.html
|
||||
|
||||
· http://metalab.unc.edu/mdw/HOWTO/mini/NFS-Root-Client-mini-
|
||||
· http://metalab.unc.edu/mdw/HOWTO/mini/NFS-Root-Client-mini-
|
||||
HOWTO/index.html
|
||||
|
||||
· http://www.redhat.com/support/docs/rhl/NFS-Tips/NFS-Tips.html
|
||||
· http://www.redhat.com/support/docs/rhl/NFS-Tips/NFS-Tips.html
|
||||
|
||||
· http://metalab.unc.edu/mdw/HOWTO/NFS-HOWTO.html
|
||||
· http://metalab.unc.edu/mdw/HOWTO/NFS-HOWTO.html
|
||||
|
||||
CODA can be found at: http://www.coda.cs.cmu.edu/
|
||||
|
||||
|
|
@ -1197,7 +1211,7 @@ http://www.nfsv4.org). The advantage of NFS today is that it is mature,
|
|||
standard, well understood, and supported robustly across a variety of
|
||||
platforms.
|
||||
|
||||
</sect1 id="NFS">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Samba">
|
||||
|
||||
|
|
@ -1227,12 +1241,11 @@ platforms.
|
|||
that Samba is the only SMB server available which will scale to many tens of thousands
|
||||
of users without crashing"
|
||||
|
||||
· Samba project home page <http://samba.anu.edu.au/samba/>
|
||||
· <ulink url="http://samba.anu.edu.au/samba/">Samba project home page</ulink>
|
||||
|
||||
· SMB HOWTO <http://metalab.unc.edu/mdw/HOWTO/SMB-HOWTO.html>
|
||||
· <ulink url="http://metalab.unc.edu/mdw/HOWTO/SMB-HOWTO.html">SMB HOWTO</ulink>
|
||||
|
||||
· Printing HOWTO <http://metalab.unc.edu/mdw/HOWTO/Printing-
|
||||
HOWTO.html>
|
||||
· <ulink url="http://metalab.unc.edu/mdw/HOWTO/Printing-HOWTO.html">Printing HOWTO</ulink>
|
||||
|
||||
<glossentry>
|
||||
<glossterm>
|
||||
|
|
@ -1274,7 +1287,7 @@ Samba adds Windows-networking support to UNIX. Whereas NFS is the most popular p
|
|||
Ricardo Alexandre Mattar
|
||||
v1.2, 2004-05-21
|
||||
|
||||
</sect1 id="SAMBA">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="SSH">
|
||||
|
||||
|
|
@ -1315,12 +1328,11 @@ Java and Embedded OSes used in routers.
|
|||
|
||||
<para>
|
||||
Encrypted remote shell sessions are available through SSH
|
||||
(http://www.ssh.fi/sshprotocols2/index.html
|
||||
<http://www.ssh.fi/sshprotocols2/index.html>) thus effectively
|
||||
allowing secure remote administration.
|
||||
(<ulink url="http://www.ssh.fi/sshprotocols2/index.html"/>)
|
||||
thus effectively allowing secure remote administration.
|
||||
</para>
|
||||
|
||||
</sect1 id="SSH">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Telnet">
|
||||
|
||||
|
|
@ -1352,11 +1364,11 @@ Please consult RFC 854 for further details behind its implementation.
|
|||
</para>
|
||||
|
||||
<para>
|
||||
· Telnet related software
|
||||
<http://metalab.unc.edu/pub/Linux/system/network/telnet/>
|
||||
· <ulink url="http://metalab.unc.edu/pub/Linux/system/network/telnet/">
|
||||
Telnet related software</ulink>
|
||||
</para>
|
||||
|
||||
</sect1 id="Telnet">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="TFTP">
|
||||
|
||||
|
|
@ -1449,7 +1461,7 @@ to test the server. At the tftp prompt, you can issue the commands put and
|
|||
get.
|
||||
</para>
|
||||
|
||||
</sect1 id="TFTP">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="VNC">
|
||||
|
||||
|
|
@ -1486,24 +1498,24 @@ get.
|
|||
open standards which have been carefully examined and tested.
|
||||
|
||||
|
||||
· A client implementation of the PPTP for Linux is available here
|
||||
<http://www.pdos.lcs.mit.edu/~cananian/Projects/PPTP/>
|
||||
· A client implementation of the PPTP for Linux is available here
|
||||
<ulink url="http://www.pdos.lcs.mit.edu/~cananian/Projects/PPTP/"/>
|
||||
|
||||
· More on Linux PPTP can be found here
|
||||
<http://bmrc.berkeley.edu/people/chaffee/linux_pptp.html>
|
||||
· More on Linux PPTP can be found here
|
||||
<ulink url="http://bmrc.berkeley.edu/people/chaffee/linux_pptp.html"/>
|
||||
|
||||
Mobile IP:
|
||||
|
||||
· http://www.hpl.hp.com/personal/Jean_Tourrilhes/MobileIP/mip.html
|
||||
· <ulink url="http://www.hpl.hp.com/personal/Jean_Tourrilhes/MobileIP/mip.html"/>
|
||||
|
||||
· http://metalab.unc.edu/mdw/HOWTO/NET3-4-HOWTO-6.html#ss6.12
|
||||
· <ulink url="http://metalab.unc.edu/mdw/HOWTO/NET3-4-HOWTO-6.html#ss6.12"/>
|
||||
|
||||
Virtual Private Networks related documents:
|
||||
|
||||
|
||||
· http://metalab.unc.edu/mdw/HOWTO/mini/VPN.html
|
||||
· <ulink url="http://metalab.unc.edu/mdw/HOWTO/mini/VPN.html"/>
|
||||
|
||||
· http://sites.inka.de/sites/bigred/devel/cipe.html
|
||||
· <ulink url="http://sites.inka.de/sites/bigred/devel/cipe.html"/>
|
||||
|
||||
|
||||
7.4. VNC
|
||||
|
|
@ -1523,7 +1535,7 @@ get.
|
|||
allowing 386s with as little as 4 MB of RAM to become fully functional
|
||||
X-Terminals.
|
||||
|
||||
· VNC web site <http://www.orl.co.uk/vnc/>
|
||||
· <ulink url="http://www.orl.co.uk/vnc/">VNC web site</ulink>
|
||||
|
||||
<para>
|
||||
Virtual Network Computing (VNC) allows a user to operate a session running on another machine.
|
||||
|
|
@ -1569,14 +1581,14 @@ vncviewer [host]:[screen-number]
|
|||
|
||||
10.1. Web Sites
|
||||
|
||||
Cipe Home Page <http://sites.inka.de/~bigred/devel/cipe.html>
|
||||
<ulink url="http://sites.inka.de/~bigred/devel/cipe.html">Cipe Home Page</ulink>
|
||||
|
||||
Masq Home Page <http://ipmasq.cjb.net>
|
||||
<ulink url="http://ipmasq.cjb.net">Masq Home Page</ulink>
|
||||
|
||||
Samba Home Page <http://samba.anu.edu.au>
|
||||
<ulink url="http://samba.anu.edu.au">Samba Home Page</ulink>
|
||||
|
||||
Linux HQ <http://www.linuxhq.com> ---great site for lots of linux
|
||||
info
|
||||
<ulink url="http://www.linuxhq.com">Linux HQ</ulink>
|
||||
---great site for lots of linux info
|
||||
|
||||
10.2. Documentation
|
||||
|
||||
|
|
@ -1588,7 +1600,7 @@ vncviewer [host]:[screen-number]
|
|||
|
||||
IPChains-Howto, by Paul Russell, Paul.Russell@rustcorp.com.au
|
||||
|
||||
</sect1 id="VNC">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Web-Serving">
|
||||
|
||||
|
|
@ -1616,7 +1628,7 @@ will reveal a multitude of servers.
|
|||
</para>
|
||||
|
||||
<para>
|
||||
Most Linux distributions include Apache <http://www.apache.org>.
|
||||
Most Linux distributions include Apache <ulink url="http://www.apache.org"/>.
|
||||
Apache is the number one server on the internet according to
|
||||
http://www.netcraft.co.uk/survey/ . More than a half of all internet
|
||||
sites are running Apache or one of it derivatives. Apache's advantages
|
||||
|
|
@ -1631,9 +1643,9 @@ Optional support for SSL (which enables secure transactions) is also
|
|||
available at:
|
||||
</para>
|
||||
|
||||
· http://www.apache-ssl.org/
|
||||
· http://raven.covalent.net/
|
||||
· http://www.c2.net/
|
||||
· http://www.apache-ssl.org/
|
||||
· http://raven.covalent.net/
|
||||
· http://www.c2.net/
|
||||
|
||||
Dynamic Web content generation
|
||||
|
||||
|
|
@ -1659,13 +1671,12 @@ those in the Database serving section and most ODBC compliant
|
|||
databases. The language itself borrows its structure from Perl and C.
|
||||
</para>
|
||||
|
||||
· http://metalab.unc.edu/mdw/HOWTO/WWW-HOWTO.html
|
||||
· http://metalab.unc.edu/mdw/HOWTO/Virtual-Services-HOWTO.html
|
||||
· http://metalab.unc.edu/mdw/HOWTO/Intranet-Server-HOWTO.html
|
||||
· Web servers for Linux
|
||||
<http://www.linuxlinks.com/Software/Internet/WebServers/>
|
||||
· http://metalab.unc.edu/mdw/HOWTO/WWW-HOWTO.html
|
||||
· http://metalab.unc.edu/mdw/HOWTO/Virtual-Services-HOWTO.html
|
||||
· http://metalab.unc.edu/mdw/HOWTO/Intranet-Server-HOWTO.html
|
||||
· <ulink url="http://www.linuxlinks.com/Software/Internet/WebServers/">Web servers for Linux</ulink>
|
||||
|
||||
</sect1 id="Web-Serving">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="X11">
|
||||
|
||||
|
|
@ -1699,9 +1710,9 @@ is to act as pure X servers. Such systems are called X terminals.
|
|||
|
||||
<para>
|
||||
A free port of the X Window System exists for Linux and can be found
|
||||
at: Xfree <http://www.xfree86.org/>. It is included in most Linux
|
||||
at: Xfree <ulink url="http://www.xfree86.org/"/>. It is included in most Linux
|
||||
distributions.
|
||||
<para>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
For further information regarding X please see:
|
||||
|
|
@ -1711,23 +1722,23 @@ X11, LBX, DXPC, NXServer, SSH, MAS
|
|||
|
||||
Related HOWTOs:
|
||||
|
||||
· Remote X Apps HOWTO
|
||||
· Linux XDMCP HOWTO
|
||||
· XDM and X Terminal mini-HOWTO
|
||||
· The Linux XFree86 HOWTO
|
||||
· ATI R200 + XFree86 4.x mini-HOWTO
|
||||
· Second Mouse in X mini-HOWTO
|
||||
· Linux Touch Screen HOWTO
|
||||
· XFree86 Video Timings HOWTO
|
||||
· Linux XFree-to-Xinside mini-HOWTO
|
||||
· XFree Local Multi-User HOWTO
|
||||
· Using Xinerama to MultiHead XFree86 V. 4.0+
|
||||
· Connecting X Terminals to Linux Mini-HOWTO
|
||||
· How to change the title of an xterm
|
||||
· X Window System Architecture Overview HOWTO
|
||||
· The X Window User HOWTO
|
||||
· Remote X Apps HOWTO
|
||||
· Linux XDMCP HOWTO
|
||||
· XDM and X Terminal mini-HOWTO
|
||||
· The Linux XFree86 HOWTO
|
||||
· ATI R200 + XFree86 4.x mini-HOWTO
|
||||
· Second Mouse in X mini-HOWTO
|
||||
· Linux Touch Screen HOWTO
|
||||
· XFree86 Video Timings HOWTO
|
||||
· Linux XFree-to-Xinside mini-HOWTO
|
||||
· XFree Local Multi-User HOWTO
|
||||
· Using Xinerama to MultiHead XFree86 V. 4.0+
|
||||
· Connecting X Terminals to Linux Mini-HOWTO
|
||||
· How to change the title of an xterm
|
||||
· X Window System Architecture Overview HOWTO
|
||||
· The X Window User HOWTO
|
||||
|
||||
</sect1 id="X11">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Email">
|
||||
|
||||
|
|
@ -1745,7 +1756,7 @@ In times gone by, users would Telnet into the SMTP server itself and use a comma
|
|||
|
||||
* The Linux Mail User HOWTO
|
||||
|
||||
</sect1 id="Email-Hosting">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Proxy-Caching">
|
||||
|
||||
|
|
@ -1766,9 +1777,9 @@ In times gone by, users would Telnet into the SMTP server itself and use a comma
|
|||
Several proxy servers exist for Linux. One popular solution is the
|
||||
Apache proxy module. A more complete and robust implementation of an
|
||||
HTTP proxy is SQUID.
|
||||
· Apache <http://www.apache.org>
|
||||
· <ulink url="http://www.apache.org">Apache</ulink>
|
||||
|
||||
· Squid <http://squid.nlanr.net/>
|
||||
· <ulink url="http://squid.nlanr.net/">Squid</ulink>
|
||||
|
||||
<title>Proxy-Caching</title>
|
||||
|
||||
|
|
@ -1783,7 +1794,7 @@ Traffic Control HOWTO
|
|||
|
||||
ProxyARP Subnetting HOWTO
|
||||
|
||||
</sect1 id="Proxy-Caching">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="NTP">
|
||||
|
||||
|
|
@ -2041,7 +2052,7 @@ You can also use the TZ environment variable to change the current
|
|||
time zone, which is handy of you're logged in remotely to a machine in
|
||||
another time zone. Also see the man pages for tzset and tzfile.
|
||||
This is nicely summarized at
|
||||
<http://www.linuxsa.org.au/tips/time.html>
|
||||
<ulink url="http://www.linuxsa.org.au/tips/time.html"/>
|
||||
</para>
|
||||
|
||||
2.5. The Bottom Line
|
||||
|
|
@ -2086,7 +2097,7 @@ Xntpd (NTPv3) has been replaced by ntpd (NTPv4); the earlier version
|
|||
is no longer being maintained.
|
||||
</para>
|
||||
|
||||
</para>
|
||||
<para>
|
||||
Ntpd is the standard program for synchronizing clocks across a
|
||||
network, and it comes with a list of public time servers you can
|
||||
connect to. It can be a little more complicated to set up, but if
|
||||
|
|
@ -2096,11 +2107,11 @@ take a look at it.
|
|||
|
||||
<para>
|
||||
The "home base" for information on ntpd is the NTP website at
|
||||
<http://www.eecis.udel.edu/~ntp/> which also includes links to all
|
||||
<ulink url="http://www.eecis.udel.edu/~ntp/"/> which also includes links to all
|
||||
kinds of interesting time-related stuff (including software for other
|
||||
OS's). Some linux distributions include ntpd on the CD. There is a
|
||||
list of public time servers at
|
||||
<http://www.eecis.udel.edu/~mills/ntp/clock2.html>.
|
||||
<ulink url="http://www.eecis.udel.edu/~mills/ntp/clock2.html"/>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
|
@ -2117,13 +2128,13 @@ are some cheaper alternatives (discussed in later sections). In the
|
|||
past most were WWV or WWVB receivers, but now most of them seem to be
|
||||
GPS receivers. NIST has a PDF file that lists manufacturers of radio
|
||||
clocks on their website at
|
||||
<http://www.boulder.nist.gov/timefreq/links.htm> (near the bottom of
|
||||
<ulink url="http://www.boulder.nist.gov/timefreq/links.htm"/> (near the bottom of
|
||||
the page). The NTP website also includes many links to manufacturers
|
||||
of radio clocks at <http://www.eecis.udel.edu/~ntp/hardware.htm> and
|
||||
<http://www.eecis.udel.edu/~mills/ntp/refclock.htm>. Either list may
|
||||
of radio clocks at <ulink url="http://www.eecis.udel.edu/~ntp/hardware.htm"/> and
|
||||
<ulink url="http://www.eecis.udel.edu/~mills/ntp/refclock.htm"/>. Either list may
|
||||
or may not be up to date at any given time :-). The list of drivers
|
||||
for ntpd is at
|
||||
<http://www.eecis.udel.edu/~ntp/ntp_spool/html/refclock.htm>.
|
||||
<ulink url="http://www.eecis.udel.edu/~ntp/ntp_spool/html/refclock.htm"/>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
|
@ -2148,7 +2159,7 @@ turned off for long periods of time.
|
|||
|
||||
<para>
|
||||
You can get more information from Richard Curnow's website at
|
||||
<http://www.rrbcurnow.freeuk.com/chrony> or <http://go.to/chrony>.
|
||||
<ulink url="http://www.rrbcurnow.freeuk.com/chrony"/> or <ulink url="http://go.to/chrony"/>.
|
||||
There are also two chrony mailing lists, one for announcements and one
|
||||
for discussion by users. For information send email to chrony-users-
|
||||
subscribe@egroups.com or chrony-announce-subscribe@egroups.com
|
||||
|
|
@ -2171,7 +2182,7 @@ machines on a LAN.
|
|||
|
||||
<para>
|
||||
I've sometimes had trouble reaching his website at
|
||||
<http://Cr.yp.to/clockspeed.html>, so if you get a DNS error try again
|
||||
<ulink url="http://Cr.yp.to/clockspeed.html"/>, so if you get a DNS error try again
|
||||
on another day. I'll try to update this section if I get some better
|
||||
information.
|
||||
</para>
|
||||
|
|
@ -2197,10 +2208,10 @@ Time.
|
|||
If you run a dual-boot system that spends a lot of time running
|
||||
Windows, you may want to check out some of the clock software
|
||||
available for that OS instead. Follow the links on the NTP website at
|
||||
<http://www.eecis.udel.edu/~ntp/software.html>.
|
||||
<ulink url="http://www.eecis.udel.edu/~ntp/software.html"/>.
|
||||
</para>
|
||||
|
||||
</sect1 id="NTP">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Traffic-Control">
|
||||
|
||||
|
|
@ -2224,29 +2235,29 @@ dropping. This HOWTO provides an introduction and overview of the
|
|||
capabilities and implementation of traffic control under Linux.
|
||||
</para>
|
||||
|
||||
* the linux DiffServ project
|
||||
* the linux DiffServ project
|
||||
|
||||
* HTB site (Martin "devik" Devera)
|
||||
* HTB site (Martin "devik" Devera)
|
||||
|
||||
* Traffic Control Next Generation (tcng)
|
||||
* Traffic Control Next Generation (tcng)
|
||||
|
||||
TCNG manual (Werner Almesberger)
|
||||
|
||||
* iproute2 (Alexey Kuznetsov)
|
||||
* iproute2 (Alexey Kuznetsov)
|
||||
|
||||
iproute2 manual (Alexey Kuznetsov)
|
||||
|
||||
* Research and documentation on traffic control under linux (Stef Coene)
|
||||
* Research and documentation on traffic control under linux (Stef Coene)
|
||||
|
||||
* LARTC HOWTO (bert hubert, et. al.)
|
||||
* LARTC HOWTO (bert hubert, et. al.)
|
||||
|
||||
* guide to IP networking with linux (Martin A. Brown)
|
||||
* guide to IP networking with linux (Martin A. Brown)
|
||||
|
||||
* http://metalab.unc.edu/mdw/HOWTO/NET3-4-HOWTO-6.html#ss6.15
|
||||
* <ulink url="http://metalab.unc.edu/mdw/HOWTO/NET3-4-HOWTO-6.html#ss6.15"/>
|
||||
|
||||
* Traffic Control HOWTO
|
||||
|
||||
</sect1 id="Traffic-Control">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Load-Balancing">
|
||||
|
||||
|
|
@ -2267,11 +2278,10 @@ appearance that only one server exists.
|
|||
</para>
|
||||
|
||||
<para>
|
||||
Linux IP-NAT information may be found here <http://www.csn.tu-
|
||||
chemnitz.de/HyperNews/get/linux-ip-nat.html>
|
||||
Linux IP-NAT information may be found here <ulink url="http://www.csn.tu-chemnitz.de/HyperNews/get/linux-ip-nat.html"/>
|
||||
</para>
|
||||
|
||||
</sect1 id="Load-Balancing">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Bandwidth-Limiting">
|
||||
|
||||
|
|
@ -2335,7 +2345,7 @@ Indonesian translation of this HOWTO by Rahmat Rafiudin mjl_id@yahoo.com
|
|||
[http://raf.unisba.ac.id/resources/BandwidthLimitingHOWTO/index.html] http://
|
||||
raf.unisba.ac.id/resources/BandwidthLimitingHOWTO/index.html
|
||||
|
||||
</sect1 id="Bandwidth-Limiting">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="IP-Accounting">
|
||||
|
||||
|
|
@ -2470,7 +2480,7 @@ you'll now need to use ipchains instead of ipfwadm to configure your
|
|||
filters. (From Documentation/Changes in the latest kernel sources).
|
||||
</para>
|
||||
|
||||
</sect1 id="IP-Accounting">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="IP-Aliasing">
|
||||
|
||||
|
|
@ -2498,7 +2508,7 @@ World Wide Web and ftp offerings for their customers. You can refer to
|
|||
the ``IP-Alias mini-HOWTO'' for more information than you find here.
|
||||
</para>
|
||||
|
||||
</sect1 id="IP-Aliasing">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Multicasting">
|
||||
|
||||
|
|
@ -2506,8 +2516,9 @@ the ``IP-Alias mini-HOWTO'' for more information than you find here.
|
|||
|
||||
<para>
|
||||
* Multicast HOWTO
|
||||
</para>
|
||||
|
||||
</sect1 id="Multicast">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Network-Management">
|
||||
|
||||
|
|
@ -2520,15 +2531,15 @@ projects are linuxconf and webmin:
|
|||
</para>
|
||||
|
||||
<para>
|
||||
· Webmin <http://www.webmin.com/webmin/>
|
||||
· Linuxconf <http://www.solucorp.qc.ca/linuxconf/>
|
||||
· <ulink url="http://www.webmin.com/webmin/">Webmin</ulink>
|
||||
· <ulink url="http://www.solucorp.qc.ca/linuxconf/">Linuxconf</ulink>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Other tools include network traffic analysis tools, network security
|
||||
tools, monitoring tools, configuration tools, etc. An archive of many
|
||||
of these tools may be found at Metalab
|
||||
<http://www.metalab.unc.edu/pub/Linux/system/network/>
|
||||
<ulink url="http://www.metalab.unc.edu/pub/Linux/system/network/"/>
|
||||
</para>
|
||||
|
||||
9.2. SNMP
|
||||
|
|
@ -2550,9 +2561,10 @@ infrastructure to have proper mechanisms to guarantee network
|
|||
availability nearly 100% of the time. Some related techniques are
|
||||
described in the following sections. Most of the following material
|
||||
can be found at the excellent Linas website:
|
||||
http://linas.org/linux/index.html and in the Linux High-Availability
|
||||
HOWTO <http://metalab.unc.edu/pub/Linux/ALPHA/linux-ha/High-
|
||||
Availability-HOWTO.html>
|
||||
http://linas.org/linux/index.html and in the
|
||||
<ulink url="http://metalab.unc.edu/pub/Linux/ALPHA/linux-ha/High-Availability-HOWTO.html">Linux High-Availability
|
||||
HOWTO</ulink>
|
||||
|
||||
</para>
|
||||
|
||||
10.1. High Availability
|
||||
|
|
@ -2568,7 +2580,7 @@ steps to restore normal operation and to notifying system
|
|||
administrators.
|
||||
</para>
|
||||
|
||||
</sect1 id="Networking-Management">
|
||||
</sect1>
|
||||
|
||||
<sect1 id="Redundant-Networking">
|
||||
|
||||
|
|
@ -2588,4 +2600,4 @@ http://metalab.unc.edu/pub/Linux/ALPHA/linux-ha/High-Availability-
|
|||
HOWTO.html
|
||||
</para>
|
||||
|
||||
</sect1 id="Redundant-Networking">
|
||||
</sect1>
|
||||
|
|
|
|||
Loading…
Reference in New Issue