- Timestamp:
- 03/15/2008 07:05:04 AM (17 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 12.2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gimp3, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/for-12.3, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/spidermonkey128, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 56507332
- Parents:
- 07dfa4f
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
connect/dialup/ppp.xml
r07dfa4f rab8365a 75 75 <note id="ppp-kernel"> 76 76 <para><application>PPP</application> support (CONFIG_PPP), 77 the asynchronous line discipline (CONFIG_PPP_ASYNC), and the 78 driver for your serial port device must be 79 compiled into the kernel or loaded as a kernel module. 80 Udev doesn't load the ppp_generic module automatically, it must be 81 mentioned in the <filename>/etc/sysconfig/modules</filename> file.</para> 77 the asynchronous line discipline (CONFIG_PPP_ASYNC), the 78 driver for your serial port device and/or the PPP over Ethernet 79 (PPPoE) protocol driver (CONGIG_PPPOE) must be compiled into the 80 kernel or loaded as kernel modules. 81 Udev doesn't load the ppp_generic and pppoe modules automatically, they 82 must be mentioned in the <filename>/etc/sysconfig/modules</filename> 83 file.</para> 82 84 </note> 83 85 … … 86 88 </indexterm> 87 89 90 <para>Create (as <systemitem class="username">root</systemitem>) 91 the group for users who may run <application>PPP</application>:</para> 92 93 <screen role="root"><userinput>groupadd -g 52 pppusers</userinput></screen> 94 88 95 <para>Install <application>PPP</application> by running the 89 96 following commands:</para> … … 96 103 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 97 104 98 <screen role='root'><userinput>groupadd -g 52 pppusers && 99 make install && 105 <screen role='root'><userinput>make install && 100 106 <!-- FIXME: is "make install-etcppp" needed for KPPP/WvDial? 101 107 The example configuration below overwrites two of three files, and … … 155 161 or <application>KPPP</application> from 156 162 <xref linkend="kdenetwork"/>. The text below explains how to set up 157 <!-- PPPoE, -->dialup and GPRS connections using only tools provided with163 PPPoE, dialup and GPRS connections using only tools provided with 158 164 the <application>PPP</application> package. All configuration steps 159 165 in this section are executed as … … 162 168 <sect4> 163 169 <title>Setting the passwords</title> 170 171 <warning><para>Instructions in this section result in your password 172 appearing on the screen in a visible clear-text form. Make sure that 173 nobody else looks at the screen.</para></warning> 164 174 165 175 <para>Passwords are stored in <filename>/etc/ppp/pap-secrets</filename> … … 227 237 configuration information about a specific connection to 228 238 <command>pppd</command>:</para> 229 <screen role="root"><userinput>cat $gt;/etc/ppp/dialup.chat <<"EOF"</userinput>239 <screen role="root"><userinput>cat >/etc/ppp/dialup.chat <<"EOF"</userinput> 230 240 <literal>ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' 231 241 ABORT 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT DELAYED … … 290 300 <!-- FIXME: watch for new standards! SkyLink is already offering 291 301 3.1 megabits per second with CDMA mobile phones, and 292 293 294 302 the configuration below doesn't work. It is reported that 303 a regular dialup setup with the telephone number "#777", 304 username "mobile" and password "internet" works with SkyLink. --> 295 305 296 306 The maximum possible data transfer rate is 170 kilobits per second … … 321 331 # \T is the APN, passed from /etc/ppp/peers/<replaceable>gprs</replaceable> 322 332 # This example stores the APN as profile #1 in the phone. 323 # The telephone number, *99***<profile_number>#, is always the same333 # The "telephone number", *99***<profile_number>#, is always the same. 324 334 # If you want to store this as profile #2, change 1 to 2 in the 325 335 # following two lines. … … 353 363 354 364 <sect4> 355 <title>Establishing the connection</title> 365 <title>PPPoE connections</title> 366 367 <!-- This section has been tested with the "USI" ISP in Yekaterinburg, 368 Russia. Other editors can test it as described in 369 http://linuxfromscratch.org/pipermail/blfs-dev/2008-March/018290.html 370 - Alexander E. Patrakov --> 371 372 <para>PPPoE connections are established over Ethernet, typically between 373 a computer and an ADSL router (usually installed in the same room) 374 that forwards the packets down the telephone line using frequencies 375 25-2500 kHz, thus not interfering with voice calls. Although the router 376 can, in theory, forward any Ethernet packet, PPP encapsulation is used 377 for password-based authentication, so that the ISP can limit the 378 bandwidth and charge money according to the chosen tariff. The maximum 379 data transfer rate on ADSL is 24 megabits per second, and the gateway 380 ping time is typically less than 10 ms. In order to configure a PPPoE 381 connection, it is required to know the username, the password, and, 382 sometimes, the service name and/or the access concentrator name.</para> 383 384 <para>In order to configure a PPPoE connection, only the peer file 385 has to be created:</para> 386 <screen role="root"><userinput>cat >/etc/ppp/peers/adsl <<"EOF"</userinput> 387 <literal>plugin rp-pppoe.so 388 # Ethernet interface name 389 <replaceable>eth0</replaceable> 390 # Your username at the ISP 391 user "<replaceable>jdoe</replaceable>" 392 # What should be in the second column in /etc/ppp/*-secrets 393 remotename "<replaceable>adsl</replaceable>" 394 # If needed, specify the service and the access concentrator name 395 # rp_pppoe_service "<replaceable>internet</replaceable>" 396 # rp_pppoe_ac "<replaceable>ac1</replaceable>" 397 398 # The settings below usually don't need to be changed 399 noauth 400 hide-password 401 updetach 402 debug 403 defaultroute 404 noipdefault 405 usepeerdns</literal> 406 <userinput>EOF</userinput></screen> 407 </sect4> 408 409 <sect4> 410 <title>Establishing the connection manually</title> 356 411 357 412 <para>In order to establish a PPP connection described by the … … 363 418 <para>In order to tear the connection down, run:</para> 364 419 <screen><userinput>poff <replaceable>peername</replaceable></userinput></screen> 420 421 </sect4> 422 423 <sect4> 424 <title>Bringing up PPPoE connection at boot time</title> 425 <para>If your service provider does not charge by the minute, it is 426 usually good to have a bootscript handle the connection for you. 427 You can, of course, choose not to install the following script, and 428 start your connection manually with the <command>pon</command> command, 429 as described above. If you wish your PPPoE connection to be brought 430 up at boot time, run:</para> 431 432 <screen role='root'><userinput>make install-service-pppoe</userinput></screen> 433 434 <para>The above command installs the <filename>pppoe</filename> 435 service script and the <filename>/etc/ppp/peers/pppoe</filename> 436 file with some settings that make sense for most PPPoE connections. 437 The bootscript calls <command>pppd</command> with the the following 438 options:</para> 439 440 <screen>pppd call pppoe ${1} linkname ${1} ${PPP_OPTS}</screen> 441 442 <para>Here <quote>${1}</quote> is the network interface name, 443 <quote>linkname ${1}</quote> is added for creation of the 444 <filename>/var/run/ppp-${1}.pid</filename> file with the 445 <command>pppd</command> process ID (to be used when bringing 446 the connection down), and the <quote>${PPP_OPTS}</quote> variable 447 contains user-specified options such as <quote>user</quote> and 448 <quote>remotename</quote>.</para> 449 450 <para>Now create the config file for use with the <filename>pppoe</filename> 451 service script:</para> 452 453 <screen role='root'><userinput>install -v -d /etc/sysconfig/network-devices/ifconfig.eth0 && 454 cat > /etc/sysconfig/network-devices/ifconfig.eth0/pppoe << "EOF" 455 <literal>ONBOOT="yes" 456 SERVICE="pppoe" 457 PPP_OPTS="user <replaceable>jdoe</replaceable> remotename <replaceable>adsl</replaceable>"</literal> 458 EOF</userinput></screen> 459 460 <note><para>Instead of specifying additional options in the $PPP_OPTS 461 variable, you can also edit the <filename>/etc/ppp/peers/pppoe</filename> 462 file, but then your configuration will be lost when upgrading 463 BLFS bootscripts.</para></note> 365 464 366 465 </sect4>
Note:
See TracChangeset
for help on using the changeset viewer.