PPPOE AJATO

Pessoal,

to com um problema. Aqui em casa nao consigo conectar meu CABLE MODEM da Ajato na Inet (SO -> RH9) de jeito nenhum...sempre vem a msg TERMINATED...

Bem, ja fiz de tudo, entao, iniciei novamente em modo DEBUG e lhes mostro o log gerado. Qualquer luz, agradeco de coracao.

Pelas ultimas linhas do log parece que estah havendo um erro de comunicacao, ele tah enviando pacotes a um destino invalido (DestAddr ff:ff:ff:ff:ff:ff), e como obviamente nao ha retorno, dah o problema. Quanto a parte fisica, eu estou nesse momento no Windows, eh a mesma maquina, e tah tudo funcionando aqui 8-(...bem lah vai...

Realmente nao sei como resolver isso... e me desculpem por esta CARTA...

======= INICIO DO LOG =========
---------------------------------------------
* The following section contains information about your system
Fri Oct 17 17:08:43 BRST 2003
Output of uname -a
Linux home 2.4.20-Home0810200303 #14 Wed Oct 8 18:31:51 BRT 2003 i686
athlon i386 GNU/Linux
---------------------------------------------
* The following section contains information about your network
* interfaces. The one you chose for PPPoE should contain the words:
* ´UP´ and ´RUNNING´. If it does not, you probably have an Ethernet
* driver problem.
Output of ifconfig -a
eth0 Link encap:Ethernet HWaddr MI:NH:A_<IMG SRC="images/forum/icons/icon_razz.gif">L:AC:A0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x2f00

eth1 Link encap:Ethernet HWaddr MI:NH:A_<IMG SRC="images/forum/icons/icon_razz.gif">L:AC:A1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:96 (96.0 b)
Interrupt:5 Base address:0x220

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

---------------------------------------------
* The following section contains information about kernel modules
* If the module for your Ethernet card is &acute;tulip&acute;, you might
* want to look for an updated version at http://www.scyld.com
Output of lsmod
Module Size Used by Not tainted
ppp_synctty 7744 0 (unused)
ppp_async 9344 0
ppp_generic 20892 0 [ppp_synctty ppp_async]
slhc 6660 0 [ppp_generic]
autofs 12948 0 (autoclean) (unused)
3c509 13268 1
8139too 18440 0 (unused)
mii 3960 0 [8139too]
nls_iso8859-1 3484 1 (autoclean)
ntfs 58304 1 (autoclean)
keybdev 2912 0 (unused)
mousedev 5428 0 (unused)
hid 15912 0 (unused)
input 5824 0 [keybdev mousedev hid]
usb-uhci 25868 0 (unused)
usbcore 76896 1 [hid usb-uhci]
ext3 69984 2
jbd 51220 2 [ext3]
---------------------------------------------
* The following section lists your routing table.
* If you have an entry which starts with &acute;0.0.0.0&acute;, you probably
* have defined a default route and gateway, and pppd will
* not create a default route using your ISP. Try getting
* rid of this route.
Output of netstat -n -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface
169.254.0.0 0.0.0.0 255.255.0.0 U 0
0 0 lo
127.0.0.0 0.0.0.0 255.0.0.0 U 0
0 0 lo
---------------------------------------------
Contents of /etc/resolv.conf
* The following section lists DNS setup.
* If you can browse by IP address, but not name, suspect
* a DNS problem.
nameserver xxx.xxx.xxx.x (jah conferi, estao certos...)
nameserver xxx.xxx.xxx.x
---------------------------------------------
* The following section lists /etc/ppp/options.
* You should have NOTHING in that file.
Contents of /etc/ppp/options
---------------------------------------------
* The following section identifies your Ethernet interface
* and user name. Some ISP&acute;s need &acute;username&acute;; others
* need &acute;username@i...&acute;. Try both
ETH=eth1; USER=meu_user@a... (tb estah correto...e a senha tb)
---------------------------------------------
* The following section shows the pppd command we will invoke
pppd invocation
/usr/bin/setsid /usr/sbin/pppd pty &acute;/usr/sbin/pppoe -
p /var/run/pppoe.conf-adsl.pid.pppoe -I eth1 -T 80 -U -m 1412 &acute;
noipdefault noauth default-asyncmap defaultroute hide-password
nodetach mtu 1492 mru 1492 noaccomp noccp nobsdcomp nodeflate
nopcomp novj novjccomp user meu_user@a... lcp-echo-interval 20
lcp-echo-failure 3 debug
---------------------------------------------
using channel 2
Using interface ppp0
Connect: ppp0 <--> /dev/pts/0
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5ae1a383>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5ae1a383>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5ae1a383>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5ae1a383>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5ae1a383>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5ae1a383>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5ae1a383>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5ae1a383>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5ae1a383>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x5ae1a383>]
LCP: timeout sending Config-Requests
Connection terminated.
Waiting for 1 child processes...
script /usr/sbin/pppoe -p /var/run/pppoe.conf-adsl.pid.pppoe -I
eth1 -T 80 -U -m 1412 -D /tmp/pppoe-debug-945/pppoe-debug.txt-0,
pid 1003
pppoe: Timeout waiting for PADO packets
Script /usr/sbin/pppoe -p /var/run/pppoe.conf-adsl.pid.pppoe -I eth1 -
T 80 -U -m 1412 -D /tmp/pppoe-debug-945/pppoe-debug.txt-0
finished (pid 1003), status = 0x1
---------------------------------------------
* The following section is an extract from your log.
* Look for error messages from pppd, such as
* a lack of kernel support for PPP, authentication failure
* etc.
Extract from /var/log/messages
Oct 17 16:51:36 home pppd[804]: pppd 2.4.1 started by root, uid 0
Oct 17 16:51:36 home pppd[804]: Using interface ppp0
Oct 17 16:51:36 home pppd[804]: Connect: ppp0 <--> /dev/pts/0
Oct 17 16:51:36 home /etc/hotplug/net.agent: assuming ppp0 is already
up
Oct 17 16:52:07 home pppd[804]: LCP: timeout sending Config-Requests
Oct 17 16:52:07 home pppd[804]: Connection terminated.
Oct 17 16:52:11 home pppoe[805]: Timeout waiting for PADO packets
Oct 17 16:52:11 home pppd[804]: Exit.
Oct 17 17:07:50 home pppd[758]: pppd 2.4.1 started by root, uid 0
Oct 17 17:07:50 home pppd[758]: Using interface ppp0
Oct 17 17:07:50 home pppd[758]: Connect: ppp0 <--> /dev/pts/0
Oct 17 17:08:22 home pppd[758]: LCP: timeout sending Config-Requests
Oct 17 17:08:22 home pppd[758]: Connection terminated.
Oct 17 17:08:26 home pppoe[759]: Timeout waiting for PADO packets
Oct 17 17:08:26 home pppd[758]: Exit.
Oct 17 17:08:43 home pppd[1002]: pppd 2.4.1 started by root, uid 0
Oct 17 17:08:43 home pppd[1002]: Using interface ppp0
Oct 17 17:08:43 home pppd[1002]: Connect: ppp0 <--> /dev/pts/0
Oct 17 17:09:14 home pppd[1002]: LCP: timeout sending Config-Requests
Oct 17 17:09:14 home pppd[1002]: Connection terminated.
Oct 17 17:09:18 home pppoe[1003]: Timeout waiting for PADO packets
Oct 17 17:09:18 home pppd[1002]: Exit.
Fri Oct 17 17:09:19 BRST 2003
---------------------------------------------
* The following section is a dump of the packets
* sent and received by rp-pppoe. If you don&acute;t see
* any output, it&acute;s an Ethernet driver problem. If you only
* see three PADI packets and nothing else, check your cables
* and modem. Make sure the modem lights flash when you try
* to connect. Check that your Ethernet card is in
* half-duplex, 10Mb/s mode. If all else fails,
* try using pppoe-sniff.
rp-pppoe debugging dump
rp-pppoe-3.5
17:08:43.610 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr MI:NH:A_<IMG SRC="images/forum/icons/icon_razz.gif">L:AC:A1 DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 eb 03 00 00 ............

17:08:48.607 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr MI:NH:A_<IMG SRC="images/forum/icons/icon_razz.gif">L:AC:A1 DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 eb 03 00 00 ............

17:08:58.607 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr MI:NH:A_<IMG SRC="images/forum/icons/icon_razz.gif">L:AC:A1 DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 eb 03 00 00 ............
======= FIM DO LOG =========


De novo, agradeco qualquer ajuda!
[]s
Adriano!

posta o teu pppoe.conf ai, blz?

OK, como pedido...to postando o pppoe.conf e meu ifcfg-eth1 tb...

======INICIO DE 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=&acute;eth1&acute;

# 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 protected]
USER=&acute;[email protected]&acute;

# 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=SPECIFY

# 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=no

DNS1=xxx.xxx.xxx.x
DNS2=xxx.xxx.xxx.x

# Make the PPPoE connection your default route. Set to
# DEFAULTROUTE=no if you don&acute;t want this.
DEFAULTROUTE=yes

### ONLY TOUCH THE FOLLOWING SETTINGS IF YOU&acute;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&acute;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&acute;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=NONE

# 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&acute;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&acute;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

======FIM DE PPPOE.CONF========

======INICIO DE IFCFG-ETH1========
DEVICE=eth1
BOOTPROTO=dhcp
ONBOOT=no
NAME=3Com
======FIM DE IFCFG-ETH1========

...No RH9 ele inicializa a rede se o arquivo /etc/sysconfig/network for setado para yes. Ele inicializa as placas:

======INICIO DE NETWORK========
NETWORKING=yes
HOSTNAME=Home
======FIM DE NETWORK========

Bem, de novo, agradeço qualquer luz...tava la ateh agora tentando fazer funcionar...


[]s
Adriano!

Cara,
1 Como é que está a configuração do ip da sua placa eth1?
2) Por que você não setou o ip do seu dns?

Na verdade, os MACs, username e os servidores DNS estao todos setados. O que fiz foi ocultar esses valores aqui por motivo de seguranca...

Bem, ainda estou com o problema, tava navegando e vi um kra que resolveu isso usando o dhcpcd...baixei, instalei, configurei como o kra falou, &acute;but nothing...&acute;...continuo com o problema.

Quem puder ajudar...eu tb to atras e resolvendo isso, posto aqui!


[]s
Adriano!

eu uso ajato no meu cl8, a config é fácil, igual a do red hat, mas já tive problemas com red hat tbm, enquanto o cl conectava e navegava o meu rh não...

eu vou explicar como eu fiz:

* setei um ip qualquer só pra levantar a eth0, pq o pppoe usa a ppp0, que é virtual e criada após a discagem bem sucedida.
* configurei o adsl-setup, tudo ok.

mas tiveram dois detalhes fundamentais pro pppoe funcionar:

eu baixei a versão 3.5.1 , que realmente funciona e desinstalei o pacote do linuxconf-pppoe , pq ele tava atrapalhando, depois disso passou a conectar que foi uma beleza!

da uma olhada, no meu caso era isso...

falow!

De fato,

eu jah havia encontrado esta solucao na Inet tb. Setar um IP qualquer pra eth1 (no meu caso) nao adiantou, e a versao que eu tenho do pppoe eh a do site da Roaring Penguim, que eh a 3.5.1 mesmo...

To na mesma...rs...soh faltava eu ter que reinst o linux por causa disso...

Bem, ainda estou com o problema, e como dito antes, se eu resolver, posto a solucao aqui.


[]s e agradeço a atençao de vcs!
Adriano!

putz...ninguem tem uma ideia nova?!

to ferrado aqui...


[]s
Adriano!

Oi pessoal!

Continuo procurando como resolver este problema. Acho que tenho novidade. Uma coisa que nunca vi acontecer, e que está acontecendo desta vez é que a NIC está levantando em half-duplex. Vejam a saída de meu adsl-start:

========
eth1: Setting 3c5x9/3c5x9B half-duplex mode if_port: 0, sw_info: 1321
................TIMED OUT
/usr/sbin/adsl-start: line 191: 549 Terminated $CONNECT "$@" >/dev/null 2>&1
========

Isso não acontecia quando eu conseguia conectar. Logo que a msg de eth1 é exibida, ela é tb levantada e o led de atividade do Cable Modem acende.

Bem, fica agora também a pergunta de como posso setar a NIC pra iniciar em modo full-duplex!

[]s ( e continuo a procurar...)
Adriano!

Opa turma!

Continuando o épico...reisntalei o RH e nada!

Putz grila! Seguinte: Algém pode me dar uma luz???

A única diferença das inst. anteriores, onde o RH9 se conectava sem problemas, é que agora meu PC está com duas placas de rede, sendo a 3COM a eth1, que é onde está o CableMODEM.

Meus caros...agora nem sei o que faço mais...


[]s
Adriano!

Problema resolvido.

Foi só passar o link para eth0.

Não sei porque, mas assim funciona.

Qualquer esclarecimento extra, dou pelo email
blackmorejr / arroba \ hotmail ponto com


[]s
Adriano!