Pelo amor de Deus, me ajudem! :'(

[Beto]

Bom eu uso o kubuntu 5.10, Kernel 2.6.12.5, kde 3.4.2
bom eu tenho um modem q no meu windows é reconhecido como:

PCTEL Platinum v.90 Modem(ele conecta a 52 kb)

no linux atraves do comando lspci:

modem pctel inc hsp micromodem 56 rev 02

gostaria de obter ajudar de como instalar ja fui no site dado no no guiadohardware mais deu erro em um tal de gcc, ele nem passa dai da erro no gcc, pelo amor de Deus me ajudem, preciso muito disso!
ñ aguento mais esta presso ainda ao windows  

[josevitor]

O driver do teu modem deve ter o mesmo padrão de compiliação do kernel.. vasculha no forum atras de informações sobre gcc que você entenderá.. existe até um a respeito de webcam que fala disso.. procura que você acha.

Vai em pesquisar, seleciona a opção de pesquisa por todas as palavaras e digita "web cam gcc".

Vai com fé, a fé não costuma falhar.

heheh.

boa sorte

[KubLin]

veja: http://www.guiadohardware.net/guias/05/

falou

[alarcon]

Bom eu uso o kubuntu 5.10, Kernel 2.6.12.5, kde 3.4.2
bom eu tenho um modem q no meu windows é reconhecido como:

PCTEL Platinum v.90 Modem(ele conecta a 52 kb)

no linux atraves do comando lspci:

modem pctel inc hsp micromodem 56 rev 02

gostaria de obter ajudar de como instalar ja fui no site dado no no guiadohardware mais deu erro em um tal de gcc, ele nem passa dai da erro no gcc, pelo amor de Deus me ajudem, preciso muito disso!
ñ aguento mais esta presso ainda ao windows  

Vc antes de usar o driver para compilar tem de ter instalado na sua distro o mesmo compilador que foi usado para compilar o kernel, portanto descubra qual foi o usado no kernel.

A forma mais simples de descobrir isso é através do arquivo "/proc/version":

 

cat /proc/version

Se você estiver usando o Ubuntu 5.10, por exemplo, vai receber como resposta:

   

Linux version 2.6.12-9-386(buildd@rothera) (gcc version 3.4.5 20050809)

Por aqui podemos ver que está sendo usado o Kernel 2.6.12-9 (compilado sem otimizações para os processadores atuais, daí o "386"), que por sua vez foi compilado usando o gcc 3.4.

Sabendo agora em qual versão do gcc foi compilado o seu kernel então procure na internet pelo pacote .deb para ele com um outro sistema operacional já que com o Ubuntu não é possível.


Por fim use o driver mais recente da PCTel para os modems HSP56 Micromodem que é o:

http://linmodems.technion.ac.il/pctel-linux/pctel-0.9.7-9-rht-5.tar.gz

Me parece que este não é mais necessário fazer a correção falada por Carlos e. Morimoto do kurumin.

Veja a lista de Modems suportados por este novo driver da PCTel:

134d:7890   PCtel HSP MicroModem 56                    PCT789T-C1     pct789
134d:7891   PCtel HSP MicroModem 56                    PCT 789T          pct789
134d:7892   PCtel HSP MicroModem 56                    PCT 789T-A       pct789
134d:7893   PCtel HSP MicroModem 56                    S911 K017        pct789
134d:7894   PCtel HSP MicroModem 56                    FT13                   pct789
134d:7895   PCtel HSP MicroModem 56                    PCT789T-C1     pct789
134d:7896   PCtel HSP MicroModem 56                    PCT789T-C1     pct789
134d:7897   PCtel HSP MicroModem 56                    PCT789T           pct789
13f6:0211    C-Media CM8738                                     CM8738             cm8738

[Beto]

Bom Jose Vitor, meu problema ñ é com webcam e sim com meu modem e o gcc ja conseguir instalar realmente estavde sistalado obrigado   :lol:

Kublin: man eu ja li tudo ñ so li como salvei e coloquei lá no linux pra poder ver e  fazer mais nada mais obrigado mesmo assim

Alarcon vou fazer isso mais desde já obrigado pela ajuda

[Beto]

Alarcon
esta dando um erro no comando "Printf" ele diz q ñ é compativel e depois com o codigo "Main"
da erro na linha 448 q ñ contem um arquivo ou pasta ./t

[alarcon]

Alarcon
esta dando um erro no comando "Printf" ele diz q ñ é compativel e depois com o codigo "Main"
da erro na linha 448 q ñ contem um arquivo ou pasta ./t

Bem vamos lá, antes de usar qualquer driver para compilação se faz necessário a presença de alguns pacotes no seu sistema que são certos compiladores e etc.

Eu tenho o Ubuntu 5.10 e no caso dele os arquivos necessários são:

make

gcc
 -binutils
 -gcc-4.0
   
build-essential
-dpkg-dev
-g++
-g++-4.0
-libc6-dev
-libstdc++6-4.0-dev
-linux-kernel-headers

linux-headers-2.6.12-9-386
-linux-headers-2.6.12-9

Estes pacotes, em negrito, vc pode instalar pelo Synaptic do Ubuntu 5.10 sem precisar da internet, pois já vem no Ubuntu mais não estão ainda instalados. Os que estão logo abaixo dos em negrito e com um traço "-" antes do nome são os arquivos dependentes que serão instalados automáticamente com os principais quando vc selecionar eles (os em negrito) lá no Synaptic que se encontra em: Sistema > Administração >Gerenciador de Pacotes Synaptic. Com o programa aberto clique no botão procurar (Search) e digite o nome do pacote desejado e depois de encontrá-los clique com o botão direito do mouse sobre ele e selecione marcar para instalação e depois clique no botão Aplicar e aguarde o processo de instalação.

Atenção: Vc informou aqui que seu kernel é outro 2.6.12.5 pois sua distro é o kubuntu 5.10 então pode ser diferente algumas coisa. Então no caso o pacote linux-headers-2.6.12-9-386 informado logo acima deverá ser mudado para a versão do seu kernel, ou seja, linux-headers-2.6.12-5-386 ou algo assim.

Bem depois de instalado os pacotes acima e de ter verificado em qual gcc foi compilado o kernel com eu já disse aqui anteriormente mais para cima, procure na net pelos mesmos para poder instalá-los que estes nã ovem na distro.

Caso o gcc seja a versão 3.4 vc pode baixar aqui:

http://archive.ubuntu.com/ubuntu/pool/main/g/gcc-3.4/gcc-3.4-base_3.4.4-6ubuntu8_i386.deb

http://archive.ubuntu.com/ubuntu/pool/main/g/gcc-3.4/cpp-3.4_3.4.4-6ubuntu8_i386.deb

http://archive.ubuntu.com/ubuntu/pool/main/g/gcc-3.4/gcc-3.4_3.4.4-6ubuntu8_i386.deb

OBs: abra um terminal ( Menu Aplicações> Acessório > Terminal) e instale nesta ordem apresentada acima, da seguinte forma:

   

$ sudo su
   Password: sua senha
   # dpkg -i gcc-3.4-base_3.4.4-6ubuntu8_i386.deb cpp-3.4_3.4.4-6ubuntu8_i386.deb gcc-3.4_3.4.4-6ubuntu8_i386.deb

Obs: os símbolos "$" e "#" em negrito e à esquerda dos comandos não são para serem digitados, apenas indicam um comando dado como usuário normal ($) e um comando dado como root (#) que é um superusuário e pode tudo, ao contrário do outro que é limitado.



Ainda com o terminal aberto e como root (símbolo #) digite os seguintes comandos:

 

# cd /usr/bin
   #  ln -sf /usr/bin/cpp-3.4 cpp
   #  ln -sf /usr/bin/gcc-3.4 gcc
   #  ln -sf /usr/bin/gccbug-3.4 gccbug
   #  ln -sf /usr/bin/gcov-3.4 gcov
   #  ln -sf /usr/bin/i486-linux-gnu-cpp-3.4 i486-linux-gnu-cpp
   #  ln -sf /usr/bin/i486-linux-gnu-gcc-3.4 i486-linux-gnu-gcc

bom depois de tudo isso aí é que vc vai usar o driver da PCTel e não antes destes pacotes instalados  Ok.

[Beto]

man conseguir instalar
mais ñ conecta, ele não se comunica  com o modem no kppp, como fala carlos morimoto
bom instalei deu tudo normal sem nenhuma mensagem de erro
logo depois fui ao kppp como o carlos falou e logo quando ele abri da mensagem sem a pasta "/etc/resolv.conf"
depois  quando peço pra testar o modem se comunicar, ele abri  uma janela comunicando com ATI diz q ñ tem como  comunicar
fiquei ate as 04:40 da manhã e nada

[alarcon]

man conseguir instalar
mais ñ conecta, ele não se comunica  com o modem no kppp, como fala carlos morimoto
bom instalei deu tudo normal sem nenhuma mensagem de erro
logo depois fui ao kppp como o carlos falou e logo quando ele abri da mensagem sem a pasta "/etc/resolv.conf"
depois  quando peço pra testar o modem se comunicar, ele abri  uma janela comunicando com ATI diz q ñ tem como  comunicar
fiquei ate as 04:40 da manhã e nada

Bom, depois de compilar o driver do modem e se tudo tiver ocorrido sem erros vc deveria fazer isso:

abra um terminal (Aplicações > Acessórios > Terminal) e vire root:

sudo su
Password: sua senha

e faça isso:

modprobe linmodem
modprobe pctel country_code=33
modprobe pctel_hw

rm -f /dev/modem
ln -sf /dev/ttyS_PCTEL0 /dev/modem
chmod 666 /dev/modem

Agora crie o arquivo que vai ser o responsável pela ativação do modem no boot (ainda como root, comando sudo su):

echo '#!/bin/sh' >> /etc/init.d/ativar-modem
echo 'modprobe linmodem' >> /etc/init.d/ativar-modem
echo 'modprobe pctel country_code=33' >> /etc/init.d/ativar-modem
echo 'modprobe pctel_hw' >> /etc/init.d/ativar-modem
chmod +x /etc/init.d/ativar-modem
ln -sf /etc/init.d/ativar-modem /etc/rc2.d/S98ativar-modem

Com isso vc vai criar dois arquivos. Um chamado de ativar-modem em /etc/init.d/ e o outro de S98ativar-modem em /etc/rc2.d/ que são os responsáveis pela inicialização do modem na hora do boot. Após estes procedimentos, por favor REINICIE o seu PC.

Caso ainda não funcione a sua conexão com o kppp, então estou mostrando uma configuração padrão para o kppp que vc deve fazer aí por que funciona em 90% dos  casos.

Abra um Terminal (Aplicações > Acessório > Terminal) e desta vez não precisa ser como root e digite:

gedit /home/seu_nome_de_usuário_corrente/.kde/share/config/kppprc

Vc irá abrir o arquivo de configuração do kppp chamado de kppprc. Atenção, no caminho indicado acima veja que antes do nome kde tem um sinal de ponto (".") , deve ser digitado, que indica que esta pasta está oculta dentro da sua pasta de usuário.

Depois de abrir este arquivo (kppprc) deixe-o exatamente desta forma aqui:

pppdArguments=

[Account0]
AccountingEnabled=0
AccountingFile=
Authentication=4
AutoDNS=1
AutoName=0
BeforeConnect=
BeforeDisconnect=
CallbackPhone=
CallbackType=0
Command=
DNS=
DefaultRoute=1
DisconnectCommand=
Domain=
ExDNSDisabled=0
Gateway=0.0.0.0
IPAddr=0.0.0.0
Name=Nome para Conta
Password=Sua Senha de acesso do provedor
Phonenumber=Número para discar
ScriptArguments=
ScriptCommands=
StorePassword=1
SubnetMask=0.0.0.0
Username=Nome de usuário do provedor
VolumeAccountingEnabled=0
pppdArguments=

[General]
DefaultAccount=Nome para Conta
DefaultModem=Modem0
DockIntoPanel=1
NumberOfAccounts=1
NumberOfModems=1
PPPDebug=0
iconifyOnConnect=0

[Graph]
Background=255,255,255
Enabled=true
InBytes=0,0,255
OutBytes=255,0,0
Text=0,0,0

[Modem]
Speed=115200
UseLockFile=0

[Modem0]
AnswerResponse=CONNECT
AnswerString=ATA
BusyResponse=BUSY
BusyWait=0
ConnectResponse=CONNECT
DLPResponse=DIGITAL LINE DETECTED
Device=/dev/modem
DialString=ATDP (para pulso) ou ATDT  (para tom)
Enter=CR
EscapeGuardTime=50
EscapeResponse=OK
EscapeString=+++
FlowControl=Hardware [CRTSCTS]
HangUpResponse=OK
HangupString=+++ATH
InitDelay=50
InitResponse=OK
InitString=ATZ
InitString1=
Name=Modem0
NoCarrierResponse=NO CARRIER
NoDialToneDetection=ATX3
NoDialToneResp=NO DIALTONE
PreInitDelay=50
RingResponse=RING
Speed=115200
Timeout=60
ToneDuration=70
UseLockFile=0
Volume=1
VolumeHigh=M1L3
VolumeMedium=M1L1
VolumeOff=M0L0
WaitForDialTone=1

[Notification Messages]
Cancelar=No

[WindowPosition]
WindowPositionConWinX=323
WindowPositionConWinY=484
WindowPositionStatWinX=275
WindowPositionStatWinY=183

Mudando as partes em verde do texto acima para as suas configurações pessoas, salve, sai do arquivo e abra o kppp e tente novamente Ok.

Se mesmo assim continuar sem conexão, então veja o que Carlos E. Morimoto diz a respeito de conectar mais não navegar:

Em casos de problemas na hora de discar, experimente abrir o kppp como root. Isso evita muitos problemas relacionados a permissões de acesso a dispositivos e arquivos de configuração.
Caso a conexão seja efetuada normalmente, mas você não consiga navegar, verifique se o endereço do servidor DNS do provedor (ou qualquer outro DNS válido) foi adicionado corretamente ao arquivo "/etc/resolv.conf". Isto é muito comum quando o kppp é aberto com um login normal de usuário.
Caso o problema persista, pode ser que o sistema não esteja usando o modem como rota padrão (isso é comum caso você tenha também uma placa de rede). Para ajustar isso manualmente, use o comando:
# route add default ppp0
Em versões antigas, era necessário usar o comando "route del default" (que remove a rota padrão anterior) antes do "route add default ppp0" (que indica o uso do modem). Atualmente apenas o segundo comando basta.

É isso espero que estas informações lhe ajudem. :-)

[Beto]

Bom alarcon se algum dia eu te conheçe te dou um  bjo
é o seguinte o modem instalou!
ele faz assim!
disca 15002442(numero do ibest)
quando conecta da isso
o serviço pppd terminou inesperadamente
status saida: 1
veja em man pppd!
para explicação do erro...
mais o modem instalou obrigado
ai lovi iu alacon :p

[Beto]

Bom Alacon vou precisar de vc de novo
bom o q aconteceu, conseguir instalar o modem mais tava dando esse erro q eu falei ai em cima!
mais fui no site:
http://developer.kde.org/~kppp/index.html
e lá eu vi ele mandando abri
/etc/ppp/options[/]
e colocar
#[/] antes da informações, fiz isso massa conecta
mais os q ñ acessa site nenhum, ele  conecta faz logon na rede mostra o tempo o ip tudo, mais quando vou acessar nada
me ajude por favor
Gilberto

[alarcon]

Bom Alacon vou precisar de vc de novo
bom o q aconteceu, conseguir instalar o modem mais tava dando esse erro q eu falei ai em cima!
mais fui no site:
http://developer.kde.org/~kppp/index.html
e lá eu vi ele mandando abri
/etc/ppp/options[/]
e colocar
#[/] antes da informações, fiz isso massa conecta
mais os q ñ acessa site nenhum, ele  conecta faz logon na rede mostra o tempo o ip tudo, mais quando vou acessar nada
me ajude por favor
Gilberto

Bom Beto não sei o que pode está ocorrendo com vc mais o meu arquivo options que se encontra em /etc/ppp/ e que funciona perfeitamente o meu discador (gnome-ppp) com o provedor Ibest está assim:

# /etc/ppp/options
#
# Originally created by Jim Knoble <jmknoble@mercury.interpath.net>
# Modified for Debian by alvar Bray <alvar@meiko.co.uk>
# Modified for PPP Server setup by Christoph Lameter <clameter@debian.org>
#
# To quickly see what options are active in this file, use this command:
#   egrep -v '#|^ *$' /etc/ppp/options

# Specify which DNS Servers the incoming Win95 or WinNT Connection should use
# Two Servers can be remotely configured
# ms-dns 192.168.1.1
# ms-dns 192.168.1.2

# Specify which WINS Servers the incoming connection Win95 or WinNT should use
# ms-wins 192.168.1.50
# ms-wins 192.168.1.51

# Run the executable or shell command specified after pppd has
# terminated the link.  This script could, for example, issue commands
# to the modem to cause it to hang up if hardware modem control signals
# were not available.
#disconnect "chat -- \d+++\d\c OK ath0 OK"

# async character map -- 32-bit hex; each bit is a character
# that needs to be escaped for pppd to receive it.  0x00000001
# represents '\x01', and 0x80000000 represents '\x1f'.
asyncmap 0

# Require the peer to authenticate itself before allowing network
# packets to be sent or received.
# Please do not disable this setting. It is expected to be standard in
# future releases of pppd. Use the call option (see manpage) to disable
# authentication for specific peers.
auth

# Use hardware flow control (i.e. RTS/CTS) to control the flow of data
# on the serial port.
crtscts

# Use software flow control (i.e. XON/XOFF) to control the flow of data
# on the serial port.
#xonxoff

# Specifies that certain characters should be escaped on transmission
# (regardless of whether the peer requests them to be escaped with its
# async control character map).  The characters to be escaped are
# specified as a list of hex numbers separated by commas.  Note that
# almost any character can be specified for the escape option, unlike
# the asyncmap option which only allows control characters to be
# specified.  The characters which may not be escaped are those with hex
# values 0x20 - 0x3f or 0x5e.
#escape 11,13,ff

# Don't use the modem control lines.

#local

# Specifies that pppd should use a UUCP-style lock on the serial device
# to ensure exclusive access to the device.
lock

# Don't show the passwords when logging the contents of PAP packets.
# This is the default.
hide-password

# When logging the contents of PAP packets, this option causes pppd to
# show the password string in the log message.
#show-password

# Use the modem control lines.  On Ultrix, this option implies hardware
# flow control, as for the crtscts option.  (This option is not fully
# implemented.)
modem

# Set the MRU [Maximum Receive Unit] value to <n> for negotiation.  pppd
# will ask the peer to send packets of no more than <n> bytes. The
# minimum MRU value is 128.  The default MRU value is 1500.  A value of
# 296 is recommended for slow links (40 bytes for TCP/IP header + 256
# bytes of data).
#mru 542

# Set the interface netmask to <n>, a 32 bit netmask in "decimal dot"
# notation (e.g. 255.255.255.0).
#netmask 255.255.255.0

# Disables the default behaviour when no local IP address is specified,
# which is to determine (if possible) the local IP address from the
# hostname. With this option, the peer will have to supply the local IP
# address during IPCP negotiation (unless it specified explicitly on the
# command line or in an options file).
#noipdefault

# Enables the "passive" option in the LCP.  With this option, pppd will
# attempt to initiate a connection; if no reply is received from the
# peer, pppd will then just wait passively for a valid LCP packet from
# the peer (instead of exiting, as it does without this option).
#passive

# With this option, pppd will not transmit LCP packets to initiate a
# connection until a valid LCP packet is received from the peer (as for
# the "passive" option with old versions of pppd).
#silent

# Don't request or allow negotiation of any options for LCP and IPCP
# (use default values).
#-all

# Disable Address/Control compression negotiation (use default, i.e.
# address/control field disabled).
#-ac

# Disable asyncmap negotiation (use the default asyncmap, i.e. escape
# all control characters).
#-am

# Don't fork to become a background process (otherwise pppd will do so
# if a serial device is specified).
#-detach

# Disable IP address negotiation (with this option, the remote IP
# address must be specified with an option on the command line or in
# an options file).
#-ip

# Disable IPCP negotiation and IP communication. This option should
# only be required if the peer is buggy and gets confused by requests
# from pppd for IPCP negotiation.
#noip

# Disable magic number negotiation.  With this option, pppd cannot
# detect a looped-back line.
#-mn

# Disable MRU [Maximum Receive Unit] negotiation (use default, i.e.
# 1500).
#-mru

# Disable protocol field compression negotiation (use default, i.e.
# protocol field compression disabled).
#-pc


# Require the peer to authenticate itself using PAP.
#+pap

# Don't agree to authenticate using PAP.
#-pap

# Require the peer to authenticate itself using CHAP [Cryptographic
# Handshake Authentication Protocol] authentication.
#+chap

# Don't agree to authenticate using CHAP.
#-chap

# Disable negotiation of Van Jacobson style IP header compression (use
# default, i.e. no compression).
#-vj

# Increase debugging level (same as -d).  If this option is given, pppd
# will log the contents of all control packets sent or received in a
# readable form.  The packets are logged through syslog with facility
# daemon and level debug. This information can be directed to a file by
# setting up /etc/syslog.conf appropriately (see syslog.conf(5)).  (If
# pppd is compiled with extra debugging enabled, it will log messages
# using facility local2 instead of daemon).
#debug

# Append the domain name <d> to the local host name for authentication
# purposes.  For example, if gethostname() returns the name porsche,
# but the fully qualified domain name is porsche.Quotron.COM, you would
# use the domain option to set the domain name to Quotron.COM.
#domain <d>

# Enable debugging code in the kernel-level PPP driver.  The argument n
# is a number which is the sum of the following values: 1 to enable
# general debug messages, 2 to request that the contents of received
# packets be printed, and 4 to request that the contents of transmitted
# packets be printed.
#kdebug n

# Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer
# requests a smaller value via MRU negotiation, pppd will request that
# the kernel networking code send data packets of no more than n bytes
# through the PPP network interface.
#mtu <n>

# Set the name of the local system for authentication purposes to <n>.
# This is a privileged option. With this option, pppd will use lines in the
# secrets files which have <n> as the second field when looking for a
# secret to use in authenticating the peer. In addition, unless overridden
# with the user option, <n> will be used as the name to send to the peer
# when authenticating the local system to the peer. (Note that pppd does
# not append the domain name to <n>.)
#name <n>

# Enforce the use of the hostname as the name of the local system for
# authentication purposes (overrides the name option).
#usehostname

# Set the assumed name of the remote system for authentication purposes
# to <n>.
#remotename <n>

# Add an entry to this system's ARP [Address Resolution Protocol]
# table with the IP address of the peer and the Ethernet address of this
# system.
proxyarp

# Use the system password database for authenticating the peer using
# PAP. Note: mgetty already provides this option. If this is specified
# then dialin from users using a script under Linux to fire up ppp wont work.
# login

# If this option is given, pppd will send an LCP echo-request frame to the
# peer every n seconds. Normally the peer should respond to the echo-request
# by sending an echo-reply. This option can be used with the
# lcp-echo-failure option to detect that the peer is no longer connected.
lcp-echo-interval 30

# If this option is given, pppd will presume the peer to be dead if n
# LCP echo-requests are sent without receiving a valid LCP echo-reply.
# If this happens, pppd will terminate the connection.  Use of this
# option requires a non-zero value for the lcp-echo-interval parameter.
# This option can be used to enable pppd to terminate after the physical
# connection has been broken (e.g., the modem has hung up) in
# situations where no hardware modem control lines are available.
lcp-echo-failure 4

# Set the LCP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#lcp-restart <n>

# Set the maximum number of LCP terminate-request transmissions to <n>
# (default 3).
#lcp-max-terminate <n>

# Set the maximum number of LCP configure-request transmissions to <n>
# (default 10).
#lcp-max-configure <n>

# Set the maximum number of LCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#lcp-max-failure <n>

# Set the IPCP restart interval (retransmission timeout) to <n>
# seconds (default 3).
#ipcp-restart <n>

# Set the maximum number of IPCP terminate-request transmissions to <n>
# (default 3).
#ipcp-max-terminate <n>

# Set the maximum number of IPCP configure-request transmissions to <n>
# (default 10).
#ipcp-max-configure <n>

# Set the maximum number of IPCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#ipcp-max-failure <n>

# Set the PAP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#pap-restart <n>

# Set the maximum number of PAP authenticate-request transmissions to
# <n> (default 10).
#pap-max-authreq <n>

# Set the maximum time that pppd will wait for the peer to authenticate
# itself with PAP to <n> seconds (0 means no limit).
#pap-timeout <n>

# Set the CHAP restart interval (retransmission timeout for
# challenges) to <n> seconds (default 3).
#chap-restart <n>

# Set the maximum number of CHAP challenge transmissions to <n>
# (default 10).
#chap-max-challenge

# If this option is given, pppd will rechallenge the peer every <n>
# seconds.
#chap-interval <n>

# With this option, pppd will accept the peer's idea of our local IP
# address, even if the local IP address was specified in an option.
#ipcp-accept-local

# With this option, pppd will accept the peer's idea of its (remote) IP
# address, even if the remote IP address was specified in an option.
#ipcp-accept-remote

# Disable the IPXCP and IPX protocols.
# To let pppd pass IPX packets comment this out --- you'll probably also
# want to install ipxripd, and have the Internal IPX Network option enabled
# in your kernel.  /usr/doc/HOWTO/IPX-HOWTO.gz contains more info.
noipx

# Exit once a connection has been made and terminated. This is the default,
# unless the `persist' or `demand' option has been specified.
#nopersist

# Do not exit after a connection is terminated; instead try to reopen
# the connection.
#persist

# Terminate after n consecutive failed connection attempts.
# A value of 0 means no limit. The default value is 10.
#maxfail <n>

# Initiate the link only on demand, i.e. when data traffic is present.
# With this option, the remote IP address must be specified by the user on
# the command line or in an options file.  Pppd will initially configure
# the interface and enable it for IP traffic without connecting to the peer.
# When traffic is available, pppd will connect to the peer and perform
# negotiation, authentication, etc.  When this is completed, pppd will
# commence passing data packets (i.e., IP packets) across the link.
#demand

# Specifies that pppd should disconnect if the link is idle for <n> seconds.
# The link is idle when no data packets (i.e. IP packets) are being sent or
# received.  Note: it is not advisable to use this option with the persist
# option without the demand option.  If the active-filter option is given,
# data packets which are rejected by the specified activity filter also
# count as the link being idle.
#idle <n>

# Specifies how many seconds to wait before re-initiating the link after
# it terminates.  This option only has any effect if the persist or demand
# option is used.  The holdoff period is not applied if the link was
# terminated because it was idle.
#holdoff <n>

# Wait for up n milliseconds after the connect script finishes for a valid
# PPP packet from the peer.  At the end of this time, or when a valid PPP
# packet is received from the peer, pppd will commence negotiation by
# sending its first LCP packet.  The default value is 1000 (1 second).
# This wait period only applies if the connect or pty option is used.
#connect-delay <n>

# Packet filtering: for more information, see pppd(
# Any packets matching the filter expression will be interpreted as link
# activity, and will cause a "demand" connection to be activated, and reset
# the idle connection timer. (idle option)
# The filter expression is akin to that of tcpdump(1)
#active-filter <filter-expression>

# ---<End of File>---

E como vc pode ver, os itens que estão destacados em verde são os que estão descomentados, ou seja, sem o símbolo # no início da linha. Portanto se vc quiser pode deixar deste modo se já não estiver assim também.

Outro arquivo que vc deve olhar é o resolv.conf qe se encontra em /etc/ e que para o Ibest aqui comigo fica assim:

nameserver 200.223.0.84
nameserver 200.202.193.76

Não sei se estes valores mudam de região para região, mas tá aí....


Também veja este dois arquivos chap-secrets e pap-secrets, ambos se encontram em /etc/ppp/ e vc deve colocar no final deles, se já não estiver,  o seguinte:

"fulano@ibest.com.br" * "abcdef"

Onde o nome em vermelho vc deve mudar para o seu nome de usuário do provedor e o nome em verde para a sua senha de acesso do provedor.

Atenção que vc deve digitar exatamente do jeito que está escrito (com as aspas, com o asterisco e etc) só mudando o que falei à pouco.

Por fim lembre-se que vc deverá fazer todas estas alterações descritas aqui como usuário root e não como usuário comum. Caso vc não sabia como virar root dê o comando sudo su em um terminal.

Se vc quiser trabalhar com o gerenciador de arquivos como root, abra o terminal, vire root e digite nautilus aí vc terá oportunidade de editar os arquivos que falei em modo gráfico sem ter de fazê-lo via terminal. Depois de fazer as alterações salve os arquivos e feche tudo.


Há outra coisa, vc fez como falei para a configuração do kppp via o arquivo kppprc?

[Beto]

fiz exatamente como vc falou kppprc
agora esses de verde q vc colocou foi exatamente o q eu coloquei o # antes !
realmente apos q coloquei ele conectou loga na rede mais ñ acessa nada
agora nem uma questão q vc colocou, eu normalmente uso o seguinte
nome de usuario: ibest
senha:ibest
numero:15002442
normalmente uso assim no windows mais observei q vc colocou um mail fulano@ibest.com.br e eu nem tenho mail da ibest
sera isso, pq pelo menos no windows se vc faz uma conexão nome de usuario: ibest, senha:ibest,  numero:15002442
mais obrigado pelo ajuda vou tentar fazer  [/b]

[Beto]

Bom fiz igual a vc, retirei os # novamente dexei igual ao seu,tudo igual ao seu mais nada:
# /etc/ppp/options
#
# Originally created by Jim Knoble <jmknoble@mercury.interpath.net>
# Modified for Debian by alvar Bray <alvar@meiko.co.uk>
# Modified for PPP Server setup by Christoph Lameter <clameter@debian.org>
#
# To quickly see what options are active in this file, use this command:
#   egrep -v '#|^ *$' /etc/ppp/options

# Specify which DNS Servers the incoming Win95 or WinNT Connection should use
# Two Servers can be remotely configured
# ms-dns 192.168.1.1
# ms-dns 192.168.1.2

# Specify which WINS Servers the incoming connection Win95 or WinNT should use
# ms-wins 192.168.1.50
# ms-wins 192.168.1.51

# Run the executable or shell command specified after pppd has
# terminated the link.  This script could, for example, issue commands
# to the modem to cause it to hang up if hardware modem control signals
# were not available.
#disconnect "chat -- \d+++\d\c OK ath0 OK"

# async character map -- 32-bit hex; each bit is a character
# that needs to be escaped for pppd to receive it.  0x00000001
# represents '\x01', and 0x80000000 represents '\x1f'.
asyncmap 0

# Require the peer to authenticate itself before allowing network
# packets to be sent or received.
# Please do not disable this setting. It is expected to be standard in
# future releases of pppd. Use the call option (see manpage) to disable
# authentication for specific peers.
auth

# Use hardware flow control (i.e. RTS/CTS) to control the flow of data
# on the serial port.
crtscts

# Use software flow control (i.e. XON/XOFF) to control the flow of data
# on the serial port.
#xonxoff

# Specifies that certain characters should be escaped on transmission
# (regardless of whether the peer requests them to be escaped with its
# async control character map).  The characters to be escaped are
# specified as a list of hex numbers separated by commas.  Note that
# almost any character can be specified for the escape option, unlike
# the asyncmap option which only allows control characters to be
# specified.  The characters which may not be escaped are those with hex
# values 0x20 - 0x3f or 0x5e.
#escape 11,13,ff

# Don't use the modem control lines.

#local

# Specifies that pppd should use a UUCP-style lock on the serial device
# to ensure exclusive access to the device.
lock

# Don't show the passwords when logging the contents of PAP packets.
# This is the default.
hide-password

# When logging the contents of PAP packets, this option causes pppd to
# show the password string in the log message.
#show-password

# Use the modem control lines.  On Ultrix, this option implies hardware
# flow control, as for the crtscts option.  (This option is not fully
# implemented.)
modem

# Set the MRU [Maximum Receive Unit] value to <n> for negotiation.  pppd
# will ask the peer to send packets of no more than <n> bytes. The
# minimum MRU value is 128.  The default MRU value is 1500.  A value of
# 296 is recommended for slow links (40 bytes for TCP/IP header + 256
# bytes of data).
#mru 542

# Set the interface netmask to <n>, a 32 bit netmask in "decimal dot"
# notation (e.g. 255.255.255.0).
#netmask 255.255.255.0

# Disables the default behaviour when no local IP address is specified,
# which is to determine (if possible) the local IP address from the
# hostname. With this option, the peer will have to supply the local IP
# address during IPCP negotiation (unless it specified explicitly on the
# command line or in an options file).
#noipdefault

# Enables the "passive" option in the LCP.  With this option, pppd will
# attempt to initiate a connection; if no reply is received from the
# peer, pppd will then just wait passively for a valid LCP packet from
# the peer (instead of exiting, as it does without this option).
#passive

# With this option, pppd will not transmit LCP packets to initiate a
# connection until a valid LCP packet is received from the peer (as for
# the "passive" option with old versions of pppd).
#silent

# Don't request or allow negotiation of any options for LCP and IPCP
# (use default values).
#-all

# Disable Address/Control compression negotiation (use default, i.e.
# address/control field disabled).
#-ac

# Disable asyncmap negotiation (use the default asyncmap, i.e. escape
# all control characters).
#-am

# Don't fork to become a background process (otherwise pppd will do so
# if a serial device is specified).
#-detach

# Disable IP address negotiation (with this option, the remote IP
# address must be specified with an option on the command line or in
# an options file).
#-ip

# Disable IPCP negotiation and IP communication. This option should
# only be required if the peer is buggy and gets confused by requests
# from pppd for IPCP negotiation.
#noip

# Disable magic number negotiation.  With this option, pppd cannot
# detect a looped-back line.
#-mn

# Disable MRU [Maximum Receive Unit] negotiation (use default, i.e.
# 1500).
#-mru

# Disable protocol field compression negotiation (use default, i.e.
# protocol field compression disabled).
#-pc


# Require the peer to authenticate itself using PAP.
#+pap

# Don't agree to authenticate using PAP.
#-pap

# Require the peer to authenticate itself using CHAP [Cryptographic
# Handshake Authentication Protocol] authentication.
#+chap

# Don't agree to authenticate using CHAP.
#-chap

# Disable negotiation of Van Jacobson style IP header compression (use
# default, i.e. no compression).
#-vj

# Increase debugging level (same as -d).  If this option is given, pppd
# will log the contents of all control packets sent or received in a
# readable form.  The packets are logged through syslog with facility
# daemon and level debug. This information can be directed to a file by
# setting up /etc/syslog.conf appropriately (see syslog.conf(5)).  (If
# pppd is compiled with extra debugging enabled, it will log messages
# using facility local2 instead of daemon).
#debug

# Append the domain name <d> to the local host name for authentication
# purposes.  For example, if gethostname() returns the name porsche,
# but the fully qualified domain name is porsche.Quotron.COM, you would
# use the domain option to set the domain name to Quotron.COM.
#domain <d>

# Enable debugging code in the kernel-level PPP driver.  The argument n
# is a number which is the sum of the following values: 1 to enable
# general debug messages, 2 to request that the contents of received
# packets be printed, and 4 to request that the contents of transmitted
# packets be printed.
#kdebug n

# Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer
# requests a smaller value via MRU negotiation, pppd will request that
# the kernel networking code send data packets of no more than n bytes
# through the PPP network interface.
#mtu <n>

# Set the name of the local system for authentication purposes to <n>.
# This is a privileged option. With this option, pppd will use lines in the
# secrets files which have <n> as the second field when looking for a
# secret to use in authenticating the peer. In addition, unless overridden
# with the user option, <n> will be used as the name to send to the peer
# when authenticating the local system to the peer. (Note that pppd does
# not append the domain name to <n>.)
#name <n>

# Enforce the use of the hostname as the name of the local system for
# authentication purposes (overrides the name option).
#usehostname

# Set the assumed name of the remote system for authentication purposes
# to <n>.
#remotename <n>

# Add an entry to this system's ARP [Address Resolution Protocol]
# table with the IP address of the peer and the Ethernet address of this
# system.
proxyarp

# Use the system password database for authenticating the peer using
# PAP. Note: mgetty already provides this option. If this is specified
# then dialin from users using a script under Linux to fire up ppp wont work.
# login

# If this option is given, pppd will send an LCP echo-request frame to the
# peer every n seconds. Normally the peer should respond to the echo-request
# by sending an echo-reply. This option can be used with the
# lcp-echo-failure option to detect that the peer is no longer connected.
lcp-echo-interval 30

# If this option is given, pppd will presume the peer to be dead if n
# LCP echo-requests are sent without receiving a valid LCP echo-reply.
# If this happens, pppd will terminate the connection.  Use of this
# option requires a non-zero value for the lcp-echo-interval parameter.
# This option can be used to enable pppd to terminate after the physical
# connection has been broken (e.g., the modem has hung up) in
# situations where no hardware modem control lines are available.
lcp-echo-failure 4

# Set the LCP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#lcp-restart <n>

# Set the maximum number of LCP terminate-request transmissions to <n>
# (default 3).
#lcp-max-terminate <n>

# Set the maximum number of LCP configure-request transmissions to <n>
# (default 10).
#lcp-max-configure <n>

# Set the maximum number of LCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#lcp-max-failure <n>

# Set the IPCP restart interval (retransmission timeout) to <n>
# seconds (default 3).
#ipcp-restart <n>

# Set the maximum number of IPCP terminate-request transmissions to <n>
# (default 3).
#ipcp-max-terminate <n>

# Set the maximum number of IPCP configure-request transmissions to <n>
# (default 10).
#ipcp-max-configure <n>

# Set the maximum number of IPCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#ipcp-max-failure <n>

# Set the PAP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#pap-restart <n>

# Set the maximum number of PAP authenticate-request transmissions to
# <n> (default 10).
#pap-max-authreq <n>

# Set the maximum time that pppd will wait for the peer to authenticate
# itself with PAP to <n> seconds (0 means no limit).
#pap-timeout <n>

# Set the CHAP restart interval (retransmission timeout for
# challenges) to <n> seconds (default 3).
#chap-restart <n>

# Set the maximum number of CHAP challenge transmissions to <n>
# (default 10).
#chap-max-challenge

# If this option is given, pppd will rechallenge the peer every <n>
# seconds.
#chap-interval <n>

# With this option, pppd will accept the peer's idea of our local IP
# address, even if the local IP address was specified in an option.
#ipcp-accept-local

# With this option, pppd will accept the peer's idea of its (remote) IP
# address, even if the remote IP address was specified in an option.
#ipcp-accept-remote

# Disable the IPXCP and IPX protocols.
# To let pppd pass IPX packets comment this out --- you'll probably also
# want to install ipxripd, and have the Internal IPX Network option enabled
# in your kernel.  /usr/doc/HOWTO/IPX-HOWTO.gz contains more info.
noipx

# Exit once a connection has been made and terminated. This is the default,
# unless the `persist' or `demand' option has been specified.
#nopersist

# Do not exit after a connection is terminated; instead try to reopen
# the connection.
#persist

# Terminate after n consecutive failed connection attempts.
# A value of 0 means no limit. The default value is 10.
#maxfail <n>

# Initiate the link only on demand, i.e. when data traffic is present.
# With this option, the remote IP address must be specified by the user on
# the command line or in an options file.  Pppd will initially configure
# the interface and enable it for IP traffic without connecting to the peer.
# When traffic is available, pppd will connect to the peer and perform
# negotiation, authentication, etc.  When this is completed, pppd will
# commence passing data packets (i.e., IP packets) across the link.
#demand

# Specifies that pppd should disconnect if the link is idle for <n> seconds.
# The link is idle when no data packets (i.e. IP packets) are being sent or
# received.  Note: it is not advisable to use this option with the persist
# option without the demand option.  If the active-filter option is given,
# data packets which are rejected by the specified activity filter also
# count as the link being idle.
#idle <n>

# Specifies how many seconds to wait before re-initiating the link after
# it terminates.  This option only has any effect if the persist or demand
# option is used.  The holdoff period is not applied if the link was
# terminated because it was idle.
#holdoff <n>

# Wait for up n milliseconds after the connect script finishes for a valid
# PPP packet from the peer.  At the end of this time, or when a valid PPP
# packet is received from the peer, pppd will commence negotiation by
# sending its first LCP packet.  The default value is 1000 (1 second).
# This wait period only applies if the connect or pty option is used.
#connect-delay <n>

# Packet filtering: for more information, see pppd(Cool
# Any packets matching the filter expression will be interpreted as link
# activity, and will cause a "demand" connection to be activated, and reset
# the idle connection timer. (idle option)
# The filter expression is akin to that of tcpdump(1)
#active-filter <filter-expression>

# ---<End of File>---


voltei lá etc/ppp/options e fiz um teste e coloquei antes do auth o "#" e ai conecta, mais ñ acessa
"# Require the peer to authenticate itself before allowing network
# packets to be sent or received.
# Please do not disable this setting. It is expected to be standard in
# future releases of pppd. Use the call option (see manpage) to disable
# authentication for specific peers.
auth"

interessante q se eu retirar o "#" volta a dar um erro:
o serviço pppd terminou inesperadamente
status saida: 1
veja em man pppd!
para explicação do erro http://developer.kde.org/~kppp/index.html
quando clico em detalhes diz q ñ conseguio autenticar isso quando esta sem o "#" antes do "auth" e diz q ñ  tem explicaçaõ pro erro!
Fui no site citado ai cima diz o seguinte:
"pppd morrido - o sistema remoto é requerido authenticate...
Tanto quanto eu posso dizer há duas causas para este problema:

   * /etc/ppp/options contem a opção do auth. Simplesmente ponha a # caráter do comentário na parte dianteira e tente outra vez.
   * Seu sistema tem já um default route. Têm-no ajustam acima uma rede local? No caso do thise as versões recentes do pppd comportar-se-ão como se o auth tinha sido especificado. Para cancelar este você pode adicionar o noauth aos argumentos do pppd diálogo da instalação no kppp '. Alternativamente você poderia fazer exame para baixo da rede local antes de marcar dentro. Eu seria thankful se alguém poderia fornecer instruções em como combinar pacificamente as duas conexões de rede. "

vei e ai o q faço

[alarcon]

Bom fiz igual a vc, retirei os # novamente dexei igual ao seu,tudo igual ao seu mais nada:
# /etc/ppp/options
#
# Originally created by Jim Knoble <jmknoble@mercury.interpath.net>
# Modified for Debian by alvar Bray <alvar@meiko.co.uk>
# Modified for PPP Server setup by Christoph Lameter <clameter@debian.org>
#
#.....
(

Bom é o seguinte vc disse que não tem um nome de usuário e nem uma senha do provedor Ibest, então acho que isso pode ser a causa do erro aí, talvez na autenticação esteja ocorrendo uma falha. Procure ter um nome válido e uma senha também.

Caso vc já tenha feito isso e continue com problemas, então faça tudo que já  tinha explicado acima e mais isto:

veja se em /etc/ppp/peers/ existe um arquivo chamado de kppp-options se não existir então crie ele aí e dê o seguinte conteúdo para ele:

#noauth

Escreva exatamente como mostrado acima (com o símbolo # também) salve e feche o arquivo.

Depois de criar , caso não exista, e colocar este conteúdo aí, então faça mais isso:

chmod 644 kppp-options

e tente ver se agora funciona o kppp e caso não, reinicie o PC para ver se não é preciso isso.

E caso ainda continue sem funcionar então modifiqueo arquivo options que se encontra em /etc/ppp/ para:

# /etc/ppp/options
#
# Originally created by Jim Knoble <jmknoble@mercury.interpath.net>
# Modified for Debian by alvar Bray <alvar@meiko.co.uk>
# Modified for PPP Server setup by Christoph Lameter <clameter@debian.org>
#
# To quickly see what options are active in this file, use this command:
#   egrep -v '#|^ *$' /etc/ppp/options

# Specify which DNS Servers the incoming Win95 or WinNT Connection should use
# Two Servers can be remotely configured
# ms-dns 192.168.1.1
# ms-dns 192.168.1.2

# Specify which WINS Servers the incoming connection Win95 or WinNT should use
# ms-wins 192.168.1.50
# ms-wins 192.168.1.51

# Run the executable or shell command specified after pppd has
# terminated the link.  This script could, for example, issue commands
# to the modem to cause it to hang up if hardware modem control signals
# were not available.
#disconnect "chat -- \d+++\d\c OK ath0 OK"

# async character map -- 32-bit hex; each bit is a character
# that needs to be escaped for pppd to receive it.  0x00000001
# represents '\x01', and 0x80000000 represents '\x1f'.
asyncmap 0

# Require the peer to authenticate itself before allowing network
# packets to be sent or received.
# Please do not disable this setting. It is expected to be standard in
# future releases of pppd. Use the call option (see manpage) to disable
# authentication for specific peers.
noauth

# Use hardware flow control (i.e. RTS/CTS) to control the flow of data
# on the serial port.
crtscts

# Use software flow control (i.e. XON/XOFF) to control the flow of data
# on the serial port.
#xonxoff

# Specifies that certain characters should be escaped on transmission
# (regardless of whether the peer requests them to be escaped with its
# async control character map).  The characters to be escaped are
# specified as a list of hex numbers separated by commas.  Note that
# almost any character can be specified for the escape option, unlike
# the asyncmap option which only allows control characters to be
# specified.  The characters which may not be escaped are those with hex
# values 0x20 - 0x3f or 0x5e.
#escape 11,13,ff

# Don't use the modem control lines.
#local

# Specifies that pppd should use a UUCP-style lock on the serial device
# to ensure exclusive access to the device.
# lock

# Don't show the passwords when logging the contents of PAP packets.
# This is the default.
hide-password

# When logging the contents of PAP packets, this option causes pppd to
# show the password string in the log message.
#show-password

# Use the modem control lines.  On Ultrix, this option implies hardware
# flow control, as for the crtscts option.  (This option is not fully
# implemented.)
modem

# Set the MRU [Maximum Receive Unit] value to <n> for negotiation.  pppd
# will ask the peer to send packets of no more than <n> bytes. The
# minimum MRU value is 128.  The default MRU value is 1500.  A value of
# 296 is recommended for slow links (40 bytes for TCP/IP header + 256
# bytes of data).
#mru 542

# Set the interface netmask to <n>, a 32 bit netmask in "decimal dot"
# notation (e.g. 255.255.255.0).
#netmask 255.255.255.0

# Disables the default behaviour when no local IP address is specified,
# which is to determine (if possible) the local IP address from the
# hostname. With this option, the peer will have to supply the local IP
# address during IPCP negotiation (unless it specified explicitly on the
# command line or in an options file).
noipdefault

# Enables the "passive" option in the LCP.  With this option, pppd will
# attempt to initiate a connection; if no reply is received from the
# peer, pppd will then just wait passively for a valid LCP packet from
# the peer (instead of exiting, as it does without this option).
passive

# With this option, pppd will not transmit LCP packets to initiate a
# connection until a valid LCP packet is received from the peer (as for
# the "passive" option with old versions of pppd).
#silent

# Don't request or allow negotiation of any options for LCP and IPCP
# (use default values).
#-all

# Disable Address/Control compression negotiation (use default, i.e.
# address/control field disabled).
#-ac

# Disable asyncmap negotiation (use the default asyncmap, i.e. escape
# all control characters).
#-am

# Don't fork to become a background process (otherwise pppd will do so
# if a serial device is specified).
#-detach

# Disable IP address negotiation (with this option, the remote IP
# address must be specified with an option on the command line or in
# an options file).
#-ip

# Disable IPCP negotiation and IP communication. This option should
# only be required if the peer is buggy and gets confused by requests
# from pppd for IPCP negotiation.
#noip

# Disable magic number negotiation.  With this option, pppd cannot
# detect a looped-back line.
#-mn

# Disable MRU [Maximum Receive Unit] negotiation (use default, i.e.
# 1500).
#-mru

# Disable protocol field compression negotiation (use default, i.e.
# protocol field compression disabled).
#-pc

# Require the peer to authenticate itself using PAP.
#+pap

# Don't agree to authenticate using PAP.
#-pap

# Require the peer to authenticate itself using CHAP [Cryptographic
# Handshake Authentication Protocol] authentication.
#+chap

# Don't agree to authenticate using CHAP.
#-chap

# Disable negotiation of Van Jacobson style IP header compression (use
# default, i.e. no compression).
#-vj

# Increase debugging level (same as -d).  If this option is given, pppd
# will log the contents of all control packets sent or received in a
# readable form.  The packets are logged through syslog with facility
# daemon and level debug. This information can be directed to a file by
# setting up /etc/syslog.conf appropriately (see syslog.conf(5)).  (If
# pppd is compiled with extra debugging enabled, it will log messages
# using facility local2 instead of daemon).
#debug

# Append the domain name <d> to the local host name for authentication
# purposes.  For example, if gethostname() returns the name porsche,
# but the fully qualified domain name is porsche.Quotron.COM, you would
# use the domain option to set the domain name to Quotron.COM.
#domain <d>

# Enable debugging code in the kernel-level PPP driver.  The argument n
# is a number which is the sum of the following values: 1 to enable
# general debug messages, 2 to request that the contents of received
# packets be printed, and 4 to request that the contents of transmitted
# packets be printed.
#kdebug n

# Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer
# requests a smaller value via MRU negotiation, pppd will request that
# the kernel networking code send data packets of no more than n bytes
# through the PPP network interface.
#mtu <n>

# Set the name of the local system for authentication purposes to <n>.
# This is a privileged option. With this option, pppd will use lines in the
# secrets files which have <n> as the second field when looking for a
# secret to use in authenticating the peer. In addition, unless overridden
# with the user option, <n> will be used as the name to send to the peer
# when authenticating the local system to the peer. (Note that pppd does
# not append the domain name to <n>.)
#name <n>

# Enforce the use of the hostname as the name of the local system for
# authentication purposes (overrides the name option).
#usehostname

# Set the assumed name of the remote system for authentication purposes
# to <n>.
#remotename <n>

# Add an entry to this system's ARP [Address Resolution Protocol]
# table with the IP address of the peer and the Ethernet address of this
# system.
proxyarp

# Use the system password database for authenticating the peer using
# PAP. Note: mgetty already provides this option. If this is specified
# then dialin from users using a script under Linux to fire up ppp wont work.
# login

# If this option is given, pppd will send an LCP echo-request frame to the
# peer every n seconds. Normally the peer should respond to the echo-request
# by sending an echo-reply. This option can be used with the
# lcp-echo-failure option to detect that the peer is no longer connected.
lcp-echo-interval 30

# If this option is given, pppd will presume the peer to be dead if n
# LCP echo-requests are sent without receiving a valid LCP echo-reply.
# If this happens, pppd will terminate the connection.  Use of this
# option requires a non-zero value for the lcp-echo-interval parameter.
# This option can be used to enable pppd to terminate after the physical
# connection has been broken (e.g., the modem has hung up) in
# situations where no hardware modem control lines are available.
lcp-echo-failure 4

# Set the LCP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#lcp-restart <n>

# Set the maximum number of LCP terminate-request transmissions to <n>
# (default 3).
#lcp-max-terminate <n>

# Set the maximum number of LCP configure-request transmissions to <n>
# (default 10).
#lcp-max-configure <n>

# Set the maximum number of LCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#lcp-max-failure <n>

# Set the IPCP restart interval (retransmission timeout) to <n>
# seconds (default 3).
#ipcp-restart <n>

# Set the maximum number of IPCP terminate-request transmissions to <n>
# (default 3).
#ipcp-max-terminate <n>

# Set the maximum number of IPCP configure-request transmissions to <n>
# (default 10).
#ipcp-max-configure <n>

# Set the maximum number of IPCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#ipcp-max-failure <n>

# Set the PAP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#pap-restart <n>

# Set the maximum number of PAP authenticate-request transmissions to
# <n> (default 10).
pap-max-authreq 1000

# Set the maximum time that pppd will wait for the peer to authenticate
# itself with PAP to <n> seconds (0 means no limit).
#pap-timeout <n>

# Set the CHAP restart interval (retransmission timeout for
# challenges) to <n> seconds (default 3).
#chap-restart <n>

# Set the maximum number of CHAP challenge transmissions to <n>
# (default 10).
#chap-max-challenge

# If this option is given, pppd will rechallenge the peer every <n>
# seconds.
#chap-interval <n>

# With this option, pppd will accept the peer's idea of our local IP
# address, even if the local IP address was specified in an option.
#ipcp-accept-local

# With this option, pppd will accept the peer's idea of its (remote) IP
# address, even if the remote IP address was specified in an option.
#ipcp-accept-remote

# Disable the IPXCP and IPX protocols.
# To let pppd pass IPX packets comment this out --- you'll probably also
# want to install ipxripd, and have the Internal IPX Network option enabled
# in your kernel.  /usr/doc/HOWTO/IPX-HOWTO.gz contains more info.
noipx

# Exit once a connection has been made and terminated. This is the default,
# unless the `persist' or `demand' option has been specified.
#nopersist

# Do not exit after a connection is terminated; instead try to reopen
# the connection.
#persist

# Terminate after n consecutive failed connection attempts.
# A value of 0 means no limit. The default value is 10.
maxfail 0

# Initiate the link only on demand, i.e. when data traffic is present.
# With this option, the remote IP address must be specified by the user on
# the command line or in an options file.  Pppd will initially configure
# the interface and enable it for IP traffic without connecting to the peer.
# When traffic is available, pppd will connect to the peer and perform
# negotiation, authentication, etc.  When this is completed, pppd will
# commence passing data packets (i.e., IP packets) across the link.
#demand

# Specifies that pppd should disconnect if the link is idle for <n> seconds.
# The link is idle when no data packets (i.e. IP packets) are being sent or
# received.  Note: it is not advisable to use this option with the persist
# option without the demand option.  If the active-filter option is given,
# data packets which are rejected by the specified activity filter also
# count as the link being idle.
#idle <n>

# Specifies how many seconds to wait before re-initiating the link after
# it terminates.  This option only has any effect if the persist or demand
# option is used.  The holdoff period is not applied if the link was
# terminated because it was idle.
#holdoff <n>

# Wait for up n milliseconds after the connect script finishes for a valid
# PPP packet from the peer.  At the end of this time, or when a valid PPP
# packet is received from the peer, pppd will commence negotiation by
# sending its first LCP packet.  The default value is 1000 (1 second).
# This wait period only applies if the connect or pty option is used.
#connect-delay <n>

# ---<End of File>---