Server IP : 103.119.228.120 / Your IP : 3.133.133.39 Web Server : Apache System : Linux v8.techscape8.com 3.10.0-1160.119.1.el7.tuxcare.els2.x86_64 #1 SMP Mon Jul 15 12:09:18 UTC 2024 x86_64 User : nobody ( 99) PHP Version : 5.6.40 Disable Function : shell_exec,symlink,system,exec,proc_get_status,proc_nice,proc_terminate,define_syslog_variables,syslog,openlog,closelog,escapeshellcmd,passthru,ocinum cols,ini_alter,leak,listen,chgrp,apache_note,apache_setenv,debugger_on,debugger_off,ftp_exec,dl,dll,myshellexec,proc_open,socket_bind,proc_close,escapeshellarg,parse_ini_filepopen,fpassthru,exec,passthru,escapeshellarg,escapeshellcmd,proc_close,proc_open,ini_alter,popen,show_source,proc_nice,proc_terminate,proc_get_status,proc_close,pfsockopen,leak,apache_child_terminate,posix_kill,posix_mkfifo,posix_setpgid,posix_setsid,posix_setuid,dl,symlink,shell_exec,system,dl,passthru,escapeshellarg,escapeshellcmd,myshellexec,c99_buff_prepare,c99_sess_put,fpassthru,getdisfunc,fx29exec,fx29exec2,is_windows,disp_freespace,fx29sh_getupdate,fx29_buff_prepare,fx29_sess_put,fx29shexit,fx29fsearch,fx29ftpbrutecheck,fx29sh_tools,fx29sh_about,milw0rm,imagez,sh_name,myshellexec,checkproxyhost,dosyayicek,c99_buff_prepare,c99_sess_put,c99getsource,c99sh_getupdate,c99fsearch,c99shexit,view_perms,posix_getpwuid,posix_getgrgid,posix_kill,parse_perms,parsesort,view_perms_color,set_encoder_input,ls_setcheckboxall,ls_reverse_all,rsg_read,rsg_glob,selfURL,dispsecinfo,unix2DosTime,addFile,system,get_users,view_size,DirFiles,DirFilesWide,DirPrintHTMLHeaders,GetFilesTotal,GetTitles,GetTimeTotal,GetMatchesCount,GetFileMatchesCount,GetResultFiles,fs_copy_dir,fs_copy_obj,fs_move_dir,fs_move_obj,fs_rmdir,SearchText,getmicrotime MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/local/ssl/share/doc/ppp-2.4.5/ |
Upload File : |
PPPoE Support ------------- Michal Ostrowski 8 August 2001 for ppp-2.4.2 Updated for ppp-2.4.5 by Paul Mackerras, Sep 08 1. Introduction --------------- This document describes the support for PPP over Ethernet (PPPoE) included with this package. It is assumed that the reader is familiar with Linux PPP (as it pertains to tty/modem-based connections). In particular, users of PPP in the Linux 2.2 series kernels should ensure they are familiar with the changes to the PPP implementation in the 2.4 series kernels before attempting to use PPPoE features. If you are not familiar with PPP, I recommend looking at other packages which include end-user configuration tools, such as Roaring Penguin (http://www.roaringpenguin.com/pppoe). PPPoE is a protocol typically used by *DSL providers to manage IP addresses and authenticate users. Essentially, PPPoE provides for a PPP connection to be established not over a physical serial-line or modem, but over a logical connection between two unique MAC-addresses on an ethernet network. Once the PPPoE layer discovers the end-points to be used in the link and negotiates it, frames may be sent to and received from the PPPoE layer just as if the link was a serial line (or that is how it's supposed to be). With this in mind, the goal of the implementation of PPPoE support in Linux is to allow users to simply specify that the device they intend to use for the PPP connection is an ethernet device (i.e. "eth0") and the rest of the system should function as usual. 2. Using PPPoE -------------- This section is a quick guide for getting PPPoE working, to allow one to connect to their ISP who is providing PPPoE based services. 1. Enable "Prompt for development and/or incomplete code/drivers" and "PPP over Ethernet" in your kernel configuration. Most distributions will include the kernel PPPoE module by default. 2. Compile and install your kernel. 3. Install the ppp package. 4. Add the following line to /etc/ppp/options: plugin rp-pppoe.so The effect of this line is simply to make "eth0", "eth1", ....,"ethx" all valid device names for pppd (just like ttyS0, ttyS1). 5. Add the necessary authentication options to your pppd configuration (i.e. PAP/CHAP information). If you wish to maintain seperate configurations for different devices you may place configuration options in device-specific configuration files: /etc/ppp/options.devname (devname=ttyS0, ttyS1, eth0, eth1 or any other valid device name). 6. Invoke pppd with the appropriate device name: e.g. "pppd eth0" Do not include any compression or flow control options in your PPPoE configuration. They will be ignored. Again, here it is assumed that the reader is familiar with the general process of configuring PPP. The steps outlined here refer only to the steps and configuration options which are PPPoE specific, and it is assumed that the reader will also configure other aspects of the system (e.g. PAP authentication parameters). 3. Advanced Functionality -------------------------- For more advanced functionality (such as providing PPPoE services) and user configuration tools, look to the Roaring Penguin PPPoE software package (http://www.roaringpenguin.com/pppoe). 4. Credits ----------- The PPPoE plugin included in this package is a component of the Roaring Penguin PPPoE package, included in this package courtesy of Roaring Penguin Software. (http://www.roaringpenguin.com).