Modem en Ubuntu
AnimAlf
Qué puedo hacer si tras realizar la conexión por medio de
Sistema -> Administración -> Red -> Conexión por Modem
sólo consiguo una conexión, a los 3 minutos se corta la conexion y
luego cuesta mucho conseguir la conexion de nuevo
En la salida de /var/log/messages me da lo siguiente:
Apr 21 16:48:41 ubuntu gconfd (root-8770): Finalizando
Apr 21 16:48:41 ubuntu pppd[8894]: Using interface ppp0
Apr 21 16:48:41 ubuntu pppd[8894]: Connect: ppp0 <--> /dev/ttyS0
Apr 21 16:48:43 ubuntu pppd[8894]: PAP authentication succeeded
Apr 21 16:48:43 ubuntu kernel: [ 715.669379] PPP BSD Compression
module registered
Apr 21 16:48:43 ubuntu kernel: [ 715.764948] PPP Deflate Compression
module registered
Apr 21 16:48:51 ubuntu pppd[8894]: local IP address 81.*.*.*
Apr 21 16:48:51 ubuntu pppd[8894]: remote IP address 81.*.*.*
Apr 21 16:48:51 ubuntu pppd[8894]: primary DNS address 80.58.32.33
Apr 21 16:48:51 ubuntu pppd[8894]: secondary DNS address 80.58.0.97
Apr 21 16:49:13 ubuntu pppd[8894]: LCP: Rcvd Code-Reject for code 9,
id 1
Apr 21 16:49:43 ubuntu pppd[8894]: LCP: Rcvd Code-Reject for code 9,
id 2
Apr 21 16:50:13 ubuntu pppd[8894]: LCP: Rcvd Code-Reject for code 9,
id 3
Apr 21 16:50:43 ubuntu pppd[8894]: No response to 4 echo-requests
Apr 21 16:50:43 ubuntu pppd[8894]: Serial link appears to be
disconnected.
Apr 21 16:50:43 ubuntu pppd[8894]: Connect time 1.9 minutes.
Apr 21 16:50:43 ubuntu pppd[8894]: Sent 12243 bytes, received 71507
bytes.
Apr 21 16:50:43 ubuntu pppd[8894]: Connection terminated.
Apr 21 16:50:43 ubuntu pppd[8894]: Hangup (SIGHUP)
Apr 21 16:50:44 ubuntu chat[9090]: timeout set to 60 seconds
Apr 21 16:50:44 ubuntu chat[9090]: abort on (ERROR)
Apr 21 16:50:44 ubuntu chat[9090]: abort on (BUSY)
Apr 21 16:50:44 ubuntu chat[9090]: abort on (VOICE)
Apr 21 16:50:44 ubuntu chat[9090]: abort on (NO CARRIER)
Apr 21 16:50:44 ubuntu chat[9090]: abort on (NO DIALTONE)
Apr 21 16:50:44 ubuntu chat[9090]: abort on (NO DIAL TONE)
Apr 21 16:50:44 ubuntu chat[9090]: abort on (NO ANSWER)
Apr 21 16:50:44 ubuntu chat[9090]: send (ATZ^M)
Apr 21 16:50:45 ubuntu chat[9090]: send (AT&FH0L1^M)
Apr 21 16:50:45 ubuntu chat[9090]: expect (OK)
Apr 21 16:50:45 ubuntu chat[9090]: ATZ^MAT&FH^M
Apr 21 16:50:45 ubuntu chat[9090]: OK
Apr 21 16:50:45 ubuntu chat[9090]: -- got it
Apr 21 16:50:45 ubuntu chat[9090]: send (ATDP*99#^M)
Apr 21 16:50:45 ubuntu chat[9090]: timeout set to 75 seconds
Apr 21 16:50:45 ubuntu chat[9090]: expect (CONNECT)
Apr 21 16:50:45 ubuntu chat[9090]: ^M
Apr 21 16:50:55 ubuntu chat[9090]: ATDP*99#^M^M
Apr 21 16:50:55 ubuntu chat[9090]: BUSY
Apr 21 16:50:55 ubuntu chat[9090]: -- failed
Apr 21 16:50:55 ubuntu chat[9090]: Failed (BUSY)
¿Podéis orientarme?
Gracias
atm
Pués a mí me parece que es el módem. Parece ser un modem serial
externo pero que le falta algo. Un módem que puede funcionar con
software de Bill Gates.
Tal vez necesite driver y exista driver.
Mira ver si el chip es Conexant, si lo es para que vaya bien tendrá
que ser: RC56D, SMARTSCM, SMARTCF y si no lo es, tienes un modem win, en
lugar de un modem lin.
En busca de Google "modem linux" encontrarás drivers, si los hay.
Saludos.
z1rr...@gmail.com
El modem es:
D-Link WEBCRUISER DRM-560EL 56000bps Data/Fax/Voice (tiene para
enchufar en puerto COM).
Un Saludo.
AnimAlf
> Tal vez necesite driver y exista driver.
El genérico lo acepta, miraré estos datos. Se trata de una máquina de
un tercero. Estoy muy oxidado en este tema. Recuerdo vagamente, bueno
lo cierto es que no recuerdo nada de la conexión por módem en Linux
hoy por hoy, con los sistemas actuales, personalmente las últimas
veces no me he tenido que preocupar por el hard (con todo el hard
X'D). ... je je je, con lo que me recuerdo que no tengo cabeza para
recordar 0:-))
Si os habéis encontrado en una situación similar ... :)) comentármelo
pls
tnks
AnimAlf
> D-Link WEBCRUISER DRM-560EL 56000bps Data/Fax/Voice (tiene para
> enchufar en puerto COM).
>
Mola, acabo de escribir el mensaje y ya veo que no hace falta
contactar ;-))
Gonzalo Pérez de Olaguer Córdoba
el Mon, 21 Apr 2008 22:18:42 -0700 (PDT) escribiste:
Por aquí está el fallo. Estaría bien obtener más info de esto. Si no
tienes activada la opción `debug' en la config de pppd, actívala
y prueba de nuevo. Te saldrá info más detallada de lo que está pasando.
--
Gonzalo Pérez de Olaguer Córdoba <gp...@iies.es>
PGP key 2861C704 --- F206 5671 6789 425D 111C 1302 214F 1934 2861 C704
z1rr...@gmail.com
wrote:
> Hola AnimAlf <Anim...@users.sourceforge.net>
> PGP key 2861C704 --- F206 5671 6789 425D 111C 1302 214F 1934 2861 C704
Como activo la opción degug en la configuración de pppd?
Un saludo y gracias por todas las respuestas. Aver si logramos
solucionarlo.
bytes
Mano
> Como activo la opción degug en la configuración de pppd?
Añadiendo una linea que pona debug en el archivo /etc/ppp/options, aunque
la ubicación del archivo pueda cambiar un poco dependiendo de tu
distribución.
Saludos. Mano
linuxero
En Debian la línea ya está puesta, solamente hay que quitarle la almohadilla
que tiene en el principio, todo ello hecho como root, ya que de lo
contrario no se deja modificar el fichero.
atm
He dado un repaso por Google y creo que tiene un chip de lo peor para
Linux.
Lo más importante de un modem es el chip o chipset, que parece ser
para este modem es el chip: Rockwell RCVDL56ACF/SP,
en las especificaciones técnicas este modem funciona en Windows 95/98,
2000 y NU4.0, pero seguro que no funciona por linux ni XP.
Saludos.
z1rr...@gmail.com
El modem si que funciona en XP, lo que pasa que en linux me consigo
conectar pero a los 3 minutos o 4 se desconecta.
Saludos.
z1rr...@gmail.com
root@ubuntu:/home/ubuntu# date
dom abr 27 16:25:46 UTC 2008
root@ubuntu:/home/ubuntu# tail -f /var/log/messages
Apr 27 16:25:44 ubuntu chat[8809]: expect (OK)
Apr 27 16:25:44 ubuntu chat[8809]: ATZ^MAT&FH^M
Apr 27 16:25:44 ubuntu chat[8809]: OK
Apr 27 16:25:44 ubuntu chat[8809]: -- got it
Apr 27 16:25:44 ubuntu chat[8809]: send (ATDP*99#^M)
Apr 27 16:25:44 ubuntu chat[8809]: timeout set to 75 seconds
Apr 27 16:25:44 ubuntu chat[8809]: expect (CONNECT)
Apr 27 16:25:44 ubuntu chat[8809]: ^M
Apr 27 16:25:57 ubuntu kernel: [ 535.810976] eth0: link down
Apr 27 16:25:57 ubuntu kernel: [ 535.811004] ADDRCONF(NETDEV_UP):
eth0: link is not ready
Apr 27 16:26:17 ubuntu chat[8809]: ATDP*99#^M^M
Apr 27 16:26:17 ubuntu chat[8809]: CONNECT
Apr 27 16:26:17 ubuntu chat[8809]: -- got it
Apr 27 16:26:17 ubuntu pppd[8796]: Serial connection established.
Apr 27 16:26:17 ubuntu pppd[8796]: Using interface ppp0
Apr 27 16:26:17 ubuntu pppd[8796]: Connect: ppp0 <--> /dev/ttyS0
Apr 27 16:26:18 ubuntu pppd[8796]: PAP authentication succeeded
Apr 27 16:26:26 ubuntu pppd[8796]: local IP address 81.*.*.*
Apr 27 16:26:26 ubuntu pppd[8796]: remote IP address 81.*.*.*
Apr 27 16:26:26 ubuntu pppd[8796]: primary DNS address 80.58.32.33
Apr 27 16:26:26 ubuntu pppd[8796]: secondary DNS address 80.58.0.97
Apr 27 16:26:52 ubuntu gconfd (root-8727): El servidor GConf no está
en uso, cerrándolo.
Apr 27 16:26:52 ubuntu gconfd (root-8727): Finalizando
Apr 27 16:28:18 ubuntu pppd[8796]: No response to 4 echo-requests
Apr 27 16:28:18 ubuntu pppd[8796]: Serial link appears to be
disconnected.
Apr 27 16:28:18 ubuntu pppd[8796]: Connect time 1.9 minutes.
Apr 27 16:28:18 ubuntu pppd[8796]: Sent 24108 bytes, received 56090
bytes.
Apr 27 16:28:18 ubuntu pppd[8796]: Connection terminated.
Apr 27 16:28:19 ubuntu pppd[8796]: Exit.
root@ubuntu:/home/ubuntu# date
dom abr 27 16:28:34 UTC 2008
root@ubuntu:/home/ubuntu# cat /etc/ppp/options|grep ^debug
debug #opcion debug activada
root@ubuntu:/home/ubuntu#
z1rr0...@gmail.com ha escrito:
> On 27 abr, 10:57, atm <a...@nospam.com> wrote:
> > z1rr0...@gmail.com wrote:
> > > On 23 abr, 22:41, atm <a...@nospam.com> wrote:
> >
> > >>AnimAlf wrote:
> >
> > >>>Hola
> >
> > >>>Qu� puedo hacer si tras realizar la conexi�n por medio de
> > >>>Sistema -> Administraci�n -> Red -> Conexi�n por Modem
> >
> > >>>s�lo consiguo una conexi�n, a los 3 minutos se corta la conexion y
> > >>>�Pod�is orientarme?
> > >>>Gracias
> >
> > >> Pu�s a m� me parece que es el m�dem. Parece ser un modem serial
> > >>externo pero que le falta algo. Un m�dem que puede funcionar con
> > >>software de Bill Gates.
> >
> > >> Tal vez necesite driver y exista driver.
> >
> > >> Mira ver si el chip es Conexant, si lo es para que vaya bien tendr�
> > >>que ser: RC56D, SMARTSCM, SMARTCF y si no lo es, tienes un modem win, en
> > >>lugar de un modem lin.
> >
> > >> En busca de Google "modem linux" encontrar�s drivers, si los hay.
> >
> > >>Saludos.
> >
> > > El modem es:
> > > D-Link WEBCRUISER DRM-560EL 56000bps Data/Fax/Voice (tiene para
> > > enchufar en puerto COM).
> >
> > > Un Saludo.
> >
> > He dado un repaso por Google y creo que tiene un chip de lo peor para
> > Linux.
> >
> > Lo m�s importante de un modem es el chip o chipset, que parece ser
> > para este modem es el chip: Rockwell RCVDL56ACF/SP,
> > en las especificaciones t�cnicas este modem funciona en Windows 95/98,
Gonzalo Pérez de Olaguer Córdoba
el Sun, 27 Apr 2008 07:37:13 -0700 (PDT) escribiste:
> Bien aqui puse la opción debug y capture los logs, aqui se lo dejo:
>
> root@ubuntu:/home/ubuntu# tail -f /var/log/messages
> Apr 27 16:25:44 ubuntu chat[8809]: expect (OK)
> Apr 27 16:25:44 ubuntu chat[8809]: ATZ^MAT&FH^M
> Apr 27 16:25:44 ubuntu chat[8809]: OK
> Apr 27 16:25:44 ubuntu chat[8809]: -- got it
> Apr 27 16:25:44 ubuntu chat[8809]: send (ATDP*99#^M)
> Apr 27 16:25:44 ubuntu chat[8809]: timeout set to 75 seconds
> Apr 27 16:25:44 ubuntu chat[8809]: expect (CONNECT)
> Apr 27 16:25:44 ubuntu chat[8809]: ^M
> Apr 27 16:26:17 ubuntu chat[8809]: ATDP*99#^M^M
> Apr 27 16:26:17 ubuntu chat[8809]: CONNECT
> Apr 27 16:26:17 ubuntu chat[8809]: -- got it
> Apr 27 16:26:17 ubuntu pppd[8796]: Serial connection established.
> Apr 27 16:26:17 ubuntu pppd[8796]: Using interface ppp0
> Apr 27 16:26:17 ubuntu pppd[8796]: Connect: ppp0 <--> /dev/ttyS0
> Apr 27 16:26:18 ubuntu pppd[8796]: PAP authentication succeeded
> Apr 27 16:26:26 ubuntu pppd[8796]: local IP address 81.*.*.*
> Apr 27 16:26:26 ubuntu pppd[8796]: remote IP address 81.*.*.*
> Apr 27 16:26:26 ubuntu pppd[8796]: primary DNS address 80.58.32.33
> Apr 27 16:26:26 ubuntu pppd[8796]: secondary DNS address 80.58.0.97
Aquí hay dos minutos de tiempo durante los cuales se interrumpe
la comunicación, y no hay info al respecto.
> Apr 27 16:28:18 ubuntu pppd[8796]: No response to 4 echo-requests
> Apr 27 16:28:18 ubuntu pppd[8796]: Serial link appears to be
> disconnected.
> Apr 27 16:28:18 ubuntu pppd[8796]: Connect time 1.9 minutes.
> Apr 27 16:28:18 ubuntu pppd[8796]: Sent 24108 bytes, received 56090
> bytes.
> Apr 27 16:28:18 ubuntu pppd[8796]: Connection terminated.
> Apr 27 16:28:19 ubuntu pppd[8796]: Exit.
Pues sale lo mismo que con la opción debug desactivada, ¿no? Hace años
que no uso pppd, pero recuerdo que con la opción debug activada salía
bastante más info de la que aparece ahí.
El programa pppd lee varios ficheros de configuración, dependiendo de
cómo se ejecute. Según pppd(8) lee /etc/pppd/options, ~/.ppprc,
/etc/pppd/options.ttyS0 y /etc/pppd/peers/<name> (si se llama con
la opción call <name>).
Puedes verificar si se está desactivando la opción debug en algún
otro fichero así (ejecútalo como root):
grep -ri '^[^#]*debug' /etc/pppd
También puedes probar a ver si obtienes más info así:
grep pppd /var/log/syslog
OJO: yo uso debian, y desconozco en qué medida ubuntu será diferente,
pero en Debian /var/log/syslog contiene más info que /var/log/messages
Buscando en google veo que en ubuntu forums hay alguien que dice
que ese modem le funciona correctamente. Si es así, el problema
podría estar en las opciones que tienes configuradas, pero sin más info
de lo que pasa es difícil hacer adivinanzas.
La lista concreta de opciones utilizadas la puedes obtener añadiendo
la opción dump a /etc/pppd/options.
Ya puestos, también podrías activar la opción 'kdebug 7'.
--
Gonzalo Pérez de Olaguer Córdoba <gp...@iies.es>
Gonzalo Pérez de Olaguer Córdoba
el Sun, 27 Apr 2008 20:41:00 +0200 escribiste:
Perdón, en el mensaje anterior me he colado: en todos los
sitios donde dice /etc/pppd debe decir /etc/ppp
linuxero
se soluciona. Entrando como root en /etc/ppp/ edita el fichero options, y
la línea debug quita la almohadilla, y puestos al asunto como te dice
Gonzalo quita también la almohadilla al kdebug n, a ver que sucede.
z1rr...@gmail.com wrote:
>> > >>>Qu? puedo hacer si tras realizar la conexi?n por medio de
>> > >>>Sistema -> Administraci?n -> Red -> Conexi?n por Modem
>> >
>> > >>>s?lo consiguo una conexi?n, a los 3 minutos se corta la conexion y
>> > >>>?Pod?is orientarme?
>> > >>>Gracias
>> >
>> > >> Pu?s a m? me parece que es el m?dem. Parece ser un modem serial
>> > >>externo pero que le falta algo. Un m?dem que puede funcionar con
>> > >>software de Bill Gates.
>> >
>> > >> Tal vez necesite driver y exista driver.
>> >
>> > >> Mira ver si el chip es Conexant, si lo es para que vaya bien
>> > >> tendr?
>> > >>que ser: RC56D, SMARTSCM, SMARTCF y si no lo es, tienes un modem win,
>> > >>en lugar de un modem lin.
>> >
>> > >> En busca de Google "modem linux" encontrar?s drivers, si los hay.
>> >
>> > >>Saludos.
>> >
>> > > El modem es:
>> > > D-Link WEBCRUISER DRM-560EL 56000bps Data/Fax/Voice (tiene para
>> > > enchufar en puerto COM).
>> >
>> > > Un Saludo.
>> >
>> > He dado un repaso por Google y creo que tiene un chip de lo peor
>> > para
>> > Linux.
>> >
>> > Lo m?s importante de un modem es el chip o chipset, que parece ser
>> > para este modem es el chip: Rockwell RCVDL56ACF/SP,
>> > en las especificaciones t?cnicas este modem funciona en Windows 95/98,
z1rr...@gmail.com
> Desconozco Ubunto, pero en Debian, hace lo mismo que te sucede a ti, y ello
> se soluciona. Entrando como root en /etc/ppp/ edita el fichero options, y
> la línea debug quita la almohadilla, y puestos al asunto como te dice
> Gonzalo quita también la almohadilla al kdebug n, a ver que sucede.
>
Bueno acabo de estar probando lo que me dijo Gonzalo y aqui el
resultado del syslog (parece que algo mas si que mostro):
root@ubuntu:/home/ubuntu# tail -f /var/log/syslog
Apr 27 21:29:20 ubuntu chat[9669]: send (ATZ^M)
Apr 27 21:29:20 ubuntu chat[9669]: send (AT&FH0M0^M)
Apr 27 21:29:20 ubuntu chat[9669]: expect (OK)
Apr 27 21:29:20 ubuntu chat[9669]: ATZ^MAT&F^M
Apr 27 21:29:20 ubuntu chat[9669]: OK
Apr 27 21:29:20 ubuntu chat[9669]: -- got it
Apr 27 21:29:20 ubuntu chat[9669]: send (ATDT*99#^M)
Apr 27 21:29:21 ubuntu chat[9669]: timeout set to 75 seconds
Apr 27 21:29:21 ubuntu chat[9669]: expect (CONNECT)
Apr 27 21:29:21 ubuntu chat[9669]: ^M
Apr 27 21:29:31 ubuntu ntpdate[9679]: can't find host ntp.ubuntu.com
Apr 27 21:29:31 ubuntu ntpdate[9679]: no servers can be used, exiting
Apr 27 21:29:33 ubuntu NetworkManager: <information>^IGoing to sleep.
Apr 27 21:29:33 ubuntu NetworkManager: <information>^IWaking up from
sleep.
Apr 27 21:29:33 ubuntu NetworkManager: <information>^IDeactivating
device eth0.
Apr 27 21:29:33 ubuntu dhclient: receive_packet failed on eth0:
Network is down
Apr 27 21:29:33 ubuntu kernel: [ 1017.429385] eth0: link down
Apr 27 21:29:33 ubuntu kernel: [ 1017.429415] ADDRCONF(NETDEV_UP):
eth0: link is not ready
Apr 27 21:29:33 ubuntu NetworkManager: <information>^Ieth0: Device is
fully-supported using driver '8139too'.
Apr 27 21:29:33 ubuntu NetworkManager:
<information>^Inm_device_init(): waiting for device's worker thread to
start
Apr 27 21:29:33 ubuntu NetworkManager:
<information>^Inm_device_init(): device's worker thread started,
continuing.
Apr 27 21:29:33 ubuntu NetworkManager: <information>^INow managing
wired Ethernet (802.3) device 'eth0'.
Apr 27 21:29:33 ubuntu NetworkManager: <information>^IDeactivating
device eth0.
Apr 27 21:29:54 ubuntu chat[9669]: 0^MATDT*99#^M^M
Apr 27 21:29:54 ubuntu chat[9669]: CONNECT
Apr 27 21:29:54 ubuntu chat[9669]: -- got it
Apr 27 21:29:54 ubuntu pppd[9656]: Serial connection established.
Apr 27 21:29:54 ubuntu pppd[9656]: using channel 4
Apr 27 21:29:54 ubuntu pppd[9656]: Using interface ppp0
Apr 27 21:29:54 ubuntu pppd[9656]: Connect: ppp0 <--> /dev/ttyS0
Apr 27 21:29:55 ubuntu pppd[9656]: sent [LCP ConfReq id=0x1 <asyncmap
0x0> <magic 0xb398fb62> <pcomp> <accomp>]
Apr 27 21:29:55 ubuntu pppd[9656]: rcvd [LCP ConfReq id=0x1 <asyncmap
0x0> <pcomp> <accomp> <auth pap>]
Apr 27 21:29:55 ubuntu pppd[9656]: sent [LCP ConfAck id=0x1 <asyncmap
0x0> <pcomp> <accomp> <auth pap>]
Apr 27 21:29:55 ubuntu pppd[9656]: rcvd [LCP ConfRej id=0x1 <magic
0xb398fb62>]
Apr 27 21:29:55 ubuntu pppd[9656]: sent [LCP ConfReq id=0x2 <asyncmap
0x0> <pcomp> <accomp>]
Apr 27 21:29:55 ubuntu pppd[9656]: rcvd [LCP ConfAck id=0x2 <asyncmap
0x0> <pcomp> <accomp>]
Apr 27 21:29:55 ubuntu pppd[9656]: sent [LCP EchoReq id=0x0 magic=0x0]
Apr 27 21:29:55 ubuntu pppd[9656]: sent [PAP AuthReq id=0x1
user="telefonicanet@telefonicanet" password=<hidden>]
Apr 27 21:29:55 ubuntu pppd[9656]: rcvd [PAP AuthAck id=0x1 ""]
Apr 27 21:29:55 ubuntu pppd[9656]: PAP authentication succeeded
Apr 27 21:29:55 ubuntu pppd[9656]: sent [CCP ConfReq id=0x1 <deflate
15> <deflate(old#) 15> <bsd v1 15>]
Apr 27 21:29:55 ubuntu pppd[9656]: sent [IPCP ConfReq id=0x1 <compress
VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
Apr 27 21:29:57 ubuntu pppd[9656]: rcvd [IPCP ConfReq id=0x1 <addr
81.**.5.**>]
Apr 27 21:29:57 ubuntu pppd[9656]: sent [IPCP ConfAck id=0x1 <addr
81.**.5.**>]
Apr 27 21:29:57 ubuntu pppd[9656]: rcvd [IPCP ConfRej id=0x1 <compress
VJ 0f 01>]
Apr 27 21:29:57 ubuntu pppd[9656]: sent [IPCP ConfReq id=0x2 <addr
0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
Apr 27 21:29:58 ubuntu pppd[9656]: sent [CCP ConfReq id=0x1 <deflate
15> <deflate(old#) 15> <bsd v1 15>]
Apr 27 21:29:58 ubuntu pppd[9656]: rcvd [LCP ProtRej id=0x3 80 fd 01
01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f]
Apr 27 21:29:58 ubuntu pppd[9656]: Protocol-Reject for 'Compression
Control Protocol' (0x80fd) received
Apr 27 21:30:00 ubuntu pppd[9656]: sent [IPCP ConfReq id=0x2 <addr
0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
Apr 27 21:30:00 ubuntu pppd[9656]: rcvd [IPCP ConfNak id=0x2 <addr
81.47.5.223> <ms-dns1 80.58.32.33> <ms-dns3 80.58.0.97>]
Apr 27 21:30:00 ubuntu pppd[9656]: sent [IPCP ConfReq id=0x3 <addr
81.47.5.223> <ms-dns1 80.58.32.33> <ms-dns3 80.58.0.97>]
Apr 27 21:30:03 ubuntu pppd[9656]: sent [IPCP ConfReq id=0x3 <addr
81.47.5.223> <ms-dns1 80.58.32.33> <ms-dns3 80.58.0.97>]
Apr 27 21:30:03 ubuntu pppd[9656]: rcvd [IPCP ConfAck id=0x3 <addr
81.47.5.223> <ms-dns1 80.58.32.33> <ms-dns3 80.58.0.97>]
Apr 27 21:30:03 ubuntu pppd[9656]: Cannot determine ethernet address
for proxy ARP
Apr 27 21:30:03 ubuntu pppd[9656]: local IP address 81.**.5.**
Apr 27 21:30:03 ubuntu pppd[9656]: remote IP address 81.**.5.**
Apr 27 21:30:03 ubuntu pppd[9656]: primary DNS address 80.58.32.33
Apr 27 21:30:03 ubuntu pppd[9656]: secondary DNS address 80.58.0.97
Apr 27 21:30:03 ubuntu pppd[9656]: Script /etc/ppp/ip-up started (pid
9714)
Apr 27 21:30:03 ubuntu pppd[9656]: Script /etc/ppp/ip-up finished (pid
9714), status = 0x0
Apr 27 21:30:55 ubuntu pppd[9656]: rcvd [LCP CodeRej id=0x4 09 02 00
08 00 00 00 00]
Apr 27 21:30:55 ubuntu pppd[9656]: LCP: Rcvd Code-Reject for code 9,
id 2
Apr 27 21:31:25 ubuntu pppd[9656]: rcvd [LCP CodeRej id=0x5 09 03 00
08 00 00 00 00]
Apr 27 21:31:25 ubuntu pppd[9656]: LCP: Rcvd Code-Reject for code 9,
id 3
Apr 27 21:31:36 ubuntu gconfd (root-8826): El servidor GConf no está
en uso, cerrándolo.
Apr 27 21:31:36 ubuntu gconfd (root-8826): Finalizando
Apr 27 21:31:55 ubuntu pppd[9656]: No response to 4 echo-requests
Apr 27 21:31:55 ubuntu pppd[9656]: Serial link appears to be
disconnected.
Apr 27 21:31:55 ubuntu pppd[9656]: Connect time 1.9 minutes.
Apr 27 21:31:55 ubuntu pppd[9656]: Sent 29746 bytes, received 115648
bytes.
Apr 27 21:31:55 ubuntu pppd[9656]: Script /etc/ppp/ip-down started
(pid 9769)
Apr 27 21:31:55 ubuntu pppd[9656]: sent [LCP TermReq id=0x3 "Peer not
responding"]
Apr 27 21:31:55 ubuntu pppd[9656]: Script /etc/ppp/ip-down finished
(pid 9769), status = 0x0
Apr 27 21:31:55 ubuntu pppd[9656]: rcvd [LCP TermAck id=0x3]
Apr 27 21:31:55 ubuntu pppd[9656]: Connection terminated.
Apr 27 21:31:56 ubuntu pppd[9656]: Exit.
Aqui les dejo mi /etc/ppp/options:
# /etc/ppp/options
#
# Originally created by Jim Knoble <jmkn...@mercury.interpath.net>
# Modified for Debian by alvar Bray <al...@meiko.co.uk>
# Modified for PPP Server setup by Christoph Lameter
<clam...@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
noauth
# ... Unfortunately, fixing this properly in the peers file
# (/etc/ppp/peers/ppp0, typically) is apparently incompatible with the
# paradigm used by gnome-system-tools and system-tools-backend for
# managing the peers files. So in Ubuntu Feisty we change the
default.
# 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 7
# 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(8)
# 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>---
Saludos.
Gonzalo Pérez de Olaguer Córdoba
el Sun, 27 Apr 2008 12:41:33 -0700 (PDT) escribiste:
> Apr 27 21:30:55 ubuntu pppd[9656]: rcvd [LCP CodeRej id=0x4 09 02 00 08 00 00 00 00]
> Apr 27 21:30:55 ubuntu pppd[9656]: LCP: Rcvd Code-Reject for code 9, id 2
> Apr 27 21:31:25 ubuntu pppd[9656]: rcvd [LCP CodeRej id=0x5 09 03 00 08 00 00 00 00]
> Apr 27 21:31:25 ubuntu pppd[9656]: LCP: Rcvd Code-Reject for code 9, id 3
Pues googleando esto --> LCP: Rcvd Code-Reject for code 9, id
sale, entre otras, esta página:
http://fixunix.com/ppp/62447-pppd-via-gprs-disconnection-problem.html
donde dice (otras páginas también dicen lo mismo) que el problema está
en que el otro extremo está rechazando las solicitudes LCP EchoReq.
La solución que dan es desactivar los ecos:
lcp-echo-interval 0
lcp-echo-failure 0
Yo lo metería en /etc/ppp/peers/<lo-que-sea>, porque parece ser un problema
del proveedor de acceso al que te estás conectando, no del módem.
Pero si no sabes qué es <lo-que-sea> mételo en /etc/ppp/options, si
sólo usas un proveedor de acceso.
Por cierto, ¿te estás conectando a través del teléfono de toda la vida
(RTB) o estás usando algo "raro": móvil, cable, bluetooth, ...?
z1rr...@gmail.com
wrote:
> Hola z1rr0...@gmail.com
> PGP key 2861C704 --- F206 5671 6789 425D 111C 1302 214F 1934 2861 C704
Me conecto a traves de la linea telefonica.
Entonces meto:
lcp-echo-interval 0
lcp-echo-failure 0
en el /etc/ppp/options, verdad?
aver si se soluciona este maldito problema
Muchas gracias por ayudar.
Saludos.
Gonzalo Pérez de Olaguer Córdoba
el Sun, 27 Apr 2008 15:21:12 -0700 (PDT) escribiste:
> Entonces meto:
>
> lcp-echo-interval 0
> lcp-echo-failure 0
>
> en el /etc/ppp/options, verdad?
Pruébalo, a ver qué pasa. Y si falla postea los nuevos logs.
--
Gonzalo Pérez de Olaguer Córdoba <gp...@iies.es>
z1rr...@gmail.com
wrote:
> Hola z1rr0...@gmail.com
> el Sun, 27 Apr 2008 15:21:12 -0700 (PDT) escribiste:
>
> > Entonces meto:
>
> > lcp-echo-interval 0
> > lcp-echo-failure 0
>
> > en el /etc/ppp/options, verdad?
>
> Pruébalo, a ver qué pasa. Y si falla postea los nuevos logs.
>
> --
> PGP key 2861C704 --- F206 5671 6789 425D 111C 1302 214F 1934 2861 C704
Bueno ayer no mas hacer la ultima respuesta y antes de irme a dormir
probe poniendo:
>> lcp-echo-interval 0
>> lcp-echo-failure 0
en /etc/ppp/options
y al parecer ya no se me desconectaba, estuve unos 8 minutos
conectados y me fuy a dormir.
Esta tarde lo pruebo mejor y os digo.
Muchisimas gracias a todos.
Saludos.
atm
Te paso un modelo de los cuatro ficheros que suele usar pppd.
/etc/ppp/options
connect /etc/ppp/telefonia
crtscts
modem
passive
user usuario@compania
noipdefault
debug
defaultroute
asyncmap a0000
/dev/ttyS0
115200
#mru 4136
/etc/ppp/telefonia
#!/bin/sh
/usr/sbin/chat -v "" atdtw968980xxx CONNECT ""
(Este fichero ha de tener derechos con chmod y chown)
Por ejemplo chmod 766 telefonia
chown root.root telefonia y el número de telefono lo da el proveedor.
Secrets for authentication using CHAP o PAP
/etc/ppp/chap-secrets o/y /etc/ppp/pap-secrets
# client server secret IP addresses
"usuario@compania" * "clave1"
"usuario2@compania2" * "clave2"
Y finalment el resolv.conf, para dar los concentradores, el primario y
secundario del proveedor, cada proveedor los tiene distintos.
/etc/resolv.conf
nameserver 212.59.199.2
nameserver 212.59.199.6
Mi opinión es que tienes un modem incompleto y que sólo irá bien si
hay poco tráfico, durante la madrugada.
Saludos.
z1rr...@gmail.com
Lo de desactivar los echos funciono :P
ayer no se me desconecto en toda la tarde ;D
Muchisimas gracias.
Hay alguna forma de conectarte por el modem con solo un comando?
Es por no estar entrando cada vez a redes, clickear, activar red.....
etc
Saludos.
Gonzalo Pérez de Olaguer Córdoba
el Tue, 29 Apr 2008 11:41:46 -0700 (PDT) escribiste:
> Lo de desactivar los echos funciono :P
> ayer no se me desconecto en toda la tarde ;D
> Muchisimas gracias.
Un consejo: cuando respondas a un artículo, está muy bien que cites el mensaje
al que estás respondiendo, y que pongas la cita antes que la respuesta, pero procura
borrar todo lo que no sea necesario para entender tu respuesta, para evitar
que los artículos sean demasiado largos.
> Hay alguna forma de conectarte por el modem con solo un comando?
> Es por no estar entrando cada vez a redes, clickear, activar red.....
> etc
Sí, aunque depende de cómo tengas configuradas las cosas.
En el caso ideal, te basta ejecutar 'pon' para conectarte y 'poff' para
desconectarte, y puedes hacerlo como usuario normal, sin necesidad de
usar la cuenta de root.
Pruébalo. Es probable que te falle, por alguna de las siguientes razones:
- si como root funciona pero como usuario normal no funciona, entonces
prueba a incluir al usuario normal en el grupo dip, ejecutando,
como root, 'adduser TU_NOMBRE_DE_USUARIO_NORMAL dip'
Para que eso tenga efecto el usuario normal debe salir y volver a entrar
en el ordenador (sal de la sesión X y vuelve a entrar).
- si como root tampoco funciona, entonces es que se está usando un nombre
de proveedor distinto a "provider", que es el valor por defecto.
La lista de proveedores configurados la obtendrás ejecutando,
como root, 'ls /etc/ppp/peers'.
En este caso tienes que conectarte ejecutando esto: 'pon PROVEEDOR'.
Si te aclaras con el inglés, todo esto lo tienes documentado en el ordenador.
Empieza por leer /usr/share/doc/ppp/README.Debian.gz
--
Gonzalo Pérez de Olaguer Córdoba <gp...@iies.es>