From 2690bcec1e027c80413f5d2d92eb67266a556ea7 Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: Oct 01 2011 06:19:24 +0000 Subject: Update `Configurations/Ppp/modem-config.docbook'. --- diff --git a/Manuals/Tcpi-ug/Configurations/Ppp/modem-config.docbook b/Manuals/Tcpi-ug/Configurations/Ppp/modem-config.docbook index 30ad9f7..d90737d 100644 --- a/Manuals/Tcpi-ug/Configurations/Ppp/modem-config.docbook +++ b/Manuals/Tcpi-ug/Configurations/Ppp/modem-config.docbook @@ -1,30 +1,53 @@ - Configuring The Modem Device + Configuring Modem Device Once the modem hardware has been installed in the computer, it - is necessary to determine what device inside the operating - system it was assigned to, so applications like - pppd and chat can talk - to it. This configuration process can be realized through the - wvdialconf command distributed with the - wvdial package or the - system-config-network command. Once the + is necessary to determine what device location the operating + system assigned to it, so applications like + chat be able to know which device + to talk to. This configuration process can be realized + through the wvdialconf command, distributed + with the wvdial package. + + + + Another way to configure modems installed in your computer is + through the graphical interface provided by + system-config-network command. This + interface may result specially useful when you need to + configure your computer to establish Modem connections to + remote Internet Service Providers (ISPs). The interface + provided by system-config-network command + uses the same configuration file that + wvdialconf command does (e.g., + /etc/wvdial.conf), however, there are + some differences in the way these commands create + configuration files that we need to be aware of. + + + + This section describes how you could use the + wvdialconf and + system-config-network commands to configure + the modem installed in your computer, as well as possible + issues you might face if these two commands are arbitrarily + combined one another. - <command>wvdialconf</command> + The <command>wvdialconf</command> Command - The wvdialconf automatically detects your - modem and generates/updates the wvdial - configuration file (/etc/wvdial.conf) - using the modem's maximum baud rate found in the - auto-detection process, and a good initialization string for - it, as well. To set the modem configuration through - wvdialconf command, run the following - command: + The wvdialconf automatically detects the + location the operating system assigned to your modem, its + maximum baud rate, a good initialization string for it, and + generates/updates the wvdial configuration + file (/etc/wvdial.conf) the + wvdial command needs to work. To set the + modem configuration through wvdialconf + command, run the command as follows: sudo /usr/bin/wvdialconf /etc/wvdial.conf @@ -83,125 +106,55 @@ Modem Type = USB Modem ; Password = <Your Password> - - At this point, the computer should be ready to attend incoming - calls. - - - - When an incoming call arrives to the server they are attended - by the pppd deamon. To administer - the way such incoming calls are attended (e.g., forcing user - authentication, restricting the phone numbers the calls can be - initiated from, etc.), you need to set the - pppd deamon configuration to fit - your needs. To know more about how to configure the - pppd deamon and the options it - provides, read its man page (e.g., man - pppd). - - - - On the other hand, when you are configuring a computer to act - as client (i.e., you are calling out an ISP to establish - connection to it), you need to realize a few more tunning - steps on /etc/wvdial.conf to set the - information related of that Internet Service Provider (ISP) - you want to get connected to (e.g., uncommenting the - Phone, Username and - Password lines above to set the appropiate values - there). - - - - Once you've specified the ISP information, run the following - command to stablish connection: - - - sudo /usr/bin/wvdial - - Both wvdial and - wvdialconf commands must be run with - administrative privilages because its configuration file - (/etc/wvdial.conf) is readable by the - root user only. + It is possible to configure the same computer to act both as + server (i.e., to receive incoming calls from clients) and + client (i.e., to realize outgoing calls to servers). However, + be aware that only one of these connections can be established + at a time. - <command>system-config-network</command> + The <command>system-config-network</command> Command - In addition to the configuration process described so far, you - can manage modem configurations through the - system-config-network command. This command - provides a graphical interface (administrative privileges - required) which let you configure several ISP and alternate - the one you connect to. This command has been already - documented in the Deployment Guide - availabe in the Deployment_Guide and we - won't duplicate that information here. However, there are some - differences between the output produced by - system-config-network and - wvdialconf commads you need to be aware of. - - - - The first thing to know is that both - system-config-network and - wvdialconf commands write configurations to - the /etc/wvdial.conf file, but the - interface provided by system-config-network - command doesn't detect the configuration intially created by - wvdialconf command. In fact, if you set a - new (modem) hardware configuration through the interface - provided by the system-config-network - command, any configuraion previously created by - wvdailconf will be lost. - - - - The interface provided by system-config-network command doesn't - provide modem device detection (as - wvdialconf would do) and uses the - /dev/modem as default location. This - location doesn't exists by default, so whatever configuration - you set from it will not work. To solve this, chose one of the - following workarounds: - - - - - Replace the /dev/modem location by that - one wvdialconf found when the interface - provided by system-config-network ask you - to enter the modem device. + detect the configuration intially created by + wvdialconf command. In fact, if you set a + new (modem) hardware configuration through it, any + configuration previously created by + wvdailconf command will be lost. On the + other hand, if you firstly generate the configuration file + using the interface provided by + system-config-network command and later run + the wvdialconf command over it, you will + end up having two similar configuration settings under + different definitions stored in the same configuration file. - - + + - Create /dev/modem location as a symbolic - link to that location found by wvdialconf - command. For example: - sudo /bin/ln -s /dev/ttyACM0 /dev/modem + The wvdial command doesn't understand the + configuration file produced by + system-config-network command, even both + wvdialconf and + system-config-network commands use the same + configuration syntax to create the configuration file. - - - + Inside the /etc/wvdial.conf configuration file, the interface provided by system-config-network identifies default - modem configurations through the line [Modem0], + modem configurations through the [Modem0] line, while the wvdialconf command does the same - through the line [Dialer Defauls]. Something + through the [Dialer Defaults] line. Something interesting about the configuration file created by system-config-network is that it is possible to create several ISP configurations that reuse @@ -228,6 +181,36 @@ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Inherits = Modem0 + + + The interface provided by + system-config-network command doesn't + provide modem detection (as wvdialconf + command would do) and uses the /dev/modem + as default location. This location doesn't exists by default, + so whatever configuration you set from it will not work. To + solve this issue, chose one of the following workarounds: + + + + + Replace the /dev/modem location by that + one wvdialconf found when the interface + provided by system-config-network ask you + to enter the modem device. + + + + + Create /dev/modem location as a symbolic + link to that location found by wvdialconf + command. For example: + sudo /bin/ln -s /dev/ttyACM0 /dev/modem + + + + +