193865 Update `Configurations/Ppp/modem.docbook'.

Authored and Committed by areguera 13 years ago
    Update `Configurations/Ppp/modem.docbook'.
    
        
Manuals/Tcpi-ug/Configurations/Ppp/modem.docbook CHANGED
@@ -64,44 +64,34 @@ Bus 004 Device 001: ID 0000:0000
64
64
<title>Configuration</title>
65
65
66
66
<para>
67
- The modem configuration depends on whether you are setting the
68
- server computer or the client computer. Nevertheless, the
69
- configuration stuff related to modem detection is both valid
70
- on server acn client computers.
71
- </para>
72
-
73
- <sect3 id="configurations-ppp-modem-config-detect">
74
- <title>Detecting The Modem Device</title>
75
-
76
- <para>
77
67
Once the modem hardware has been installed in the computer, it
78
68
is necessary to determine what device inside the operating
79
69
system it was assigned to, so applications like
80
70
<command>pppd</command> and <command>chat</command> can talk
81
- to it. To perform this very specific configuration step, run
82
- the following command:
71
+ to it. This configuration process can be realized through the
72
+ <command>wvdialconf</command> command distributed with the
73
+ <package>wvdial</package> package or the
74
+ <command>system-config-network</command> command. Once the
75
+ </para>
76
+
77
+ <sect3 id="configurations-ppp-modem-config-wvdial">
78
+ <title><command>wvdialconf</command></title>
79
+
80
+ <para>
81
+ The <command>wvdialconf</command> automatically detects your
82
+ modem and generates/updates the <command>wvdial</command>
83
+ configuration file (<filename>/etc/wvdial.conf</filename>)
84
+ using the modem's maximum baud rate found in the
85
+ auto-detection process, and a good initialization string for
86
+ it, as well. To set the modem configuration through
87
+ <command>wvdialconf</command> command, run the following
88
+ command:
83
89
</para>
84
90
85
91
<screen>sudo /usr/bin/wvdialconf /etc/wvdial.conf</screen>
86
92
87
93
<para>
88
- The <command>wvdialconf</command> command comes with the
94
+ This command will produce an output like the following:
89
- <package>wvdial</package><footnote>
90
- <para>
91
- <command>wvdial</command> is an intelligent PPP dialer
92
- that takes care of dialing a modem and starting PPP to
93
- connect almost any ISP without special configurations. It
94
- is something like the <application>chat</application>
95
- program, except that it uses heuristics to guess how to
96
- dial and log into your server rather than forcing you to
97
- write a login script.
98
- </para></footnote> package and detects your modem, its maximum
99
- baud rate, and a good initialization string. Later, using this
100
- information, it generates or updates the
101
- <command>wvdial</command> configuration file
102
- (<filename>/etc/wvdial.conf</filename>). The output produced
103
- by <command>wvdialconf</command> command looks as the
104
- following:
105
95
</para>
106
96
107
97
<screen>
@@ -137,8 +127,8 @@ ttyACM0&lt;Info&gt;: Speed 460800; init "ATQ0 V1 E1 S0=0 &amp;C1 &amp;D2 +FCLASS
137
127
</screen>
138
128
139
129
<para>
140
- which produces the following <command>wvdial</command>
141
- configuration file:
130
+ and a <command>wvdial</command> configuration file like the
131
+ following:
142
132
</para>
143
133
144
134
<screen>
@@ -156,72 +146,151 @@ Modem Type = USB Modem
156
146
157
147
<para>
158
148
At this point, the computer should be ready to attend incoming
159
- calls. When an incoming call is detected by the computer, the
160
- <application>pppd</application> deamon responds to it. To
161
- configure the way such incoming calls are attended (e.g.,
162
- forcing user authentication, restricting the phone numbers the
163
- calls can be initiated from, etc.), you need to set-up the
164
- <application>pppd</application> deamon to fit your needs. On
165
- the other hand, if you are configuring a computer to act as
166
- client, you need to realize a few more tunning steps on
167
- <filename>/etc/wvdial.conf</filename> to set the information
168
- related of that Internet Service Provider (ISP) you want to
169
- get connected in (e.g., by uncommenting the
149
+ calls.
150
+ </para>
151
+
152
+ <para>
153
+ When an incoming call arrives to the server they are attended
154
+ by the <application>pppd</application> deamon. To administer
155
+ the way such incoming calls are attended (e.g., forcing user
156
+ authentication, restricting the phone numbers the calls can be
157
+ initiated from, etc.), you need to set the
158
+ <application>pppd</application> deamon configuration to fit
159
+ your needs. To know more about how to configure the
160
+ <application>pppd</application> deamon and the options it
161
+ provides, read its man page (e.g., <command>man
162
+ pppd</command>).
163
+ </para>
164
+
165
+ <para>
166
+ On the other hand, when you are configuring a computer to act
167
+ as client (i.e., you are calling out an ISP to establish
168
+ connection to it), you need to realize a few more tunning
169
+ steps on <filename>/etc/wvdial.conf</filename> to set the
170
+ information related of that Internet Service Provider (ISP)
171
+ you want to get connected to (e.g., uncommenting the
170
172
<code>Phone</code>, <code>Username</code> and
171
173
<code>Password</code> lines above to set the appropiate values
172
- there) and then, instruct to <application>pppd</application>
173
- deamon about the user credential (e.g., user name and
174
- password) you will use to connect the target ISP. In this
175
- case, credentials defined both in
176
- <application>wvdial</application> and
177
- <application>pppd</application> applications must be exactly
174
+ there).
175
+ </para>
176
+
177
+ <para>
178
+ Once you've specified the ISP information, run the following
179
+ command to stablish connection:
178
- the same.
179
180
</para>
180
181
181
- </sect3>
182
+ <screen>sudo /usr/bin/wvdial</screen>
182
-
183
- <sect3 id="configurations-ppp-modem-config-server">
184
- <title>The Server Settings</title>
185
183
184
+ <note>
186
185
<para>
187
- ...
186
+ Both <command>wvdial</command> and
187
+ <command>wvdialconf</command> commands must be run with
188
+ administrative privilages because its configuration file
189
+ (<filename>/etc/wvdial.conf</filename>) is readable by the
190
+ <systemitem class="username">root</systemitem> user only.
188
191
</para>
192
+ </note>
189
193
190
194
</sect3>
191
195
192
- <sect3 id="configurations-ppp-modem-config-client">
193
- <title>The Client Settings</title>
196
+ <sect3 id="configuration-ppp-modem-config-scn">
197
+ <title><command>system-config-network</command></title>
198
+
194
199
<para>
195
- ...
200
+ In addition to the configuration process described so far, you
201
+ can manage modem configurations through the
202
+ <command>system-config-network</command> command. This command
203
+ provides a graphical interface (administrative privileges
204
+ required) which let you configure several ISP and alternate
205
+ the one you connect to. This command has been already
206
+ documented in the <citetitle>Deployment Guide</citetitle>
207
+ availabe in the <package>Deployment_Guide</package> and we
208
+ won't duplicate that information here. However, there are some
209
+ differences between the output produced by
210
+ <command>system-config-network</command> and
211
+ <command>wvdialconf</command> commads you need to be aware of.
196
212
</para>
197
- </sect3>
198
213
199
- </sect2>
214
+ <para>
215
+ The first thing to know is that both
216
+ <command>system-config-network</command> and
217
+ <command>wvdialconf</command> commands write configurations to
218
+ the <filename>/etc/wvdial.conf</filename> file, but the
219
+ interface provided by <command>system-config-network</command>
220
+ command doesn't detect the configuration intially created by
221
+ <command>wvdialconf</command> command. In fact, if you set a
222
+ new (modem) hardware configuration through the interface
223
+ provided by the <command>system-config-network</command>
224
+ command, any configuraion previously created by
225
+ <command>wvdailconf</command> will be lost.
226
+ </para>
227
+
228
+ <caution>
229
+ <para>
230
+ The interface provided by
231
+ <command>system-config-network</command> command doesn't
232
+ provide modem device detection (as
233
+ <command>wvdialconf</command> would do) and uses the
234
+ <filename>/dev/modem</filename> as default location. This
235
+ location doesn't exists by default, so whatever configuration
236
+ you set from it will not work. To solve this, chose one of the
237
+ following workarounds:
238
+ </para>
239
+ <itemizedlist>
240
+ <listitem>
241
+ <para>
242
+ Replace the <filename>/dev/modem</filename> location by that
243
+ one <command>wvdialconf</command> found when the interface
244
+ provided by <command>system-config-network</command> ask you
245
+ to enter the modem device.
246
+ </para>
247
+ </listitem>
248
+ <listitem>
249
+ <para>
250
+ Create <filename>/dev/modem</filename> location as a symbolic
251
+ link to that location found by <command>wvdialconf</command>
252
+ command. For example:
253
+ <screen>sudo /bin/ln -s /dev/ttyACM0 /dev/modem</screen>
254
+ </para>
255
+ </listitem>
256
+ </itemizedlist>
257
+ </caution>
200
258
201
- <sect2 id="configurations-ppp-modem-verification">
202
- <title>Verification</title>
203
259
<para>
204
- ...
260
+ Inside the <filename>/etc/wvdial.conf</filename> configuration
261
+ file, the interface provided by
262
+ <command>system-config-network</command> identifies default
263
+ modem configurations through the line <code>[Modem0]</code>,
264
+ while the <command>wvdialconf</command> command does the same
265
+ through the line <code>[Dialer Defauls]</code>. Something
266
+ interesting about the configuration file created by
267
+ <command>system-config-network</command> is that it is
268
+ possible to create several ISP configurations that reuse
269
+ default settings in the <code>[Modem0]</code> section. For
270
+ example, consider the following example:
205
271
</para>
206
272
207
273
<screen>
208
- --> WvDial: Internet dialer version 1.54.0
209
- --> Cannot get information for serial port.
210
- --> Initializing modem.
211
- --> Sending: ATZ
212
- ATZ
213
- OK
214
- --> Sending: ATQ0 V1 E1 S0=0 &amp;C1 &amp;D2 +FCLASS=0
215
- ATQ0 V1 E1 S0=0 &amp;C1 &amp;D2 +FCLASS=0
216
- OK
217
- --> Modem initialized.
218
- --> Sending: ATDT520347
219
- --> Waiting for carrier.
220
- ATDT520347
221
- NO DIALTONE
222
- --> No dial tone.
223
- --> Disconnecting at Thu Sep 29 13:04:30 2011
274
+ [Modem0]
275
+ Modem = /dev/ttyACM0
276
+ Baud = 460800
277
+ SetVolume = 2
278
+ Dial Command = ATDT
279
+ Init1 = ATZ
280
+ Init3 = ATM1L2
281
+ FlowControl = CRTSCTS
282
+ [Dialer Vispa_Internet]
283
+ Username = signup
284
+ Password = rebel
285
+ Phone = 08453080125
286
+ Stupid Mode = 1
287
+ Init1 = ATZ
288
+ Init2 = ATQ0 V1 E1 S0=0 &amp;C1 &amp;D2 +FCLASS=0
289
+ Inherits = Modem0
224
290
</screen>
291
+
292
+ </sect3>
293
+
225
294
</sect2>
226
295
227
296
</sect1>