diff --git a/Manuals/Howto-dialup/Client.docbook b/Manuals/Howto-dialup/Client.docbook new file mode 100644 index 0000000..6a43d5a --- /dev/null +++ b/Manuals/Howto-dialup/Client.docbook @@ -0,0 +1,9 @@ + + + The Client Computer + + &client-usage; + &client-install; + &client-config; + + diff --git a/Manuals/Howto-dialup/Client.ent b/Manuals/Howto-dialup/Client.ent new file mode 100644 index 0000000..c89c2b8 --- /dev/null +++ b/Manuals/Howto-dialup/Client.ent @@ -0,0 +1,10 @@ + + + + + + + + + + diff --git a/Manuals/Howto-dialup/Client/Config.docbook b/Manuals/Howto-dialup/Client/Config.docbook new file mode 100644 index 0000000..6396561 --- /dev/null +++ b/Manuals/Howto-dialup/Client/Config.docbook @@ -0,0 +1,9 @@ + + + Dial-Up Client Configuration + + &client-config-overview; + &client-config-hardware; + &client-config-software; + + diff --git a/Manuals/Howto-dialup/Client/Config/hardware.docbook b/Manuals/Howto-dialup/Client/Config/hardware.docbook new file mode 100644 index 0000000..7fdf79c --- /dev/null +++ b/Manuals/Howto-dialup/Client/Config/hardware.docbook @@ -0,0 +1,9 @@ + + + Configuring Client Hardware + + + ... + + + diff --git a/Manuals/Howto-dialup/Client/Config/overview.docbook b/Manuals/Howto-dialup/Client/Config/overview.docbook new file mode 100644 index 0000000..371a1d9 --- /dev/null +++ b/Manuals/Howto-dialup/Client/Config/overview.docbook @@ -0,0 +1,9 @@ + + + Overview + + + ... + + + diff --git a/Manuals/Howto-dialup/Client/Config/software.docbook b/Manuals/Howto-dialup/Client/Config/software.docbook new file mode 100644 index 0000000..f374689 --- /dev/null +++ b/Manuals/Howto-dialup/Client/Config/software.docbook @@ -0,0 +1,9 @@ + + + Configuring Client Software + + + ... + + + diff --git a/Manuals/Howto-dialup/Client/Install.docbook b/Manuals/Howto-dialup/Client/Install.docbook new file mode 100644 index 0000000..6753e7d --- /dev/null +++ b/Manuals/Howto-dialup/Client/Install.docbook @@ -0,0 +1,9 @@ + + + Dial-Up Client Installation + + &client-install-overview; + &client-install-hardware; + &client-install-software; + + diff --git a/Manuals/Howto-dialup/Client/Install/hardware.docbook b/Manuals/Howto-dialup/Client/Install/hardware.docbook new file mode 100644 index 0000000..53a4f84 --- /dev/null +++ b/Manuals/Howto-dialup/Client/Install/hardware.docbook @@ -0,0 +1,9 @@ + + + Installing Client Hardware + + + ... + + + diff --git a/Manuals/Howto-dialup/Client/Install/overview.docbook b/Manuals/Howto-dialup/Client/Install/overview.docbook new file mode 100644 index 0000000..b62e798 --- /dev/null +++ b/Manuals/Howto-dialup/Client/Install/overview.docbook @@ -0,0 +1,9 @@ + + + Overview + + + ... + + + diff --git a/Manuals/Howto-dialup/Client/Install/software.docbook b/Manuals/Howto-dialup/Client/Install/software.docbook new file mode 100644 index 0000000..e057cdf --- /dev/null +++ b/Manuals/Howto-dialup/Client/Install/software.docbook @@ -0,0 +1,9 @@ + + + Installing Client Software + + + ... + + + diff --git a/Manuals/Howto-dialup/Client/Usage.docbook b/Manuals/Howto-dialup/Client/Usage.docbook new file mode 100644 index 0000000..281aca0 --- /dev/null +++ b/Manuals/Howto-dialup/Client/Usage.docbook @@ -0,0 +1,9 @@ + + + Dial-Up Client Usage + + + ... + + + diff --git a/Manuals/Howto-dialup/Configurations/Dialup/client.docbook b/Manuals/Howto-dialup/Configurations/Dialup/client.docbook index 894c293..26adb42 100644 --- a/Manuals/Howto-dialup/Configurations/Dialup/client.docbook +++ b/Manuals/Howto-dialup/Configurations/Dialup/client.docbook @@ -16,7 +16,7 @@ ... - + Establishing Dial-Up Connection diff --git a/Manuals/Howto-dialup/Configurations/Dialup/usage.docbook b/Manuals/Howto-dialup/Configurations/Dialup/usage.docbook index 62be0b9..f6bc809 100644 --- a/Manuals/Howto-dialup/Configurations/Dialup/usage.docbook +++ b/Manuals/Howto-dialup/Configurations/Dialup/usage.docbook @@ -2,289 +2,5 @@ Usage Convenctions - - The infrastructure described in this chapter uses the - client/server model to provide a public mail service through - the telephone line. In this configuration, we (the poeple - building the infrastructure) provide the information you (the - person using the infrastructure) need to know in order to - establish a point-to-point connection from the client computer - to the server computer through the telephone line. - - - The infrastructure described in this chapter is made available - to you free of charge, however, you should know that - maintaining it costs both money and time. For example, for - each hour the server computer is on production there is an - electrical consume that need to be paid every month. - Likewise, each call that you establish from the client - computer to the server computer will cost you money, based on - the location you made the call from and the time you spend - connected. - - - - In this section we discuss usage convenctions we all must be - agree with, in order to achieve a practical and secure - interchange system. - - - - Administering Dial-Up Connections - - - The lifetime of dial-up connections must be limitted based on - the number of users you expect to establish connection and the - kind of services you plan to provide. The mail service - provided by the server computer is conceived as a public - service so anyone with a modem attached to a computer would be - able to have access to it. However, due to hardware - limitations, only 100 users will be allowed to be registered - in the public mail service. Based on this information, the - lifetime of established connections will be of 15 minutes from - the established moment on. Once the connection has been - established, if the link is idle for 1 minute, the server - computer will close the established connection to free the - telephone line. This control can be implemented through the - and options - inside the pppd's configuration - file. - - - - Only registered user profiles will be able to establish connections - to the server computer. This control can be implemented using - the option in the - pppd's configuration file to define a - list of all telephone numbers that are allowed to establish - connection with the server computer, based on the list of - registered user profiles. By default, all telephone numbers - are denied from establishing access with the server computer, - except those ones explicitly set by - option. If the - option is not present in - pppd's configuration file, all - telephone numbers are allowed to establish connection with the - server computer, so be sure to include the - option in - pppd's configuration file if you - want to control who can/cannot establish connection with the - server computer. - - - -##### centos-pppd-config will overwrite this part!!! (begin) ##### -allow-number 12345 -allow-number 21345 -allow-number 34567 -##### centos-pppd-config will overwrite this part!!! (end) ##### - - - - The centos-pppd-admin application - must be considered part of user profile registration process - inside the server computer. The - centos-pppd-admin application would - be used to control the list of allowed telephone numbers - inside the pppd's configuration - file, based on the list of user profiles. The - centos-pppd-admin application - should be executed after any registration/deletion action - against the list of user profiles with root privilages in order to be - able of writing the settings on - pppd's configuration file. - - - - Redialing consecutive connections from the same telephone - number without any dealy between call retries must be avoided - from client computers. This would reduce the possibilities for - other client computers to establish connection with the server - computer. To prevent this issue from happening, it would be - necessary to provide more telephone lines than users - authorized to establish connection with the server computer. - Nevertheless, there is only one telephone line available for - the server computer to use. - - - - - - Administering User Profiles - - - In order for you to use any service provided by the server - computer it is required that you register yourself inside the - server computer creating a user profile. The user profile - provides the user information required by services inside the - server computer (e.g., username, password, e-mail address, - telephone number, etc.). To register new user profiles, you - need to use the web application provided by the server - computer. For example, assuming the domain name of the server - computer is example.com, the web - application would be accessable through the following URL: - . - - - - To reach the web interface, the first thing you need to do is - establishing a dial-up connection to the server computer as - described in . Once the - dial-up connection has been established, you need to open a - web browser (e.g., Firefox) and put the URL mentioned above in - the address space, and press Enter to go. This will present - you a web page with the instructions you need to follow in - order to register your user profile. Other actions like - updating or deleting your own user profile should be also - possible from this web interface. - - - - - The web interface used to manage user profiles inside the - server computer must be presented over an encrypted session in - order to protect all the information passing through. - - - - - Inside the server computer, all related subsystems in need of - user information (e.g., Postix, Cyrus-Imapd and Saslauthd) - retrive user information from one single (LDAP) source. The - web application provided by the server computer manages all - these subsystems' configuration files in order to provide a - pleasant experience for end users. The web interface must be - as simple as possible in order to achieve all administration - tasks in the range of time permitted by the server computer - before it closes the connection established from the client - computer. - - - - More information about the web interface you need to use to - manage your user profile inside the server computer can be - found in . - - - - - - Administering Services - - - The information generated inside the server computer is - isolated from Internet. This way, any information generated - inside the server computer will be available only to people - registered inside the server computer. For example, don't ever - expect to send/receive e-mails to/from Internet e-mail - accounts like Gmail or Yahoo, nor visiting web sites like - Google or Wikipedia either. For - this to happen, it is required an established connection - between the server computer you are establishing connection - through and the Internet network those services are available - in. Without that link, it is not possible to direct your - requests to those sites. - - - - The implementation of services that required persistent - connections (e.g., chats) will not - be considered as a practical offer inside the server computer. - Instead, only asynchronous services (e.g., - e-mail) will be supported. This - restriction is required to reduce the amount of time demanded - by services. For example, consider an environment where you - connect to the server computer for sending/receiving e-mails - messages and then quickly disconnect from it to free the - telephone line for others to use. In this environment, there - is no need for you and other person to be both connected at - the same time to send/receive e-mail messages to/from each - other. The e-mails sent from other person to you will be - available in your mailbox the next time you get connected to - the server computer and use your e-mail client to send/receive - e-mail messages. Likewise, you don't need to be connected to - the server computer in order to write your e-mail messages. - You can write down your messages off-line and then establish - connection once you've finished writing, just to send them - out and receive new messages that could have been probably - sent to you. - - - - Another issue related to e-mail exchange is the protocol used - to receive messages. Presently, there are two popular ways to - do this, one is through IMAP and another through POP3. When - you use IMAP protocol, e-mail messages are retained in the - server computer and aren't downloaded to client computer. - Otherwise, when you use POP3 protocol, e-mail messages are - downloaded to the client computer and removed from server - computer. Based on the resources we have and the kind of link - used by the client computer to connect the server computer, - using POP3 is rather prefered than IMAP. However both are made - available. - - - - Assuming you use IMAP protocol to read your mailbox, be aware - that you need to be connected to the server computer. Once - the connection is lost you won't be able to read your messages - (unless your e-mail client possesses a feature that let you - reading messages off-line). Morover, you run the risk of - getting your mailbox out of space. If your mailbox gets out of - space, new messages sent to you will not be deliver to your - mailbox. Instead, they will be deferred for a period of time - (e.g., about 5 days when using - Postfix defaults) hoping you to - free the space in your mailbox to deliver them. If you don't - free space within this period of time, the deferred e-mails - will be bounced back to their senders and you will never see - them. On the other hand, assuming you are using POP3 protocol - to read your mailbox, you always keep your mailbox free to - receive new e-mails messages and keep them for you until the - next time you establish connection with the server computer - and download them to your client computer using your e-mail - client. - - - - - Administering Disk Space - - - The maximum number of registered user profiles is limited - inside the server computer, based on the maximum disk space - the server computer confines to such purpose. For example, - consider an environment where users can get registered - themselves using a web interface. In this case the web - interface must know how much disk space is available before - proceeding to register new mail accounts inside the server - computer and this way preventing any disk writing when there - isn't enough free space on disk to perform a new user - registration. Considering the server computer has confined - 1GB of disk space to handle the mail service (e.g., mail - queues, mailboxes, etc.) and each user mailbox is 10MB, it - will be possible to provide self-registration through the web - interface for 100 users in total. - - - - Another measure related to save disk space might be to remove - unused user accounts and their related files (e.g., mailboxes) - from the server computer. For example, consider an environment - where user accounts are automatically removed from the server - computer when they don't establish a connection with the - server computer in a period greater than 7 days since the last - valid connection established to the server computer. Once the - user account is removed, it is no longer functional of course, - and the person whom lost the account will need to create a new - one, assuming it want to have access to the mail service - again. - - - diff --git a/Manuals/Howto-dialup/Preface.docbook b/Manuals/Howto-dialup/Preface.docbook index 7eca40b..42c8578 100755 --- a/Manuals/Howto-dialup/Preface.docbook +++ b/Manuals/Howto-dialup/Preface.docbook @@ -2,39 +2,8 @@ Preface - - Welcome to &TCPIUG;, the official documentation of &TCPI;. - - - - This book describes how &TCPI; is organized and the guidelines - both users and administrators should follow to make use of it. - If you need to know what the technical and political desitions - behind &TCP; are, this book is definitly for you. - - - - To make the information in this book managable, it has been - organized in the following parts: - - - - - - organizes the licenses mentioned - in this book. - - - - - - This book is oriented to system administrators and assumes you - have a basic understanding of &TCD;. If you need help with - it, go to the Help page inside - &TCWIKI; for or a list of different places you can find help. - - &preface-overview; + &preface-docconvs; + &preface-feedback; diff --git a/Manuals/Howto-dialup/Preface.ent b/Manuals/Howto-dialup/Preface.ent index 41f09f0..263be1d 100755 --- a/Manuals/Howto-dialup/Preface.ent +++ b/Manuals/Howto-dialup/Preface.ent @@ -1,2 +1,4 @@ + + diff --git a/Manuals/Howto-dialup/Preface/docconvs.docbook b/Manuals/Howto-dialup/Preface/docconvs.docbook new file mode 100644 index 0000000..8eda7bc --- /dev/null +++ b/Manuals/Howto-dialup/Preface/docconvs.docbook @@ -0,0 +1,225 @@ +
+ + Document Convenctions + + + In this manual, certain words are represented in different + fonts, typefaces, sizes, and weights. This highlighting is + systematic; different words are represented in the same style + to indicate their inclusion in a specific category. The types + of words that are represented this way include the + following: + + + + + command + + + Linux commands (and other operating system commands, when + used) are represented this way. This style should + indicate to you that you can type the word or phrase on + the command line and press Enter to + invoke a command. Sometimes a command contains words that + would be displayed in a different style on their own (such + as file names). In these cases, they are considered to be + part of the command, so the entire phrase is displayed as + a command. For example: + + + + Use the centos-art render + trunk/Identity/Images/Themes/TreeFlower/4/Distro/5/Anaconda + --filter="01-welcome" command to produce the first + slide image used by Anaconda in the branch 5 of &TCD; + using the version 4 of TreeFlower artistic motif. + + + + + + file name + + + File names, directory names, paths, and RPM package names + are represented this way. This style indicates that a + particular file or directory exists with that name on your + system. Examples: + + + + The init.sh file in trunk/Scripts/Bash/Cli/ + directory is the initialization script, written in Bash, + used to automate most of tasks in the repository. + + + + The centos-art command uses the + ImageMagick RPM package to convert + images from PNG format to other formats. + + + + + + key + + + A key on the keyboard is shown in this style. For + example: + + + + To use Tab completion to list particular + files in a directory, type ls, then a + character, and finally the Tab key. Your + terminal displays the list of files in the working + directory that begin with that character. + + + + + + keycombination + + + A combination of keystrokes is represented in this way. + For example: + + + + The CtrlAltBackspace + key combination exits your graphical session and returns + you to the graphical login screen or the console. + + + + + + computer output + + + Text in this style indicates text displayed to a shell + prompt such as error messages and responses to commands. + For example, the ls command displays + the contents of a directory using this style: + + + +render_doTranslation.sh render_getDirTemplate.sh render_doBaseActions.sh +render_getConfigOption.sh render_getOptions.sh render_doThemeActions.sh +render_getDirOutput.sh render.sh + + + + The output returned in response to the command (in this + case, the contents of the directory) is shown in this + style. + + + + + + prompt + + + A prompt, which is a computer's way of signifying that it + is ready for you to input something, is shown in this + style. Examples: + + + + + + $ + + + + + # + + + + + [centos@projects centos]$ + + + + + projects login: + + + + + + + + user input + + + Text that the user types, either on the command line or + into a text box on a GUI screen, is displayed in this + style. In the following example, + text is displayed in this style: To + boot your system into the text based installation program, + you must type in the text command + at the boot: prompt. + + + + + + replaceable + + + Text used in examples that is meant to be replaced with + data provided by the user is displayed in this style. In + the following example, + version-number is displayed in + this style: The directory for the kernel source is + /usr/src/kernels/version-number/, + where version-number is the + version and type of kernel installed on this system. + + + + + + Additionally, we use several different strategies to draw + your attention to certain pieces of information. In order of + urgency, these items are marked as a note, tip, important, + caution, or warning. For example: + + + Remember that Linux is case sensitive. In other words, a + rose is not a ROSE is not a rOsE. + + + + The directory /usr/share/doc/ contains + additional documentation for packages installed on your + system. + + + + If you modify the DHCP configuration file, the changes + do not take effect until you restart the DHCP daemon. + + + + Do not perform routine tasks as root — use a + regular user account unless you need to use the root account + for system administration tasks. + + + + Be careful to remove only the necessary partitions. + Removing other partitions could result in data loss or a + corrupted system environment. + + +
diff --git a/Manuals/Howto-dialup/Preface/feedback.docbook b/Manuals/Howto-dialup/Preface/feedback.docbook new file mode 100644 index 0000000..976502b --- /dev/null +++ b/Manuals/Howto-dialup/Preface/feedback.docbook @@ -0,0 +1,15 @@ +
+ + Send In Your Feedback + + + If you find a bug in the infrastructure described in this + manual, we would like to hear about it. To report bugs + related to this manual, send an e-mail to the + centos-docs@centos.org mailing list. When you + write the bug report, take care of being specific about the + problem you are reporting on (e.g., where it is, the section + number, etc.) so we can found it easily. + + +
diff --git a/Manuals/Howto-dialup/Preface/overview.docbook b/Manuals/Howto-dialup/Preface/overview.docbook index 1ef0ded..962fa81 100755 --- a/Manuals/Howto-dialup/Preface/overview.docbook +++ b/Manuals/Howto-dialup/Preface/overview.docbook @@ -3,7 +3,22 @@ Overview - ... + This manual describes two computers configuration, one acting + as server and other as client. The server computer will be + configured to provide internet services and the client to make + use of those internet services provided by the server + computer. The connection medium both client and server + computer use is the telelphone line (i.e., the same medium you + use to realize phone calls). In this configuration, both + client and server computers use special devices named + Modems to transmit data in form of sound across + the telephone line. + + + + The configuration described in this chapter could be a good + choise when the only communication medium you have access to + is a telephone network. diff --git a/Manuals/Howto-dialup/Server.docbook b/Manuals/Howto-dialup/Server.docbook new file mode 100644 index 0000000..f934db3 --- /dev/null +++ b/Manuals/Howto-dialup/Server.docbook @@ -0,0 +1,9 @@ + + + The Server Computer + + &server-usage; + &server-install; + &server-config; + + diff --git a/Manuals/Howto-dialup/Server.ent b/Manuals/Howto-dialup/Server.ent new file mode 100644 index 0000000..531a560 --- /dev/null +++ b/Manuals/Howto-dialup/Server.ent @@ -0,0 +1,15 @@ + + + + + + + + + + + + + + + diff --git a/Manuals/Howto-dialup/Server/Config.docbook b/Manuals/Howto-dialup/Server/Config.docbook new file mode 100644 index 0000000..40c442b --- /dev/null +++ b/Manuals/Howto-dialup/Server/Config.docbook @@ -0,0 +1,9 @@ + + + Dial-Up Server Configuration + + &server-config-overview; + &server-config-hardware; + &server-config-software; + + diff --git a/Manuals/Howto-dialup/Server/Config/hardware.docbook b/Manuals/Howto-dialup/Server/Config/hardware.docbook new file mode 100644 index 0000000..4660bc4 --- /dev/null +++ b/Manuals/Howto-dialup/Server/Config/hardware.docbook @@ -0,0 +1,9 @@ + + + Configuring Server Hardware + + + ... + + + diff --git a/Manuals/Howto-dialup/Server/Config/overview.docbook b/Manuals/Howto-dialup/Server/Config/overview.docbook new file mode 100644 index 0000000..bcfcc4a --- /dev/null +++ b/Manuals/Howto-dialup/Server/Config/overview.docbook @@ -0,0 +1,9 @@ + + + Overview + + + ... + + + diff --git a/Manuals/Howto-dialup/Server/Config/software.docbook b/Manuals/Howto-dialup/Server/Config/software.docbook new file mode 100644 index 0000000..e6f9bcd --- /dev/null +++ b/Manuals/Howto-dialup/Server/Config/software.docbook @@ -0,0 +1,9 @@ + + + Configuring Server Software + + + ... + + + diff --git a/Manuals/Howto-dialup/Server/Install.docbook b/Manuals/Howto-dialup/Server/Install.docbook new file mode 100644 index 0000000..fcc98c2 --- /dev/null +++ b/Manuals/Howto-dialup/Server/Install.docbook @@ -0,0 +1,9 @@ + + + Dial-Up Server Installation + + &server-install-overview; + &server-install-hardware; + &server-install-software; + + diff --git a/Manuals/Howto-dialup/Server/Install/hardware.docbook b/Manuals/Howto-dialup/Server/Install/hardware.docbook new file mode 100644 index 0000000..72b37bb --- /dev/null +++ b/Manuals/Howto-dialup/Server/Install/hardware.docbook @@ -0,0 +1,61 @@ + + + Installing Server Hardware + + + In order to establish a PPP link between two computers using + the telephone line as medium for data transmission, you need + to install (at least) one modem device in each computer. + + + + To install a modem device in computer you need to attach the + modem hardware to the computer and later the telephone line to + the modem hardware. To connect the modem to your computer, you + need to connect the serial or USB cable that comes from the + modem hardware to the appropriate input on your computer. To + connect the modem to the telephone line system, you need to + unplug the cable that connects your telephone device and plug + it on the modem device, specifically in the port reserved for + data transmission. Later, using a similar cable, you could + connect your telephone device to the modem's telephone port, + so you can realize telephone calls when no data transmition + take place. + + + + To be on the safe side, do all the installation with the + computer turned off. Then, when everthing has been put in + place, turn it on. Once the system is up, you can verify the + modem hardware using either the lsusb or + lspci commands. These commands need to be + run with administrative privileges, so probably need to + sudo them or login as root user in order to execute + thme. For example, assuming you are logged in as root user, + and you are using an USB modem like that one we mentioned + before, the output of lsusb command would + look like the following: + + + +Bus 003 Device 001: ID 0000:0000 +Bus 001 Device 001: ID 0000:0000 +Bus 001 Device 002: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader +Bus 002 Device 001: ID 0000:0000 +Bus 005 Device 003: ID 06e0:f104 Multi-Tech Systems, Inc. +MT5634ZBA-USB MultiModemUSB (new firmware) +Bus 005 Device 001: ID 0000:0000 +Bus 005 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse +Bus 004 Device 001: ID 0000:0000 + + + + The relevant line here is that mentioning the existence of a + Multi-Tech System, Inc. MT5634ZBA-USB MultiModemUSB (new + firmware) device. If the modem you installed doesn't + appear in this list, it is probably because such hardware is + not supported by &TCD;, yet. + + + diff --git a/Manuals/Howto-dialup/Server/Install/overview.docbook b/Manuals/Howto-dialup/Server/Install/overview.docbook new file mode 100644 index 0000000..f7e99b1 --- /dev/null +++ b/Manuals/Howto-dialup/Server/Install/overview.docbook @@ -0,0 +1,9 @@ + + + Overview + + + ... + + + diff --git a/Manuals/Howto-dialup/Server/Install/software.docbook b/Manuals/Howto-dialup/Server/Install/software.docbook new file mode 100644 index 0000000..72baf64 --- /dev/null +++ b/Manuals/Howto-dialup/Server/Install/software.docbook @@ -0,0 +1,9 @@ + + + Installing Server Software + + + ... + + + diff --git a/Manuals/Howto-dialup/Server/Usage.docbook b/Manuals/Howto-dialup/Server/Usage.docbook new file mode 100644 index 0000000..b121a6a --- /dev/null +++ b/Manuals/Howto-dialup/Server/Usage.docbook @@ -0,0 +1,11 @@ + + + Dial-Up Server Usage + + &server-usage-overview; + &server-usage-connections; + &server-usage-users; + &server-usage-services; + &server-usage-diskspace; + + diff --git a/Manuals/Howto-dialup/Server/Usage/connections.docbook b/Manuals/Howto-dialup/Server/Usage/connections.docbook new file mode 100644 index 0000000..dea10e3 --- /dev/null +++ b/Manuals/Howto-dialup/Server/Usage/connections.docbook @@ -0,0 +1,81 @@ + + + Administering Dial-Up Connections + + + The lifetime of dial-up connections must be limitted based on + the number of users you expect to establish connection and the + kind of services you plan to provide. The mail service + provided by the server computer is conceived as a public + service so anyone with a modem attached to a computer would be + able to have access to it. However, due to hardware + limitations, only 100 users will be allowed to be registered + in the public mail service. Based on this information, the + lifetime of established connections will be of 15 minutes from + the established moment on. Once the connection has been + established, if the link is idle for 1 minute, the server + computer will close the established connection to free the + telephone line. This control can be implemented through the + and options + inside the pppd's configuration + file. + + + + Only registered user profiles will be able to establish connections + to the server computer. This control can be implemented using + the option in the + pppd's configuration file to define a + list of all telephone numbers that are allowed to establish + connection with the server computer, based on the list of + registered user profiles. By default, all telephone numbers + are denied from establishing access with the server computer, + except those ones explicitly set by + option. If the + option is not present in + pppd's configuration file, all + telephone numbers are allowed to establish connection with the + server computer, so be sure to include the + option in + pppd's configuration file if you + want to control who can/cannot establish connection with the + server computer. + + + +##### centos-pppd-config will overwrite this part!!! (begin) ##### +allow-number 12345 +allow-number 21345 +allow-number 34567 +##### centos-pppd-config will overwrite this part!!! (end) ##### + + + + The centos-pppd-admin application + must be considered part of user profile registration process + inside the server computer. The + centos-pppd-admin application would + be used to control the list of allowed telephone numbers + inside the pppd's configuration + file, based on the list of user profiles. The + centos-pppd-admin application + should be executed after any registration/deletion action + against the list of user profiles with root privilages in order to be + able of writing the settings on + pppd's configuration file. + + + + Redialing consecutive connections from the same telephone + number without any dealy between call retries must be avoided + from client computers. This would reduce the possibilities for + other client computers to establish connection with the server + computer. To prevent this issue from happening, it would be + necessary to provide more telephone lines than users + authorized to establish connection with the server computer. + Nevertheless, there is only one telephone line available for + the server computer to use. + + + diff --git a/Manuals/Howto-dialup/Server/Usage/diskspace.docbook b/Manuals/Howto-dialup/Server/Usage/diskspace.docbook new file mode 100644 index 0000000..950fc51 --- /dev/null +++ b/Manuals/Howto-dialup/Server/Usage/diskspace.docbook @@ -0,0 +1,36 @@ + + + Administering Disk Space + + + The maximum number of registered user profiles is limited + inside the server computer, based on the maximum disk space + the server computer confines to such purpose. For example, + consider an environment where users can get registered + themselves using a web interface. In this case the web + interface must know how much disk space is available before + proceeding to register new mail accounts inside the server + computer and this way preventing any disk writing when there + isn't enough free space on disk to perform a new user + registration. Considering the server computer has confined + 1GB of disk space to handle the mail service (e.g., mail + queues, mailboxes, etc.) and each user mailbox is 10MB, it + will be possible to provide self-registration through the web + interface for 100 users in total. + + + + Another measure related to save disk space might be to remove + unused user accounts and their related files (e.g., mailboxes) + from the server computer. For example, consider an environment + where user accounts are automatically removed from the server + computer when they don't establish a connection with the + server computer in a period greater than 7 days since the last + valid connection established to the server computer. Once the + user account is removed, it is no longer functional of course, + and the person whom lost the account will need to create a new + one, assuming it want to have access to the mail service + again. + + + diff --git a/Manuals/Howto-dialup/Server/Usage/overview.docbook b/Manuals/Howto-dialup/Server/Usage/overview.docbook new file mode 100644 index 0000000..0287ab1 --- /dev/null +++ b/Manuals/Howto-dialup/Server/Usage/overview.docbook @@ -0,0 +1,33 @@ + + + Overview + + + The infrastructure described in this chapter uses the + client/server model to provide a public mail service through + the telephone line. In this configuration, we (the poeple + building the infrastructure) provide the information you (the + person using the infrastructure) need to know in order to + establish a point-to-point connection from the client computer + to the server computer through the telephone line. + + + + The infrastructure described in this chapter is made available + to you free of charge, however, you should know that + maintaining it costs both money and time. For example, for + each hour the server computer is on production there is an + electrical consume that need to be paid every month. + Likewise, each call that you establish from the client + computer to the server computer will cost you money, based on + the location you made the call from and the time you spend + connected. + + + + In this chapter we discuss usage convenctions we all must be + agree with, in order to achieve a practical and secure + interchange system. + + + diff --git a/Manuals/Howto-dialup/Server/Usage/services.docbook b/Manuals/Howto-dialup/Server/Usage/services.docbook new file mode 100644 index 0000000..2f89a6c --- /dev/null +++ b/Manuals/Howto-dialup/Server/Usage/services.docbook @@ -0,0 +1,81 @@ + + + Administering Internet Services + + + The information generated inside the server computer is + isolated from Internet. This way, any information generated + inside the server computer will be available only to people + registered inside the server computer. For example, don't ever + expect to send/receive e-mails to/from Internet e-mail + accounts like Gmail or Yahoo, nor visiting web sites like + Google or Wikipedia either. For + this to happen, it is required an established connection + between the server computer you are establishing connection + through and the Internet network those services are available + in. Without that link, it is not possible to direct your + requests to those sites. + + + + The implementation of services that required persistent + connections (e.g., chats) will not + be considered as a practical offer inside the server computer. + Instead, only asynchronous services (e.g., + e-mail) will be supported. This + restriction is required to reduce the amount of time demanded + by services. For example, consider an environment where you + connect to the server computer for sending/receiving e-mails + messages and then quickly disconnect from it to free the + telephone line for others to use. In this environment, there + is no need for you and other person to be both connected at + the same time to send/receive e-mail messages to/from each + other. The e-mails sent from other person to you will be + available in your mailbox the next time you get connected to + the server computer and use your e-mail client to send/receive + e-mail messages. Likewise, you don't need to be connected to + the server computer in order to write your e-mail messages. + You can write down your messages off-line and then establish + connection once you've finished writing, just to send them + out and receive new messages that could have been probably + sent to you. + + + + Another issue related to e-mail exchange is the protocol used + to receive messages. Presently, there are two popular ways to + do this, one is through IMAP and another through POP3. When + you use IMAP protocol, e-mail messages are retained in the + server computer and aren't downloaded to client computer. + Otherwise, when you use POP3 protocol, e-mail messages are + downloaded to the client computer and removed from server + computer. Based on the resources we have and the kind of link + used by the client computer to connect the server computer, + using POP3 is rather prefered than IMAP. However both are made + available. + + + + Assuming you use IMAP protocol to read your mailbox, be aware + that you need to be connected to the server computer. Once + the connection is lost you won't be able to read your messages + (unless your e-mail client possesses a feature that let you + reading messages off-line). Morover, you run the risk of + getting your mailbox out of space. If your mailbox gets out of + space, new messages sent to you will not be deliver to your + mailbox. Instead, they will be deferred for a period of time + (e.g., about 5 days when using + Postfix defaults) hoping you to + free the space in your mailbox to deliver them. If you don't + free space within this period of time, the deferred e-mails + will be bounced back to their senders and you will never see + them. On the other hand, assuming you are using POP3 protocol + to read your mailbox, you always keep your mailbox free to + receive new e-mails messages and keep them for you until the + next time you establish connection with the server computer + and download them to your client computer using your e-mail + client. + + + diff --git a/Manuals/Howto-dialup/Server/Usage/users.docbook b/Manuals/Howto-dialup/Server/Usage/users.docbook new file mode 100644 index 0000000..2cdf646 --- /dev/null +++ b/Manuals/Howto-dialup/Server/Usage/users.docbook @@ -0,0 +1,61 @@ + + + Administering Users Accounts + + + In order for you to use any service provided by the server + computer it is required that you register yourself inside the + server computer creating a user profile. The user profile + provides the user information required by services inside the + server computer (e.g., username, password, e-mail address, + telephone number, etc.). To register new user profiles, you + need to use the web application provided by the server + computer. For example, assuming the domain name of the server + computer is example.com, the web + application would be accessable through the following URL: + . + + + + To reach the web interface, the first thing you need to do is + establishing a dial-up connection to the server computer as + described in . Once the + dial-up connection has been established, you need to open a + web browser (e.g., Firefox) and put the URL mentioned above in + the address space, and press Enter to go. This will present + you a web page with the instructions you need to follow in + order to register your user profile. Other actions like + updating or deleting your own user profile should be also + possible from this web interface. + + + + + The web interface used to manage user profiles inside the + server computer must be presented over an encrypted session in + order to protect all the information passing through. + + + + + Inside the server computer, all related subsystems in need of + user information (e.g., Postix, Cyrus-Imapd and Saslauthd) + retrive user information from one single (LDAP) source. The + web application provided by the server computer manages all + these subsystems' configuration files in order to provide a + pleasant experience for end users. The web interface must be + as simple as possible in order to achieve all administration + tasks in the range of time permitted by the server computer + before it closes the connection established from the client + computer. + + + + More information about the web interface you need to use to + manage your user profile inside the server computer can be + found in .... + + + diff --git a/Manuals/Howto-dialup/howto-dialup.docbook b/Manuals/Howto-dialup/howto-dialup.docbook index f2b634b..af57010 100755 --- a/Manuals/Howto-dialup/howto-dialup.docbook +++ b/Manuals/Howto-dialup/howto-dialup.docbook @@ -5,22 +5,21 @@ - - + + %Commons.ent; %Preface.ent; -%Administration.ent; -%Configurations.ent; +%Server.ent; +%Client.ent; %Licenses.ent; ]> - The CentOS Project Infrastructure - User's Guide + Dial-Up Infrastructure @@ -71,8 +70,8 @@ &preface; - &administration; - &configurations; + &server; + &client; &licenses;