Изпечатай

[astronom]

Здравейте. Публикувам тук конфигурационния файл на pppoe, pap-secrets, както и syslog-a. Нека някой ме опровергае ако PAP authentication failed не значи проблем с username и password.
Смених доставчика си на LAN Интернет и в момента се оптивам да ползвам услугите му. Доставчикът е HomeLan (data.bg). Ако някой има опит в настройването на PPPoE (Point-to-Point over Ethernet) към HomeLan под Linux, нека сподели своя опит.
Подробности за конфигурацията:
OS: Slackware Linux 8.1
pppd: pppd 2.4.1
pppoe: rp-pppoe 3.5

pppoe.conf

Примерен код

$cat /etc/ppp/pppoe.conf #*********************************************************************** # # pppoe.conf # # Configuration file for rp-pppoe.  Edit as appropriate and install in # /etc/ppp/pppoe.conf # # NOTE: This file is used by the adsl-start, adsl-stop, adsl-connect and #       adsl-status shell scripts.  It is *not* used in any way by the #       "pppoe" executable. # # Copyright (C) 2000 Roaring Penguin Software Inc. # # This file may be distributed under the terms of the GNU General # Public License. # # LIC: GPL # $Id: pppoe.conf,v 1.10 2002/04/09 17:28:38 dfs Exp $ #*********************************************************************** # When you configure a variable, DO NOT leave spaces around the "=" sign. # Ethernet card connected to ADSL modem ETH='eth0' # ADSL user name.  You may have to supply "@provider.com"  Sympatico # users in Canada do need to include "@sympatico.ca" # Sympatico uses PAP authentication.  Make sure /etc/ppp/pap-secrets # contains the right username/password combination. # For Magma, use [EMAIL=xxyyzz@magma.ca]xxyyzz@magma.ca[/EMAIL] USER='gsotirov' # Bring link up on demand?  Default is to leave link up all the time. # If you want the link to come up on demand, set DEMAND to a number indicating # the idle time after which the link is brought down. DEMAND=no #DEMAND=300 # DNS type: SERVER=obtain from server; SPECIFY=use DNS1 and DNS2; # NOCHANGE=do not adjust. DNSTYPE=SERVER # Obtain DNS server addresses from the peer (recent versions of pppd only) # In old config files, this used to be called USEPEERDNS.  Changed to # PEERDNS for better Red Hat compatibility PEERDNS=yes DNS1= DNS2= # Make the PPPoE connection your default route.  Set to # DEFAULTROUTE=no if you don't want this. DEFAULTROUTE=yes ### ONLY TOUCH THE FOLLOWING SETTINGS IF YOU'RE AN EXPERT # How long adsl-start waits for a new PPP interface to appear before # concluding something went wrong.  If you use 0, then adsl-start # exits immediately with a successful status and does not wait for the # link to come up.  Time is in seconds. # # WARNING WARNING WARNING: # # If you are using rp-pppoe on a physically-inaccessible host, set # CONNECT_TIMEOUT to 0.  This makes SURE that the machine keeps trying # to connect forever after adsl-start is called.  Otherwise, it will # give out after CONNECT_TIMEOUT seconds and will not attempt to # connect again, making it impossible to reach. CONNECT_TIMEOUT=30 # How often in seconds adsl-start polls to check if link is up CONNECT_POLL=2 # Specific desired AC Name ACNAME= # Specific desired service name SERVICENAME= # Character to echo at each poll.  Use PING="" if you don't want # anything echoed PING="." # File where the adsl-connect script writes its process-ID. # Three files are actually used: #   $PIDFILE       contains PID of adsl-connect script #   $PIDFILE.pppoe contains PID of pppoe process #   $PIDFILE.pppd  contains PID of pppd process CF_BASE=`basename $CONFIG` PIDFILE="/var/run/$CF_BASE-adsl.pid" # Do you want to use synchronous PPP?  "yes" or "no".  "yes" is much # easier on CPU usage, but may not work for you.  It is safer to use # "no", but you may want to experiment with "yes".  "yes" is generally # safe on Linux machines with the n_hdlc line discipline; unsafe on others. SYNCHRONOUS=no # Do you want to clamp the MSS?  Here's how to decide: # - If you have only a SINGLE computer connected to the ADSL modem, choose #   "no". # - If you have a computer acting as a gateway for a LAN, choose "1412". #   The setting of 1412 is safe for either setup, but uses slightly more #   CPU power. CLAMPMSS=1412 #CLAMPMSS=no # LCP echo interval and failure count. LCP_INTERVAL=20 LCP_FAILURE=3 # PPPOE_TIMEOUT should be about 4*LCP_INTERVAL PPPOE_TIMEOUT=80 # Firewalling: One of NONE, STANDALONE or MASQUERADE FIREWALL=STANDALONE # Linux kernel-mode plugin for pppd.  If you want to try the kernel-mode # plugin, use LINUX_PLUGIN=/etc/ppp/plugins/rp-pppoe.so LINUX_PLUGIN= # Any extra arguments to pass to pppoe.  Normally, use a blank string # like this: PPPOE_EXTRA="" # Rumour has it that "Citizen's Communications" with a 3Com # HomeConnect ADSL Modem DualLink requires these extra options: # PPPOE_EXTRA="-f 3c12:3c13 -S ISP" # Any extra arguments to pass to pppd.  Normally, use a blank string # like this: PPPD_EXTRA="" ########## DON'T CHANGE BELOW UNLESS YOU KNOW WHAT YOU ARE DOING # If you wish to COMPLETELY overrride the pppd invocation: # Example: # OVERRIDE_PPPD_COMMAND="pppd call dsl" # If you want adsl-connect to exit when connection drops: # RETRY_ON_FAILURE=no

syslog

Примерен код

$cat /var/log/syslog | tail Jan 29 21:42:12 sotirov pppd[389]: PAP authentication failed Jan 29 21:42:12 sotirov pppoe[390]: read (asyncReadFromPPP): Session 732: Input/output error Jan 29 21:42:22 sotirov pppd[435]: PAP authentication failed Jan 29 21:42:22 sotirov pppoe[436]: read (asyncReadFromPPP): Session 733: Input/output error Jan 29 21:42:31 sotirov pppd[490]: PAP authentication failed Jan 29 21:42:31 sotirov pppoe[491]: read (asyncReadFromPPP): Session 734: Input/output error Jan 29 21:42:40 sotirov pppd[533]: PAP authentication failed Jan 29 21:42:40 sotirov pppoe[534]: read (asyncReadFromPPP): Session 735: Input/output error

pap-secrets

Примерен код

$cat /etc/ppp/pap-secrets # Username      Server      Password      IP addresses "gsotirov"      *           "my_password"

[growchie]

taka na pyrvo chetene ne mi se struva che imash problemi s parolata se pak dava I/O error.
do kolkoto vijdam se opitvash da pusnesh vpn. ne sym siguren ama v sluchaja pptp maj shte ti svyrshi poveche rabota ot pppoe. njama ideja se pak kak e nastroen lana tam.
vijdam che imash i/o error ot pppoe-to

[growchie]

a i oshte neshto ne sym 100% siguren ama vij si kavichkite v pap-secret fileto maj njamashe takiva...
pone pri mene njamashe ..... navremeto vij v google po vyprosa

[astronom]

>taka na pyrvo chetene ne mi se struva che imash problemi s parolata se pak dava I/O error.

Да, забелязах го това, но все пак тази грешка е след 'pppd[<pid>]: PAP authentication failed' и затова обръщам внимание първо на нея. Имах още грешки преди тези, но ги оправих и остана само това.

>a i oshte neshto ne sym 100% siguren ama vij si kavichkite v pap-secret fileto maj njamashe takiva...

Това за кавичките в pap-secrets файла мисля, че не е проблем. Пробвах първо без кавички (както май е стандартно), след това с двойни кавички ["] и с единични кавички ['], но резлутатът не се промени.

Възможно ли е този проблем да е в резултат на това, че доставчикът използва M$ PAP/CHAP протоколите? Дали въобще pppd ги поддържа тези M$ bullshits?

Поздрави!!!

http://www.linux-bg.org/cgi-bin....8168583