Fibre optique et debian :)

domoticity · Novembre 21, 2017, 9:55am

Hello à toutes et tous.
A la maison j’ai une connexion fibre chez Orange et je souhaiterais utiliser une nanocard Bananapi directement derrière mon ONT.
Orange utilisant le protocole pppoe, j’ai trouvé des tuto qui vont bien

https://benjamin.sonntag.fr/Se_debarasser_de_la_livebox_fibre_orange_pppoe_mode_d_emploi_

donc dans le fichier /etc/modules
j’ai ajouté le module 8021q.

ensuite modifié /etc/network/interfaces
auto eth0 eth0.832 ppp0
iface eth0 inet manual
iface eth0.832 inet manual
iface ppp0 inet ppp
provider ft_fibre

J’ai créé le fichier de configuration /etc/ppp/peers/ft_fibre

pty "/usr/sbin/pppoe -I eth0.832 -T 80 -m 1452"
noipdefault
hide-password
lcp-echo-interval 20
lcp-echo-failure 3
connect /bin/true
noauth
persist
mtu 1492
usepeerdns
defaultroute
noaccomp
default-asyncmap
plugin rp-pppoe.so eth0.832
user "fti/blabla"

Et j’ai ajouté les identifiants de connexion dans /etc/ppp/chap-secrets et /etc/ppp/pap-secrets

“fti/blabla” * “votrepassword”

Je reboot la carte et lance la configuration via la commande
pon ft_fibre

quand je regarde les logs avec plogs j’ai des erreurs

 root@bananapim2:~# plog
Nov 20 22:18:09 localhost pppd[1172]: Serial connection established.
Nov 20 22:18:09 localhost pppd[1172]: Using interface ppp0
Nov 20 22:18:09 localhost pppd[1172]: Connect: ppp0 <--> /dev/pts/1
root@bananapim2:~# plog
Nov 20 22:18:14 localhost pppd[1165]: Timeout waiting for PADO packets
Nov 20 22:18:15 localhost pppd[1165]: Unable to complete PPPoE Discovery
Nov 20 22:18:17 localhost pppd[1131]: Timeout waiting for PADO packets
Nov 20 22:18:17 localhost pppd[1131]: Unable to complete PPPoE Discovery

Le kernel gere le pppoe nativement.
Je ne vois pas mon ou mes erreurs.
Si quelquun a une idée

domoticity · Novembre 20, 2017, 9:42pm

J’ai oublié de dire qu’a priori maintenant le vlan internet chez Orange est le 832, pas le 835 comme dit dans le tuto.

PengouinPdt · Novembre 21, 2017, 9:55am

Bonjour,
En quoi, c’est de la programmation ?
Conformément à la FAQ, merci de veiller à poster dans le forum adéquate, en l’occurence “Support” !

Déplacement du post !

mattotop · Novembre 21, 2017, 6:50pm

Tu pourrais donner un extrait un peu plus long de ton log ppp, avec plog -x ou x est un nombre suffisant pour avoir une sessions de connection complète, parce que là, c’est un peu trop parcellaire pour réflechir.

domoticity · Novembre 22, 2017, 12:03am

Bonsoir
Merci pour ta réponse.
Je t’envoie ça demain dans la journée.
Par contre je ne sais pas si ça peut aider à réfléchir,
Mais quand je fais ifconfig je ne vois pas mon interface ppp0, je vois les wifi l’éther et et le vlan sous forme eth0.83 mais pas le ppp0.

domoticity · Novembre 22, 2017, 4:06pm

RE,
Merci encore pour ta réponse.

Alors je te remets mes fichiers onf.
Pour /etc/network/interfaces j’ai mis :
source /etc/network/interfaces.d/*

# Local loopback
auto lo
iface lo inet loopback

#ETH0
auto eth0
allow-hotplug eth0
iface eth0 inet manual

#PROVIDER
auto eth0.832
iface eth0.832 inet manual

auto ppp0
iface ppp0 inet ppp
        provider fibre

#WIFI AP
auto wlan0
allow-hotplug wlan0
iface wlan0 inet static
        address 10.0.0.1
        netmask 255.255.255.0
        network 10.0.0.0
        gateway 10.0.0.1
        broadcast 10.0.0.255
        dns nameservers 8.8.8.8
        hwaddress ether 98:3b:16:c6:36:36

#WIFI MANAGED
auto wlan1
allow-hotplug wlan1
iface wlan1 inet manual

Ensuite le fichier pap-secret
/etc/ppp/pap-secrets

# /etc/ppp/pap-secrets
#
# This is a pap-secrets file to be used with the AUTO_PPP function of
# mgetty. mgetty-0.99 is preconfigured to startup pppd with the login option
# which will cause pppd to consult /etc/passwd (and /etc/shadow in turn)
# after a user has passed this file. Don't be disturbed therefore by the fact
# that this file defines logins with any password for users. /etc/passwd
# (again, /etc/shadow, too) will catch passwd mismatches.
#
# This file should block ALL users that should not be able to do AUTO_PPP.
# AUTO_PPP bypasses the usual login program so it's necessary to list all
# system userids with regular passwords here.
#
# ATTENTION: The definitions here can allow users to login without a
# password if you don't use the login option of pppd! The mgetty Debian
# package already provides this option; make sure you don't change that.

# INBOUND connections

# Every regular user can use PPP and has to use passwords from /etc/passwd
*       hostname        ""      *

# UserIDs that cannot use PPP at all. Check your /etc/passwd and add any
# other accounts that should not be able to use pppd!
guest   hostname        "*"     -
master  hostname        "*"     -
root    hostname        "*"     -
support hostname        "*"     -
stats   hostname        "*"     -

# OUTBOUND connections

# Here you should add your userid password to connect to your providers via
# PAP. The * means that the password is to be used for ANY host you connect
# to. Thus you do not have to worry about the foreign machine name. Just
# replace password with your password.
# If you have different providers with different passwords then you better
# remove the following line.

#       *       password
"fti/XXXXX" * "XXXXXX"

Et le fichier chap-secrets
/etc/ppp/chap-secrets

# Secrets for authentication using CHAP
# client        server  secret                  IP addresses
"fti/XXXXX" * "XXXXX"

Ensuite pour le fichier provider
/etc/ppp/peers/fibre

quand je mets :
pty "/usr/sbin/pppoe -I eth0.833 -T 80 -m 1452"
noipdefault
hide-password
lcp-echo-interval 20
lcp-echo-failure 3
connect /bin/true
noauth
persist
mtu 1492
usepeerdns
defaultroute
noaccomp
default-asyncmap
plugin rp-pppoe.so eth0.832 <======== J’ai essayé sans aussi
# remplacez fti/blabla par votre login orange :
user “fti/XXXX”

En faisant plog -10000000 j’ai :
Nov 22 16:41:16 localhost pppd[687]: Plugin rp-pppoe.so loaded.
Nov 22 16:41:16 localhost pppd[689]: pppd 2.4.6 started by root, uid 0
Nov 22 16:41:16 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:41:16 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:41:19 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:41:29 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:41:49 localhost pppd[689]: Timeout waiting for PADO packets
Nov 22 16:41:49 localhost pppd[689]: Unable to complete PPPoE Discovery
Nov 22 16:42:19 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:42:19 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:42:24 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:42:34 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:42:45 localhost pppd[1729]: Plugin rp-pppoe.so loaded.
Nov 22 16:42:45 localhost pppd[1730]: pppd 2.4.6 started by root, uid 0
Nov 22 16:42:45 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:42:45 localhost pppd[1730]: error receiving pppoe packet: Network is down
Nov 22 16:42:50 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:42:54 localhost pppd[689]: Timeout waiting for PADO packets
Nov 22 16:42:54 localhost pppd[689]: Unable to complete PPPoE Discovery
Nov 22 16:43:00 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:43:20 localhost pppd[1730]: Timeout waiting for PADO packets
Nov 22 16:43:20 localhost pppd[1730]: Unable to complete PPPoE Discovery
Nov 22 16:43:24 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:43:24 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:43:29 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:43:39 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:43:50 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:43:50 localhost pppd[1730]: error receiving pppoe packet: Network is down
Nov 22 16:43:55 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:43:59 localhost pppd[689]: Timeout waiting for PADO packets
Nov 22 16:43:59 localhost pppd[689]: Unable to complete PPPoE Discovery
Nov 22 16:44:05 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:44:25 localhost pppd[1730]: Timeout waiting for PADO packets
Nov 22 16:44:25 localhost pppd[1730]: Unable to complete PPPoE Discovery
Nov 22 16:44:29 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:44:30 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:44:35 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:44:39 localhost pppd[1749]: Plugin rp-pppoe.so loaded.
Nov 22 16:44:39 localhost pppd[1750]: pppd 2.4.6 started by root, uid 0
Nov 22 16:44:39 localhost pppd[1750]: error sending pppoe packet: Network is down
Nov 22 16:44:39 localhost pppd[1750]: error receiving pppoe packet: Network is down
Nov 22 16:44:44 localhost pppd[1750]: error sending pppoe packet: Network is down
Nov 22 16:44:45 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:44:54 localhost pppd[1750]: error sending pppoe packet: Network is down
Nov 22 16:44:55 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:44:55 localhost pppd[1730]: error receiving pppoe packet: Network is down

Et quand j’enleve la ligne que j’ai tagué, toujours dans le fichier conf provider.

root@diagbox:~# plog -100000000
Nov 22 16:41:16 localhost pppd[687]: Plugin rp-pppoe.so loaded.
Nov 22 16:41:16 localhost pppd[689]: pppd 2.4.6 started by root, uid 0
Nov 22 16:41:16 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:41:16 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:41:19 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:41:29 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:41:49 localhost pppd[689]: Timeout waiting for PADO packets
Nov 22 16:41:49 localhost pppd[689]: Unable to complete PPPoE Discovery
Nov 22 16:42:19 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:42:19 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:42:24 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:42:34 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:42:45 localhost pppd[1729]: Plugin rp-pppoe.so loaded.
Nov 22 16:42:45 localhost pppd[1730]: pppd 2.4.6 started by root, uid 0
Nov 22 16:42:45 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:42:45 localhost pppd[1730]: error receiving pppoe packet: Network is down
Nov 22 16:42:50 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:42:54 localhost pppd[689]: Timeout waiting for PADO packets
Nov 22 16:42:54 localhost pppd[689]: Unable to complete PPPoE Discovery
Nov 22 16:43:00 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:43:20 localhost pppd[1730]: Timeout waiting for PADO packets
Nov 22 16:43:20 localhost pppd[1730]: Unable to complete PPPoE Discovery
Nov 22 16:43:24 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:43:24 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:43:29 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:43:39 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:43:50 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:43:50 localhost pppd[1730]: error receiving pppoe packet: Network is down
Nov 22 16:43:55 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:43:59 localhost pppd[689]: Timeout waiting for PADO packets
Nov 22 16:43:59 localhost pppd[689]: Unable to complete PPPoE Discovery
Nov 22 16:44:05 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:44:25 localhost pppd[1730]: Timeout waiting for PADO packets
Nov 22 16:44:25 localhost pppd[1730]: Unable to complete PPPoE Discovery
Nov 22 16:44:29 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:44:30 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:44:35 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:44:39 localhost pppd[1749]: Plugin rp-pppoe.so loaded.
Nov 22 16:44:39 localhost pppd[1750]: pppd 2.4.6 started by root, uid 0
Nov 22 16:44:39 localhost pppd[1750]: error sending pppoe packet: Network is down
Nov 22 16:44:39 localhost pppd[1750]: error receiving pppoe packet: Network is down
Nov 22 16:44:44 localhost pppd[1750]: error sending pppoe packet: Network is down
Nov 22 16:44:45 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:44:54 localhost pppd[1750]: error sending pppoe packet: Network is down
Nov 22 16:44:55 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:44:55 localhost pppd[1730]: error receiving pppoe packet: Network is down
Nov 22 16:45:00 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:45:05 localhost pppd[689]: Timeout waiting for PADO packets
Nov 22 16:45:05 localhost pppd[689]: Unable to complete PPPoE Discovery
Nov 22 16:45:10 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:45:14 localhost pppd[1750]: Timeout waiting for PADO packets
Nov 22 16:45:14 localhost pppd[1750]: Unable to complete PPPoE Discovery
Nov 22 16:45:30 localhost pppd[1730]: Timeout waiting for PADO packets
Nov 22 16:45:30 localhost pppd[1730]: Unable to complete PPPoE Discovery
Nov 22 16:45:35 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:45:35 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:45:40 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:45:44 localhost pppd[1750]: error sending pppoe packet: Network is down
Nov 22 16:45:44 localhost pppd[1750]: error receiving pppoe packet: Network is down
Nov 22 16:45:49 localhost pppd[1750]: error sending pppoe packet: Network is down
Nov 22 16:45:50 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:46:26 localhost pppd[688]: pppd 2.4.6 started by root, uid 0
Nov 22 16:46:26 localhost pppd[688]: Serial connection established.
Nov 22 16:46:26 localhost pppd[688]: Using interface ppp0
Nov 22 16:46:26 localhost pppd[688]: Connect: ppp0 <--> /dev/pts/0
Nov 22 16:46:26 localhost pppd[688]: Modem hangup
Nov 22 16:46:26 localhost pppd[688]: Connection terminated.
Nov 22 16:46:54 localhost pppd[688]: Serial connection established.
Nov 22 16:46:54 localhost pppd[688]: Using interface ppp0
Nov 22 16:46:54 localhost pppd[688]: Connect: ppp0 <--> /dev/pts/1
Nov 22 16:46:54 localhost pppd[688]: Modem hangup
Nov 22 16:46:54 localhost pppd[688]: Connection terminated.
root@diagbox:~# plog -100000000
Nov 22 16:41:16 localhost pppd[687]: Plugin rp-pppoe.so loaded.
Nov 22 16:41:16 localhost pppd[689]: pppd 2.4.6 started by root, uid 0
Nov 22 16:41:16 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:41:16 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:41:19 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:41:29 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:41:49 localhost pppd[689]: Timeout waiting for PADO packets
Nov 22 16:41:49 localhost pppd[689]: Unable to complete PPPoE Discovery
Nov 22 16:42:19 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:42:19 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:42:24 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:42:34 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:42:45 localhost pppd[1729]: Plugin rp-pppoe.so loaded.
Nov 22 16:42:45 localhost pppd[1730]: pppd 2.4.6 started by root, uid 0
Nov 22 16:42:45 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:42:45 localhost pppd[1730]: error receiving pppoe packet: Network is down
Nov 22 16:42:50 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:42:54 localhost pppd[689]: Timeout waiting for PADO packets
Nov 22 16:42:54 localhost pppd[689]: Unable to complete PPPoE Discovery
Nov 22 16:43:00 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:43:20 localhost pppd[1730]: Timeout waiting for PADO packets
Nov 22 16:43:20 localhost pppd[1730]: Unable to complete PPPoE Discovery
Nov 22 16:43:24 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:43:24 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:43:29 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:43:39 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:43:50 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:43:50 localhost pppd[1730]: error receiving pppoe packet: Network is down
Nov 22 16:43:55 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:43:59 localhost pppd[689]: Timeout waiting for PADO packets
Nov 22 16:43:59 localhost pppd[689]: Unable to complete PPPoE Discovery
Nov 22 16:44:05 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:44:25 localhost pppd[1730]: Timeout waiting for PADO packets
Nov 22 16:44:25 localhost pppd[1730]: Unable to complete PPPoE Discovery
Nov 22 16:44:29 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:44:30 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:44:35 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:44:39 localhost pppd[1749]: Plugin rp-pppoe.so loaded.
Nov 22 16:44:39 localhost pppd[1750]: pppd 2.4.6 started by root, uid 0
Nov 22 16:44:39 localhost pppd[1750]: error sending pppoe packet: Network is down
Nov 22 16:44:39 localhost pppd[1750]: error receiving pppoe packet: Network is down
Nov 22 16:44:44 localhost pppd[1750]: error sending pppoe packet: Network is down
Nov 22 16:44:45 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:44:54 localhost pppd[1750]: error sending pppoe packet: Network is down
Nov 22 16:44:55 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:44:55 localhost pppd[1730]: error receiving pppoe packet: Network is down
Nov 22 16:45:00 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:45:05 localhost pppd[689]: Timeout waiting for PADO packets
Nov 22 16:45:05 localhost pppd[689]: Unable to complete PPPoE Discovery
Nov 22 16:45:10 localhost pppd[1730]: error sending pppoe packet: Network is down
Nov 22 16:45:14 localhost pppd[1750]: Timeout waiting for PADO packets
Nov 22 16:45:14 localhost pppd[1750]: Unable to complete PPPoE Discovery
Nov 22 16:45:30 localhost pppd[1730]: Timeout waiting for PADO packets
Nov 22 16:45:30 localhost pppd[1730]: Unable to complete PPPoE Discovery
Nov 22 16:45:35 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:45:35 localhost pppd[689]: error receiving pppoe packet: Network is down
Nov 22 16:45:40 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:45:44 localhost pppd[1750]: error sending pppoe packet: Network is down
Nov 22 16:45:44 localhost pppd[1750]: error receiving pppoe packet: Network is down
Nov 22 16:45:49 localhost pppd[1750]: error sending pppoe packet: Network is down
Nov 22 16:45:50 localhost pppd[689]: error sending pppoe packet: Network is down
Nov 22 16:46:26 localhost pppd[688]: pppd 2.4.6 started by root, uid 0
Nov 22 16:46:26 localhost pppd[688]: Serial connection established.
Nov 22 16:46:26 localhost pppd[688]: Using interface ppp0
Nov 22 16:46:26 localhost pppd[688]: Connect: ppp0 <--> /dev/pts/0
Nov 22 16:46:26 localhost pppd[688]: Modem hangup
Nov 22 16:46:26 localhost pppd[688]: Connection terminated.
Nov 22 16:46:54 localhost pppd[688]: Serial connection established.
Nov 22 16:46:54 localhost pppd[688]: Using interface ppp0
Nov 22 16:46:54 localhost pppd[688]: Connect: ppp0 <--> /dev/pts/1
Nov 22 16:46:54 localhost pppd[688]: Modem hangup
Nov 22 16:46:54 localhost pppd[688]: Connection terminated.

voila je pense avoir donné toutes les infos lol

mattotop · Novembre 22, 2017, 6:02pm

NON TU N’AVAIS PAS TOUT MIS IL MANQUAIT UNE RECOPIE DE NOUVEAU DE /etc/ppp/peers/ft_fibre !
Mais bon, je serais magnanime, je considèrerais que ça n’a pas changé depuis ton premier post.

Ca permet de réflechir plus, mais rien ne me vient vraiment comme ça.

Alors le “network is down”, est ce que ça ne serait pas tout simplement parce que ta carte réseau elle même (eth0) ne s’active pas (physiquement) ?
ça me paraitrait un peu bizarre si tu vois bien l’interface secondaire eth0.832, mais à tous hasards:
que dit ip link ?

Sinon, ça vaudrait le coup d’enlever tous les auto du fstab, et d’activer eth0, puis eth0.832, puis ppp0, avant de faire le pon (d’ailleurs, ça me parait redondant d’avoir le ifup ppp0 en auto du fstab et le pon), en surveillant carrément le syslog (tail -qf /var/log/syslog).

domoticity · Novembre 22, 2017, 9:30pm

Hello,
En effet tu as raison, j’ai oublié un morceau. désolé
Mais tu la joue fairplay
Plus sérieusement encore merci pour ton aide.

alors dans un premier temps, j’ai fait un ip linkpuis une petite surveillance syslog.
Ensuite j’ai fait un ifdown etth0,eth0.832 et ppp0.
Et je les ai lancé dans le meme ordre a la main avec ifup.

voici :

root@diagbox:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT                                                                              group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mo                                                                             de DEFAULT group default qlen 1000
    link/ether 02:44:07:0f:8f:d8 brd ff:ff:ff:ff:ff:ff
3: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue stat                                                                             e DOWN mode DEFAULT group default qlen 1000
    link/ether 7e:34:01:93:c8:d6 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP m                                                                             ode DEFAULT group default qlen 1000
    link/ether 98:3b:16:c6:36:36 brd ff:ff:ff:ff:ff:ff
5: eth0.832@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFA                                                                             ULT group default qlen 1000
    link/ether 02:44:07:0f:8f:d8 brd ff:ff:ff:ff:ff:ff
root@diagbox:~# tail -qf /var/log/syslog
Nov 22 22:15:09 localhost systemd[1659]: Startup finished in 191ms.
Nov 22 22:15:09 localhost systemd[1]: Started User Manager for UID 0.
Nov 22 22:15:11 localhost pppd[691]: error sending pppoe packet: Network is down
Nov 22 22:15:14 localhost ntpd[973]: Deferring DNS for 3.debian.pool.ntp.org 1
Nov 22 22:15:14 localhost ntpd[1738]: signal_no_reset: signal 17 had flags 4000000
Nov 22 22:15:16 localhost ntpd[973]: Listen normally on 6 wlan0 fe80::9a3b:16ff:fec6:3636 UDP 123
Nov 22 22:15:16 localhost ntpd[973]: peers refreshed
Nov 22 22:15:31 localhost pppd[691]: Timeout waiting for PADO packets
Nov 22 22:15:31 localhost pppd[691]: Unable to complete PPPoE Discovery
Nov 22 22:15:36 localhost ntpd_intres[1738]: host name not found: 0.debian.pool.ntp.org
Nov 22 22:15:56 localhost ntpd_intres[1738]: host name not found: 1.debian.pool.ntp.org
Nov 22 22:15:56 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Wed Nov 22 22:16:26 2017 [try http://www.rsyslog.com/e/2007 ]
Nov 22 22:16:01 localhost pppd[691]: error sending pppoe packet: Network is down
Nov 22 22:16:01 localhost pppd[691]: error receiving pppoe packet: Network is down
Nov 22 22:16:06 localhost pppd[691]: error sending pppoe packet: Network is down
Nov 22 22:16:16 localhost pppd[691]: error sending pppoe packet: Network is down
Nov 22 22:16:16 localhost ntpd_intres[1738]: host name not found: 2.debian.pool.ntp.org
^C
root@diagbox:~# ifdown eth0
root@diagbox:~# ifdown eth0.832
root@diagbox:~# ifdown ppp0
root@diagbox:~# ifup eth0
root@diagbox:~# ifup eth0.832
root@diagbox:~# ifup ppp0
Plugin rp-pppoe.so loaded.
root@diagbox:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 02:44:07:0f:8f:d8 brd ff:ff:ff:ff:ff:ff
3: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 7e:34:01:93:c8:d6 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 98:3b:16:c6:36:36 brd ff:ff:ff:ff:ff:ff
6: eth0.832@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 02:44:07:0f:8f:d8 brd ff:ff:ff:ff:ff:ff
root@diagbox:~# ifconfig ppp0
ppp0: error fetching interface information: Device not found
root@diagbox:~# tail -qf /var/log/syslog
Nov 22 22:16:59 localhost pppd[1994]: pppd 2.4.6 started by root, uid 0
Nov 22 22:16:59 localhost pppd[1994]: error sending pppoe packet: Network is down
Nov 22 22:16:59 localhost pppd[1994]: error receiving pppoe packet: Network is down
Nov 22 22:16:59 localhost systemd[1]: Reloading OpenBSD Secure Shell server.
Nov 22 22:16:59 localhost systemd[1]: Reloaded OpenBSD Secure Shell server.
Nov 22 22:17:01 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Wed Nov 22 22:17:31 2017 [try http://www.rsyslog.com/e/2007 ]
Nov 22 22:17:01 localhost CRON[2061]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Nov 22 22:17:04 localhost pppd[1994]: error sending pppoe packet: Network is down
Nov 22 22:17:14 localhost pppd[1994]: error sending pppoe packet: Network is down
Nov 22 22:17:18 localhost ntpd_intres[1738]: host name not found: 1.debian.pool.ntp.org
Nov 22 22:17:34 localhost pppd[1994]: Timeout waiting for PADO packets
Nov 22 22:17:34 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Wed Nov 22 22:18:04 2017 [try http://www.rsyslog.com/e/2007 ]
Nov 22 22:17:34 localhost pppd[1994]: Unable to complete PPPoE Discovery
Nov 22 22:17:38 localhost ntpd_intres[1738]: host name not found: 2.debian.pool.ntp.org
^C
root@diagbox:~#

est ce que ca te parle plus?

ps : j’ai fait ca avec dans le fichier provider le petit script qui lance le module
plugin rp-pppoe.so eth0.832

Et la je viens de faire les memes manip mais en enlevant plugin rp-pppoe.so eth0.832 du fichier provider fibre

root@diagbox:~# nano /etc/ppp/peers/fibre
root@diagbox:~# ifdown eth0
root@diagbox:~# ifdown eth0.832
root@diagbox:~# ifdown ppp0
root@diagbox:~# ifup eth0
root@diagbox:~# ifup eth0.832
root@diagbox:~# ifup ppp0
root@diagbox:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 02:44:07:0f:8f:d8 brd ff:ff:ff:ff:ff:ff
3: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 7e:34:01:93:c8:d6 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 98:3b:16:c6:36:36 brd ff:ff:ff:ff:ff:ff
7: eth0.832@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 02:44:07:0f:8f:d8 brd ff:ff:ff:ff:ff:ff
root@diagbox:~# tail -qf /var/log/syslog
Nov 22 22:23:39 localhost pppd[2397]: Connect: ppp0 <--> /dev/pts/1
Nov 22 22:23:39 localhost pppoe[2486]: ioctl(SIOCGIFHWADDR): Session 0: No such device
Nov 22 22:23:39 localhost NetworkManager[877]: <info> (ppp0): new Generic device (driver: 'ppp' ifindex: 9)
Nov 22 22:23:39 localhost NetworkManager[877]: <info> (ppp0): exported as /org/freedesktop/NetworkManager/Devices/8
Nov 22 22:23:39 localhost NetworkManager[877]: <info> devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Nov 22 22:23:39 localhost NetworkManager[877]: <info> get unmanaged devices count: 4
Nov 22 22:23:39 localhost pppd[2397]: Modem hangup
Nov 22 22:23:39 localhost pppd[2397]: Connection terminated.
Nov 22 22:23:39 localhost NetworkManager[877]: <info> devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Nov 22 22:23:39 localhost NetworkManager[877]: <info> get unmanaged devices count: 3
Nov 22 22:24:09 localhost pppd[2397]: Serial connection established.
Nov 22 22:24:09 localhost pppd[2397]: Using interface ppp0
Nov 22 22:24:09 localhost pppd[2397]: Connect: ppp0 <--> /dev/pts/1
Nov 22 22:24:09 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Wed Nov 22 22:25:09 2017 [try http://www.rsyslog.com/e/2007 ]
Nov 22 22:24:09 localhost pppoe[2505]: ioctl(SIOCGIFHWADDR): Session 0: No such device
Nov 22 22:24:09 localhost NetworkManager[877]: <info> (ppp0): new Generic device (driver: 'ppp' ifindex: 10)
Nov 22 22:24:09 localhost NetworkManager[877]: <info> (ppp0): exported as /org/freedesktop/NetworkManager/Devices/9
Nov 22 22:24:09 localhost NetworkManager[877]: <info> devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Nov 22 22:24:09 localhost NetworkManager[877]: <info> get unmanaged devices count: 4
Nov 22 22:24:09 localhost pppd[2397]: Modem hangup
Nov 22 22:24:09 localhost pppd[2397]: Connection terminated.
Nov 22 22:24:09 localhost NetworkManager[877]: <info> devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Nov 22 22:24:09 localhost NetworkManager[877]: <info> get unmanaged devices count: 3
Nov 22 22:24:40 localhost pppd[2397]: Serial connection established.
Nov 22 22:24:40 localhost pppd[2397]: Using interface ppp0
Nov 22 22:24:40 localhost pppd[2397]: Connect: ppp0 <--> /dev/pts/1
Nov 22 22:24:40 localhost pppoe[2525]: ioctl(SIOCGIFHWADDR): Session 0: No such device
Nov 22 22:24:40 localhost NetworkManager[877]: <info> (ppp0): new Generic device (driver: 'ppp' ifindex: 11)
Nov 22 22:24:40 localhost NetworkManager[877]: <info> (ppp0): exported as /org/freedesktop/NetworkManager/Devices/10
Nov 22 22:24:40 localhost NetworkManager[877]: <info> devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Nov 22 22:24:40 localhost NetworkManager[877]: <info> get unmanaged devices count: 4
Nov 22 22:24:40 localhost pppd[2397]: Modem hangup
Nov 22 22:24:40 localhost pppd[2397]: Connection terminated.
Nov 22 22:24:40 localhost NetworkManager[877]: <info> devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Nov 22 22:24:40 localhost NetworkManager[877]: <info> get unmanaged devices count: 3

mattotop · Novembre 24, 2017, 9:11am

Désolé du délai.
Bon, alors ce que je te suggérais, c’était de diagnostiquer étape par étape les messages d’erreur, en mettant d’un coté un tail -qf, et de l’autre en faisant une à une les manips, et pas comme tu les a faites.
1/enlever le auto dans la config et rebooter pour être sur que toutes les interfaces soient éteintes et "à froid"
3/ faire un à un les ifup (sans faire de ifdown tout de suite aprés), et vérifier l’état avec ip link pour voir à quel moment apparait quel message.
A la limite, quand tu en arrives à la dernière étape, plutôt que le ifup ppp0, lancer la connection en manuel avec la commande ppp en mode debug (désolé, manque de temps pour détailler plus).

domoticity · Novembre 24, 2017, 9:36pm

Hello.
Ne sois pas désolé, tu m’aides et je te remercie.

Hello,
alors j’ai enlever les auto.
Seul eth0 se lance seul malgrès tout, j’ai un Acces point wifi pour controler la carte/

apres if up eth0.832

diagbox@diagbox:~$ sudo tail -qf /var/log/syslog
Nov 24 22:22:24 localhost systemd[1667]: Starting Timers.
Nov 24 22:22:24 localhost systemd[1667]: Reached target Timers.
Nov 24 22:22:24 localhost systemd[1667]: Starting Sockets.
Nov 24 22:22:24 localhost systemd[1667]: Reached target Sockets.
Nov 24 22:22:24 localhost systemd[1667]: Starting Basic System.
Nov 24 22:22:24 localhost systemd[1667]: Reached target Basic System.
Nov 24 22:22:24 localhost systemd[1667]: Starting Default.
Nov 24 22:22:24 localhost systemd[1667]: Reached target Default.
Nov 24 22:22:24 localhost systemd[1667]: Startup finished in 183ms.
Nov 24 22:22:24 localhost systemd[1]: Started User Manager for UID 0.
Nov 24 22:22:28 localhost ntpd[884]: Deferring DNS for 1.debian.pool.ntp.org 1
Nov 24 22:22:48 localhost ntpd[884]: Deferring DNS for 2.debian.pool.ntp.org 1
Nov 24 22:22:58 localhost NetworkManager[766]: <info> (eth0.832): carrier is OFF
Nov 24 22:22:58 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Fri Nov 24 22:23:28 2017 [try http://www.rsyslog.com/e/2007 ]
Nov 24 22:22:58 localhost NetworkManager[766]: <info> (eth0.832): VLAN ID 832 with parent eth0
Nov 24 22:22:58 localhost NetworkManager[766]: <info> (eth0.832): new VLAN device (driver: '8021q' ifindex: 5)
Nov 24 22:22:58 localhost NetworkManager[766]: <info> (eth0.832): exported as /org/freedesktop/NetworkManager/Devices/4
Nov 24 22:22:58 localhost NetworkManager[766]: <info> devices added (path: /sys/devices/virtual/net/eth0.832, iface: eth0.832)
Nov 24 22:22:58 localhost NetworkManager[766]: <info> locking wired connection setting
Nov 24 22:22:58 localhost NetworkManager[766]: <info> get unmanaged devices count: 3
Nov 24 22:22:59 localhost systemd[1]: Reloading OpenBSD Secure Shell server.
Nov 24 22:22:59 localhost systemd[1]: Reloaded OpenBSD Secure Shell server.

root@diagbox:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 02:44:07:0f:8f:d8 brd ff:ff:ff:ff:ff:ff
3: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 72:ec:1e:08:d9:8c brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000

apres ifup ppp0

root@diagbox:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 02:44:07:0f:8f:d8 brd ff:ff:ff:ff:ff:ff
3: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 72:ec:1e:08:d9:8c brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 98:3b:16:c6:36:36 brd ff:ff:ff:ff:ff:ff
5: eth0.832@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 02:44:07:0f:8f:d8 brd ff:ff:ff:ff:ff:ff
diagbox@diagbox:~$ sudo tail -qf /var/log/syslog
Nov 24 22:22:24 localhost systemd[1667]: Starting Timers.
Nov 24 22:22:24 localhost systemd[1667]: Reached target Timers.
Nov 24 22:22:24 localhost systemd[1667]: Starting Sockets.
Nov 24 22:22:24 localhost systemd[1667]: Reached target Sockets.
Nov 24 22:22:24 localhost systemd[1667]: Starting Basic System.
Nov 24 22:22:24 localhost systemd[1667]: Reached target Basic System.
Nov 24 22:22:24 localhost systemd[1667]: Starting Default.
Nov 24 22:22:24 localhost systemd[1667]: Reached target Default.
Nov 24 22:22:24 localhost systemd[1667]: Startup finished in 183ms.
Nov 24 22:22:24 localhost systemd[1]: Started User Manager for UID 0.
Nov 24 22:22:28 localhost ntpd[884]: Deferring DNS for 1.debian.pool.ntp.org 1
Nov 24 22:22:48 localhost ntpd[884]: Deferring DNS for 2.debian.pool.ntp.org 1
Nov 24 22:22:58 localhost NetworkManager[766]: <info> (eth0.832): carrier is OFF
Nov 24 22:22:58 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Fri Nov 24 22:23:28 2017 [try http://www.rsyslog.com/e/2007 ]
Nov 24 22:22:58 localhost NetworkManager[766]: <info> (eth0.832): VLAN ID 832 with parent eth0
Nov 24 22:22:58 localhost NetworkManager[766]: <info> (eth0.832): new VLAN device (driver: '8021q' ifindex: 5)
Nov 24 22:22:58 localhost NetworkManager[766]: <info> (eth0.832): exported as /org/freedesktop/NetworkManager/Devices/4
Nov 24 22:22:58 localhost NetworkManager[766]: <info> devices added (path: /sys/devices/virtual/net/eth0.832, iface: eth0.832)
Nov 24 22:22:58 localhost NetworkManager[766]: <info> locking wired connection setting
Nov 24 22:22:58 localhost NetworkManager[766]: <info> get unmanaged devices count: 3
Nov 24 22:22:59 localhost systemd[1]: Reloading OpenBSD Secure Shell server.
Nov 24 22:22:59 localhost systemd[1]: Reloaded OpenBSD Secure Shell server.
Nov 24 22:23:08 localhost ntpd[884]: Deferring DNS for 3.debian.pool.ntp.org 1
Nov 24 22:23:08 localhost ntpd[1838]: signal_no_reset: signal 17 had flags 4000000
Nov 24 22:23:10 localhost ntpd[884]: Listen normally on 5 eth0 fe80::44:7ff:fe0f:8fd8 UDP 123
Nov 24 22:23:10 localhost ntpd[884]: Listen normally on 6 wlan0 fe80::9a3b:16ff:fec6:3636 UDP 123
Nov 24 22:23:10 localhost ntpd[884]: peers refreshed
Nov 24 22:23:30 localhost ntpd_intres[1838]: host name not found: 0.debian.pool.ntp.org
Nov 24 22:23:30 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Fri Nov 24 22:24:00 2017 [try http://www.rsyslog.com/e/2007 ]
Nov 24 22:23:50 localhost ntpd_intres[1838]: host name not found: 1.debian.pool.ntp.org
Nov 24 22:24:10 localhost ntpd_intres[1838]: host name not found: 2.debian.pool.ntp.org
Nov 24 22:24:10 localhost rsyslogd-2007: action 'action 17' suspended, next retry is Fri Nov 24 22:24:40 2017 [try http://www.rsyslog.com/e/2007 ]
Nov 24 22:24:11 localhost pppd[1852]: Plugin rp-pppoe.so loaded.
Nov 24 22:24:11 localhost kernel: [  156.161946] PPP generic driver version 2.4.2
Nov 24 22:24:11 localhost pppd[1856]: pppd 2.4.6 started by root, uid 0
Nov 24 22:24:11 localhost kernel: [  156.260124] NET: Registered protocol family 24
Nov 24 22:24:11 localhost pppd[1856]: error sending pppoe packet: Network is down
Nov 24 22:24:11 localhost pppd[1856]: error receiving pppoe packet: Network is down
Nov 24 22:24:11 localhost systemd[1]: Reloading OpenBSD Secure Shell server.
Nov 24 22:24:11 localhost systemd[1]: Reloaded OpenBSD Secure Shell server.
Nov 24 22:24:16 localhost pppd[1856]: error sending pppoe packet: Network is down
Nov 24 22:24:26 localhost pppd[1856]: error sending pppoe packet: Network is down
Nov 24 22:24:30 localhost ntpd_intres[1838]: host name not found: 3.debian.pool.ntp.org

Je ne sais pas démarrer ppp en mode débug à la mano lol
Je débute et je ne sais pas faire grand faire.
Pourrais tu m’aider pour lancer ppp quand tu auras un peu de temps.
Merci en tout cas encore et encore

mattotop · Novembre 25, 2017, 11:40am

Je crois que c’est là et que c’est sur le fonctionnement de ta carte eth0 qu’est le problème, plutot que dans ta config.
Et là je m’aperçois que je ne me souviens plus comment on diagnostique un problème matériel sur la carte réseau…

De ce que j’ai vu, sur le Banana PI M1, c’est une carte realtek, donc à tous hasards, est ce que le paquet firmware-realtek est bien installé ?

Si ça ne suffit pas, que disent lspci et lsmod ?

mattotop · Novembre 25, 2017, 11:45am

Et la soudain une intuition.
Ca ne serait pas une question de câble rj45 droit au lieu d’un câble croisé?

PascalHambourg · Novembre 25, 2017, 12:11pm

A priori non, ip link montre que la liaison d’eth0 est active (LOWER_UP).

Par contre l’interface VLAN eth0.832 n’est pas activée. Il faut se méfier avec la méthode “manual” car elle n’active pas toujours l’interface.

ip link set eth0.832 up

domoticity · Novembre 25, 2017, 8:14pm

Hello
Merci pour ton aide
En effet en faisant la manip dite, j’enclenche le vlan.
J’ai essayé de faire de meme pour ppp0 ( créé dans mon fichier réseau interfaces)
Mais il me dit qu’il ne trouve pas le “device ppp0”

domoticity · Novembre 25, 2017, 8:17pm

Encore merci à toi
Alors j’ai bien le module realtek de lancé, mais j’ai quand meme fait une mise à jour
apt-get install firmware-realtek.

Ensuite dans le fichier /etc/modules j’ai ajouté ppp et pppoe, je ne les voyais quand je faisais lsmod.
Maintenant en faisant lsmod j’ai

root@diagbox:~# lsmod
Module                  Size  Used by
ipt_MASQUERADE         16384  1
nf_nat_masquerade_ipv4    16384  1 ipt_MASQUERADE
iptable_nat            16384  1
nf_nat_ipv4            16384  1 iptable_nat
nf_nat                 20480  2 nf_nat_masquerade_ipv4,nf_nat_ipv4
nf_conntrack_ipv4      16384  3
nf_defrag_ipv4         16384  1 nf_conntrack_ipv4
xt_conntrack           16384  1
nf_conntrack           77824  6 nf_conntrack_ipv4,ipt_MASQUERADE,nf_nat_masquerade_ipv4,xt_conntrack,nf_nat_ipv4,nf_nat
iptable_filter         16384  1
ip_tables              20480  2 iptable_filter,iptable_nat
x_tables               20480  4 ip_tables,iptable_filter,ipt_MASQUERADE,xt_conntrack
evdev                  20480  0
ir_lirc_codec          16384  0
lirc_dev               16384  1 ir_lirc_codec
sunxi_cir              16384  0
sun4i_ss               24576  0
cpufreq_dt             16384  0
uio_pdrv_genirq        16384  0
uio                    16384  1 uio_pdrv_genirq
pppoe                  20480  0
pppox                  16384  1 pppoe
ppp_generic            24576  2 pppox,pppoe
slhc                   16384  1 ppp_generic
8021q                  24576  0
garp                   16384  1 8021q
mrp                    16384  1 8021q
stp                    16384  1 garp
llc                    16384  2 garp,stp
bonding                90112  0
brcmfmac              147456  0
brcmutil               16384  1 brcmfmac
cfg80211              352256  1 brcmfmac
rfkill                 20480  2 cfg80211
fuse                   69632  1
pwrseq_simple          16384  1
realtek                16384  1


root@diagbox:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 02:44:07:0f:8f:d8 brd ff:ff:ff:ff:ff:ff
3: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 8a:8d:56:5e:74:c4 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 98:3b:16:c6:36:36 brd ff:ff:ff:ff:ff:ff
5: eth0.832@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 02:44:07:0f:8f:d8 brd ff:ff:ff:ff:ff:ff

mattotop · Novembre 25, 2017, 8:19pm

Et donc ça marche du coup ?

domoticity · Novembre 25, 2017, 8:35pm

Desole j’ai pas complété mon message lol.
Non toujours pareil.
apres avoir fait ifup ppp0, car ip link set ppp0 up ne prend pas
et quand je fait un ifconfig, je ne vois pas ppp0.

mattotop · Novembre 25, 2017, 9:58pm

Alors on va reprendre depuis le début…

Petite remarques annexes, d’abord:

c’est a priori inutile (voire sous performant) de forcer le chargement des modules dans /etc/modules, ils sont en général pour la majorité sensés se charger tout seuls en cas de besoin, et en les forçant, tu manque des éléments de diagnostic.
le ip link set eth0.832 up a marché parce que, quoi que DOWN, eth0.832 existait déjà dans ta pile IP, mais ppp0, qui n’avait encore jamais été sollicitée, n’existe pas encore, donc normal que quand tu essayes de la mettre UP, ça ne marche pas.

Bref, grand gourou réseau @PascalHambourg a dit que le montage manuel n’était pas fiable, donc tu vas remettre eth0 et eth0.832 en auto dans ton fstab, mais pas ppp0 pour l’instant, et tu bootes.
Théoriquement, tes interfaces eth0 et eth0.832 doivent être UP, mais on va vérifier qu’elles fonctionnent.
A priori (Pascal le confirmera), tu dois pouvoir voir si tu atteins l’autre bout de ta connexion fibre, en faisant un:
arping -b -I eth0 (un ping en broadcast).
Ca devrait je pense te renvoyer les macs présentes sur ton lien fibre.
Si ça ne te renvoie rien, ça devrait au moins avoir mis à jour ça dans ton cache arp, donc tu peux regarder ip neigh show ou tu trouveras un routeur avec une autre mac que ta carte eth0

Bref.
Si ça passe, dans une console, tu lances plog -qf pour surveiller ce qui se passe. Tu ne l’arrêtes pas.
Ensuite,DANS UNE AUTRE CONSOLE, tu lances ta connection avec pon, pas avec un ifup, et tu copies >UNIQUEMENT< les nouvelles lignes qui sont apparues dans la première console ou il y a le suivi de ton log.

PascalHambourg · Novembre 25, 2017, 10:56pm

“Grand gourou réseau” dit que les arguments de ta commande arping sont invalides. Tu voulais peut-être écrire -i et -B au lieu de -I et -b, et de toute façon je ne vois pas l’intérêt car arping utilise le protocole ARP qui fait de la résolution d’adresse IP en adresse MAC. D’une part je ne vois pas à quel titre une interface pourrait répondre à une requête ARP pour une adresse IP de broadcast, cela n’a rien à voir avec un ping ICMP en broadcast (auquel plus personne de sensé ne répond plus depuis longtemps par sécurité, donc aussi inutile). D’autre part, si ce qu’il y a à l’autre bout de la fibre est bien un concentrateur d’accès PPPoE, alors cela ne parle pas IP ni ARP. Pour finir, si c’est censé être sur le VLAN taggé 832 ça ne répondra pas si on envoie la requête sur l’interface eth0 non taggée.
La requête pour savoir s’il y a quelqu’un se ferait plutôt avec la commande suivante :

pppoe -A -I eth0.832

Petite remarque sur le fichier de conf pppd : on utilise soit le pty pppoe (userland), soit le plug-in rp-pppoe.so (kernel land), mais pas les deux en même temps.

PS : Il me semble qu’une de mes connaissances m’a dit que la fibre Orange utilisait plutôt DHCP et non PPPoE, mais ça dépend peut-être des endroits.

domoticity · Novembre 25, 2017, 11:09pm

@ mac eth0
HWaddr e6:99:5d:88:7b:30

Dans un premier temps, j’ai testé avec la configuration /etc/ppp/peers/fibre suivante

pty "/usr/sbin/pppoe -I eth0.832 -T 80 -m 1452"
noipdefault
hide-password
lcp-echo-interval 20
lcp-echo-failure 3
connect /bin/true
noauth
persist
mtu 1492
usepeerdns
defaultroute
noaccomp
default-asyncmap
plugin rp-pppoe.so eth0.832

remplacez fti/blabla par votre login orange :

user “fti/deqwbzk”

/etc/network/interfaces
#RESCUE
source /etc/network/interfaces.d/*

Local loopback

auto lo
iface lo inet loopback

#ETH0
auto eth0
allow-hotplug eth0
iface eth0 inet manual

#PROVIDER
auto eth0.832
iface eth0.832 inet manual

iface ppp0 inet ppp
provider fibre

#WIFI AP
auto wlan0
allow-hotplug wlan0
iface wlan0 inet static
address 10.0.0.1
netmask 255.255.255.0
network 10.0.0.0
gateway 10.0.0.1
broadcast 10.0.0.255
dns nameservers 8.8.8.8
hwaddress ether 98:3b:16:c6:36:36

#WIFI MANAGED
auto wlan1
allow-hotplug wlan1
iface wlan1 inet manual

root@diagbox:~# arping -b -I eth0 -c 3 8.8.4.4
ARPING 8.8.4.4 from 10.0.0.1 eth0
Sent 3 probes (3 broadcast(s))
Received 0 response(s)

root@diagbox:~# ip neigh show
8.8.8.8 dev wlan0 INCOMPLETE
10.0.0.150 dev wlan0 lladdr 6c:71:d9:cc:0c:9a REACHABLE

J’ai quand meme lancé pon fibre et le plog donne

diagbox@diagbox:~$ sudo plog -qf
Nov 25 23:48:25 localhost pppd[1779]: Plugin rp-pppoe.so loaded.
Nov 25 23:48:25 localhost pppd[1780]: pppd 2.4.6 started by root, uid 0
Nov 25 23:48:25 localhost pppd[1780]: error sending pppoe packet: Network is down
Nov 25 23:48:25 localhost pppd[1780]: error receiving pppoe packet: Network is down
Nov 25 23:48:30 localhost pppd[1780]: error sending pppoe packet: Network is down

/////////////////////////////////////////////////////////////////////
Deuxième test en changeant la conf /etc/ppp/peers/fibre
pty "/usr/sbin/pppoe -I eth0.832 -T 80 -m 1452"
noipdefault
hide-password
lcp-echo-interval 20
lcp-echo-failure 3
connect /bin/true
noauth
persist
mtu 1492
usepeerdns
defaultroute
noaccomp
default-asyncmap
plugin rp-pppoe.so eth0.832 <===== SUPPRIME

remplacez fti/blabla par votre login orange :

user “fti/deqwbzk”

Meme résultats qu’en haut sauf pour le plog -qf
diagbox@diagbox:~$ sudo plog -qf
Nov 25 23:54:05 localhost pppd[1776]: pppd 2.4.6 started by root, uid 0
Nov 25 23:54:05 localhost pppd[1776]: Serial connection established.
Nov 25 23:54:05 localhost pppd[1776]: Using interface ppp0
Nov 25 23:54:05 localhost pppd[1776]: Connect: ppp0 <–> /dev/pts/2
Nov 25 23:54:36 localhost pppd[1776]: LCP: timeout sending Config-Requests
Nov 25 23:54:36 localhost pppd[1776]: Connection terminated.
Nov 25 23:54:36 localhost pppd[1776]: Modem hangup