Connection internet sous pppoe [Fermé]

Signaler
Messages postés
1928
Date d'inscription
vendredi 21 avril 2006
Statut
Membre
Dernière intervention
5 août 2015
-
Messages postés
1928
Date d'inscription
vendredi 21 avril 2006
Statut
Membre
Dernière intervention
5 août 2015
-
Bonjour,

Lors de l'IPL de ma machine (Mandriva 2008, Livebox) la connection à internet est anormalement longue (14 minutes !) Après avoir démarré, la connection à internet est normale.

Dans /var/Log/messages, on trouve :

Jan 13 12:06:10 altair kernel: r8169: eth1: link up
Jan 13 12:06:10 altair ifplugd(eth1)[3795]: Using interface eth1/00:40:F4:B3:62:64 with driver <r8169> (version: 2.2LK)
Jan 13 12:06:10 altair ifplugd(eth1)[3795]: Using detection mode: SIOCETHTOOL
Jan 13 12:06:10 altair ifplugd(eth1)[3795]: Initialization complete, link beat detected.
Jan 13 12:06:10 altair ifplugd(eth1)[3795]: Executing '/etc/ifplugd/ifplugd.action eth1 up'.
Jan 13 12:06:10 altair kernel: PPP generic driver version 2.4.2
Jan 13 12:06:10 altair ifup-ppp: pppd started for ppp0 on at
Jan 13 12:06:11 altair pppd[3829]: pppd 2.4.4 started by root, uid 0
Jan 13 12:06:11 altair pppd[3829]: Using interface ppp0
Jan 13 12:06:11 altair pppd[3829]: Connect: ppp0 <--> /dev/pts/0
Jan 13 12:06:13 altair NET[3976]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf
Jan 13 12:06:13 altair ifplugd(eth1)[3795]: Program executed successfully.
Jan 13 12:06:42 altair pppd[3829]: LCP: timeout sending Config-Requests
Jan 13 12:06:42 altair pppd[3829]: Connection terminated.
Jan 13 12:06:42 altair pppd[3829]: Modem hangup
Jan 13 12:06:46 altair pppd[3829]: Using interface ppp0
Jan 13 12:06:46 altair pppd[3829]: Connect: ppp0 <--> /dev/pts/1
Jan 13 12:06:46 altair pppoe[3892]: Timeout waiting for PADS packets
Jan 13 12:07:17 altair pppd[3829]: LCP: timeout sending Config-Requests
Jan 13 12:07:17 altair pppd[3829]: Connection terminated.
Jan 13 12:07:17 altair pppd[3829]: Modem hangup
Jan 13 12:07:21 altair pppd[3829]: Using interface ppp0
Jan 13 12:07:21 altair pppd[3829]: Connect: ppp0 <--> /dev/pts/0
Jan 13 12:07:21 altair pppoe[3992]: Timeout waiting for PADS packets
Jan 13 12:07:52 altair pppd[3829]: LCP: timeout sending Config-Requests
Jan 13 12:07:52 altair pppd[3829]: Connection terminated.
Jan 13 12:07:52 altair pppd[3829]: Modem hangup

......

Jan 13 12:19:01 altair pppd[3829]: Connect: ppp0 <--> /dev/pts/0
Jan 13 12:19:01 altair pppoe[4112]: Timeout waiting for PADS packets
Jan 13 12:19:32 altair pppd[3829]: LCP: timeout sending Config-Requests
Jan 13 12:19:32 altair pppd[3829]: Connection terminated.
Jan 13 12:19:32 altair pppd[3829]: Modem hangup
Jan 13 12:19:36 altair pppd[3829]: Using interface ppp0
Jan 13 12:19:36 altair pppd[3829]: Connect: ppp0 <--> /dev/pts/1
Jan 13 12:19:36 altair pppoe[4118]: Timeout waiting for PADS packets
Jan 13 12:20:07 altair pppd[3829]: LCP: timeout sending Config-Requests
Jan 13 12:20:07 altair pppd[3829]: Connection terminated.
Jan 13 12:20:07 altair pppd[3829]: Modem hangup
Jan 13 12:20:11 altair pppd[3829]: Using interface ppp0
Jan 13 12:20:11 altair pppd[3829]: Connect: ppp0 <--> /dev/pts/0
Jan 13 12:20:11 altair pppoe[4124]: Timeout waiting for PADS packets
Jan 13 12:20:42 altair pppd[3829]: LCP: timeout sending Config-Requests
Jan 13 12:20:42 altair pppd[3829]: Connection terminated.
Jan 13 12:20:42 altair pppd[3829]: Modem hangup
Jan 13 12:20:46 altair pppoe[4130]: Timeout waiting for PADS packets
Jan 13 12:20:46 altair pppd[3829]: Exit.
Jan 13 12:20:47 altair kernel: fuse init (API version 7.8)
Jan 13 12:20:47 altair kernel: tun: Universal TUN/TAP device driver, 1.6
Jan 13 12:20:47 altair kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>

Je n'arrive pas à touver l'origine de ce problème.
Merci de bien vouloir me mettre sur la piste pour résoudre ce problème.

Salutations

4 réponses

Messages postés
8158
Date d'inscription
samedi 7 août 2004
Statut
Membre
Dernière intervention
1 septembre 2014
469
Bonjour,

je focaliserai sur ceci :
Timeout waiting for PADS packets

LCP: timeout sending Config-Requests


peut-être un problème de pare-feu ????

autre piste : voir fichier /etc/resolv.conf ??? fichier /etc/ppp/resolv.conf ???

:-))
Messages postés
1928
Date d'inscription
vendredi 21 avril 2006
Statut
Membre
Dernière intervention
5 août 2015
117
Merci, je me mets sur ces pistes !
Messages postés
8158
Date d'inscription
samedi 7 août 2004
Statut
Membre
Dernière intervention
1 septembre 2014
469
Lors de l'IPL de ma machine

au fait ça veut dire quoi IPL ?

:-))
Messages postés
1928
Date d'inscription
vendredi 21 avril 2006
Statut
Membre
Dernière intervention
5 août 2015
117
Démarrage de l'ordi, ou boot. En fait je ne me rappèle plus ce que veut dire le sigle !
Messages postés
8158
Date d'inscription
samedi 7 août 2004
Statut
Membre
Dernière intervention
1 septembre 2014
469
ok ! ça serait bien d'afficher les fichiers /etc/resolv.conf et ppp/resolv.conf

:-))
Messages postés
1928
Date d'inscription
vendredi 21 avril 2006
Statut
Membre
Dernière intervention
5 août 2015
117
Voila, mai c'est un peu long !

==> /etc/resolv.conf :
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 80.10.246.130
nameserver 80.10.246.3
search RAMET

==>ppp/resolv.conf :
# Ethernet card connected to DSL modem
ETH='eth1'

# PPPoE 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 xxyyzz@magma.ca
USER='root@altair'

# 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=80.10.246.130
DNS2=80.10.246.3

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

### ONLY TOUCH THE FOLLOWING SETTINGS IF YOU'RE AN EXPERT

# How long pppoe-start waits for a new PPP interface to appear before
# concluding something went wrong. If you use 0, then pppoe-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 pppoe-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 pppoe-start polls to check if link is up
CONNECT_POLL=2

# Specific desired AC Name
ACNAME=

# Specific desired service name
SERVICENAME=

# Character to echo at each poll. Use PING="" if you don't want
# anything echoed
PING="."

# File where the pppoe-connect script writes its process-ID.
# Three files are actually used:
# $PIDFILE contains PID of pppoe-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-pppoe.pid"

# Do you want to use synchronous PPP? "yes" or "no". "yes" is much
# easier on CPU usage, but may not work for you. It is safer to use
# "no", but you may want to experiment with "yes". "yes" is generally
# safe on Linux machines with the n_hdlc line discipline; unsafe on others.
SYNCHRONOUS=no

# Do you want to clamp the MSS? Here's how to decide:
# - If you have only a SINGLE computer connected to the DSL modem, choose
# "no".
# - If you have a computer acting as a gateway for a LAN, choose "1412".
# The setting of 1412 is safe for either setup, but uses slightly more
# CPU power.
CLAMPMSS=1412
#CLAMPMSS=no

# LCP echo interval and failure count.
LCP_INTERVAL=20
LCP_FAILURE=3

# PPPOE_TIMEOUT should be about 4*LCP_INTERVAL
PPPOE_TIMEOUT=80

# Firewalling: One of NONE, STANDALONE or MASQUERADE
FIREWALL=STANDALONE

# Linux kernel-mode plugin for pppd. If you want to try the kernel-mode
# plugin, use LINUX_PLUGIN=/etc/ppp/plugins/rp-pppoe.so
LINUX_PLUGIN=

# Any extra arguments to pass to pppoe. Normally, use a blank string
# like this:
PPPOE_EXTRA=""

########## DON'T CHANGE BELOW UNLESS YOU KNOW WHAT YOU ARE DOING
# If you wish to COMPLETELY overrride the pppd invocation:
# Example:
# OVERRIDE_PPPD_COMMAND="pppd call dsl"

# If you want pppoe-connect to exit when connection drops:
# RETRY_ON_FAILURE=no