diff --git a/Manuals/Tcpi-ug/Configurations/Ppp/modem.docbook b/Manuals/Tcpi-ug/Configurations/Ppp/modem.docbook
index dd748a4..74c83c8 100644
--- a/Manuals/Tcpi-ug/Configurations/Ppp/modem.docbook
+++ b/Manuals/Tcpi-ug/Configurations/Ppp/modem.docbook
@@ -64,44 +64,34 @@ Bus 004 Device 001: ID 0000:0000
Configuration
- The modem configuration depends on whether you are setting the
- server computer or the client computer. Nevertheless, the
- configuration stuff related to modem detection is both valid
- on server acn client computers.
-
-
-
- Detecting The 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. To perform this very specific configuration step, run
- the following command:
+ 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
+
+
+
+ <command>wvdialconf</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:
sudo /usr/bin/wvdialconf /etc/wvdial.conf
- The wvdialconf command comes with the
- wvdial
-
- wvdial is an intelligent PPP dialer
- that takes care of dialing a modem and starting PPP to
- connect almost any ISP without special configurations. It
- is something like the chat
- program, except that it uses heuristics to guess how to
- dial and log into your server rather than forcing you to
- write a login script.
- package and detects your modem, its maximum
- baud rate, and a good initialization string. Later, using this
- information, it generates or updates the
- wvdial configuration file
- (/etc/wvdial.conf). The output produced
- by wvdialconf command looks as the
- following:
+ This command will produce an output like the following:
@@ -137,8 +127,8 @@ ttyACM0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS
- which produces the following wvdial
- configuration file:
+ and a wvdial configuration file like the
+ following:
@@ -156,72 +146,151 @@ Modem Type = USB Modem
At this point, the computer should be ready to attend incoming
- calls. When an incoming call is detected by the computer, the
- pppd deamon responds to it. To
- configure 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-up the
- pppd deamon to fit your needs. On
- the other hand, if you are configuring a computer to act as
- client, 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 in (e.g., by uncommenting the
+ 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) and then, instruct to pppd
- deamon about the user credential (e.g., user name and
- password) you will use to connect the target ISP. In this
- case, credentials defined both in
- wvdial and
- pppd applications must be exactly
- the same.
+ there).
+
+
+
+ Once you've specified the ISP information, run the following
+ command to stablish connection:
-
-
-
- The Server Settings
+ 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.
+
-
- The Client Settings
+
+ <command>system-config-network</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.
+
+
+
+
+ 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
+
+
+
+
-
- Verification
- ...
+ Inside the /etc/wvdial.conf configuration
+ file, the interface provided by
+ system-config-network identifies default
+ modem configurations through the line [Modem0],
+ while the wvdialconf command does the same
+ through the line [Dialer Defauls]. Something
+ interesting about the configuration file created by
+ system-config-network is that it is
+ possible to create several ISP configurations that reuse
+ default settings in the [Modem0] section. For
+ example, consider the following example:
---> WvDial: Internet dialer version 1.54.0
---> Cannot get information for serial port.
---> Initializing modem.
---> Sending: ATZ
-ATZ
-OK
---> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
-ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
-OK
---> Modem initialized.
---> Sending: ATDT520347
---> Waiting for carrier.
-ATDT520347
-NO DIALTONE
---> No dial tone.
---> Disconnecting at Thu Sep 29 13:04:30 2011
+[Modem0]
+Modem = /dev/ttyACM0
+Baud = 460800
+SetVolume = 2
+Dial Command = ATDT
+Init1 = ATZ
+Init3 = ATM1L2
+FlowControl = CRTSCTS
+[Dialer Vispa_Internet]
+Username = signup
+Password = rebel
+Phone = 08453080125
+Stupid Mode = 1
+Init1 = ATZ
+Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
+Inherits = Modem0
+
+
+