Pages: 1 ... 19 20 21 22 23 [24] 25 26 27 28 29 ... 322   En bas

Auteur Sujet: OpenMPTCProuter : Agréger plusieurs lignes internet  (Lu 718787 fois)

0 Membres et 1 Invité sur ce sujet

Bidibulle

  • Abonné Free fibre
  • *
  • Messages: 179
  • CAEN (14)
OpenMPTCProuteur : agréger plusieurs lignes internet
« Réponse #276 le: 08 janvier 2019 à 17:08:04 »
Pour faire avancer le schmilblick, mes problèmes de DNS sont aussi au niveau des connections sftp (ca fonctionnait sans problème ce weekend)
Citer
Statut :   Connexion à xxxxx.fr:xxxx...
Réponse :   fzSftp started, protocol_version=4
Erreur :   ssh_init: Temporary failure in name resolution
Erreur :   Impossible d'établir une connexion au serveur
Statut :   Attente avant nouvel essai...
Erreur :   ssh_init: Name or service not known
Erreur :   Impossible d'établir une connexion au serveur

Une dizaine de fois le même message, et d'un seul coup ça passe.  :-\
IP archivée

Ycarus

  • Abonné MilkyWan
  • *
  • Messages: 837
  • Coligny (01) K-Net + Milkywan FTTH + Starlink
    • OpenMPTCProuter
OpenMPTCProuteur : agréger plusieurs lignes internet
« Réponse #277 le: 08 janvier 2019 à 17:11:36 »
Citation de: Bidibulle le 08 janvier 2019 à 17:08:04
Pour faire avancer le schmilblick, mes problèmes de DNS sont aussi au niveau des connections sftp (ca fonctionnait sans problème ce weekend)
Une dizaine de fois le même message, et d'un seul coup ça passe.  :-\
Tu sembles avoir un soucis niveau UDP.
Il faut voir si le VPN est utilisé : ip route sur OpenMPTCProuter via SSH, si la route par défaut est 10.255.255.1 c'est bon.
Il faut vérifier que Glorytun TCP est bien utilisé, dans le wizard->paramètres avancés.
Et faut voir dans les logs si il n'y a rien d'étrange.
IP archivée

Bidibulle

  • Abonné Free fibre
  • *
  • Messages: 179
  • CAEN (14)
OpenMPTCProuteur : agréger plusieurs lignes internet
« Réponse #278 le: 08 janvier 2019 à 17:40:37 »
merci de ta réponse !
Alors :
Citer
root@OpenMPTCProuter:~# ip route
default via 10.255.255.1 dev tun0
default via 192.168.10.1 dev wan1 metric 3
default via 192.168.11.1 dev wan2 metric 6
10.255.255.0/24 dev tun0 proto kernel scope link src 10.255.255.2
51.xx.xx.xx via 192.168.10.1 dev wan1 proto static metric 1
51.xx.xx.xx via 192.168.10.1 dev wan1 proto static metric 3
51.xx.xx.xx via 192.168.11.1 dev wan2 proto static metric 6
127.0.0.0/8 dev lo proto static scope link metric 1
192.168.10.0/24 dev wan1 proto static scope link metric 3
192.168.11.0/24 dev wan2 proto static scope link metric 6
Ca a l'air bon de ce coté là.

Citation de: Ycarus le 08 janvier 2019 à 17:11:36
Il faut vérifier que Glorytun TCP est bien utilisé, dans le wizard->paramètres avancés.
Dans la config avancée, il y a "Paramètres du VPN">"VPN par défaut" > et "Glorytun TCP" dans le menu déroulant. C'est bien cela qu'il faut vérifier ?

Dans les logs, je ne vois rien d'anormal. C'est plutôt du coté système ou noyau qu'il faut regarder ?
Code: [Sélectionner]
Tue Jan  8 16:28:18 2019 daemon.info glorytun[5741]: STOPPED tun0
Tue Jan  8 16:28:19 2019 daemon.err glorytun[5741]: 51.xx.xx.xx.65001: connected
Tue Jan  8 16:28:19 2019 daemon.info glorytun[5741]: STARTED tun0La connection au vpn qui se refait toutes les 10 minutes environ ? Normal non ?

IP archivée

Ycarus

  • Abonné MilkyWan
  • *
  • Messages: 837
  • Coligny (01) K-Net + Milkywan FTTH + Starlink
    • OpenMPTCProuter
OpenMPTCProuteur : agréger plusieurs lignes internet
« Réponse #279 le: 08 janvier 2019 à 17:44:13 »
Citation de: Bidibulle le 08 janvier 2019 à 17:40:37
merci de ta réponse !
Alors : Ca a l'air bon de ce coté là.
Dans la config avancée, il y a "Paramètres du VPN">"VPN par défaut" > et "Glorytun TCP" dans le menu déroulant. C'est bien cela qu'il faut vérifier ?

Dans les logs, je ne vois rien d'anormal. C'est plutôt du coté système ou noyau qu'il faut regarder ?
Code: [Sélectionner]
Tue Jan  8 16:28:18 2019 daemon.info glorytun[5741]: STOPPED tun0
Tue Jan  8 16:28:19 2019 daemon.err glorytun[5741]: 51.xx.xx.xx.65001: connected
Tue Jan  8 16:28:19 2019 daemon.info glorytun[5741]: STARTED tun0La connection au vpn qui se refait toutes les 10 minutes environ ? Normal non ?
Non pas normal du tout.
Après quand ça lag trop le VPS décide de la relancer.
Il faudrait faire un test de ping vers 10.255.255.1 depuis OpenMPTCProuter et inversement ping 10.255.255.2 depuis le VPS.
IP archivée

Bidibulle

  • Abonné Free fibre
  • *
  • Messages: 179
  • CAEN (14)
OpenMPTCProuteur : agréger plusieurs lignes internet
« Réponse #280 le: 08 janvier 2019 à 17:49:21 »
Depuis le VPS :
Code: [Sélectionner]
ping 10.255.255.2
PING 10.255.255.2 (10.255.255.2) 56(84) bytes of data.
64 bytes from 10.255.255.2: icmp_seq=1 ttl=64 time=35.1 ms
64 bytes from 10.255.255.2: icmp_seq=2 ttl=64 time=35.1 ms
64 bytes from 10.255.255.2: icmp_seq=3 ttl=64 time=34.7 ms
64 bytes from 10.255.255.2: icmp_seq=4 ttl=64 time=36.1 ms
64 bytes from 10.255.255.2: icmp_seq=5 ttl=64 time=44.6 ms
64 bytes from 10.255.255.2: icmp_seq=6 ttl=64 time=34.4 ms
64 bytes from 10.255.255.2: icmp_seq=7 ttl=64 time=30.8 ms
64 bytes from 10.255.255.2: icmp_seq=8 ttl=64 time=44.3 ms
64 bytes from 10.255.255.2: icmp_seq=9 ttl=64 time=31.3 ms
64 bytes from 10.255.255.2: icmp_seq=10 ttl=64 time=30.9 ms
64 bytes from 10.255.255.2: icmp_seq=11 ttl=64 time=31.7 ms
64 bytes from 10.255.255.2: icmp_seq=12 ttl=64 time=35.4 ms
64 bytes from 10.255.255.2: icmp_seq=13 ttl=64 time=38.0 ms
64 bytes from 10.255.255.2: icmp_seq=14 ttl=64 time=34.9 ms
^C
--- 10.255.255.2 ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 13020ms
rtt min/avg/max/mdev = 30.843/35.577/44.621/4.183 ms

Depuis OpenMPTCProuter :

Code: [Sélectionner]
ping 10.255.255.1
PING 10.255.255.1 (10.255.255.1) 56(84) bytes of data.
64 bytes from 10.255.255.1: icmp_req=1 ttl=64 time=35.3 ms
64 bytes from 10.255.255.1: icmp_req=2 ttl=64 time=34.7 ms
64 bytes from 10.255.255.1: icmp_req=3 ttl=64 time=35.4 ms
64 bytes from 10.255.255.1: icmp_req=4 ttl=64 time=35.6 ms
64 bytes from 10.255.255.1: icmp_req=5 ttl=64 time=35.6 ms
64 bytes from 10.255.255.1: icmp_req=6 ttl=64 time=35.7 ms
64 bytes from 10.255.255.1: icmp_req=7 ttl=64 time=34.8 ms
64 bytes from 10.255.255.1: icmp_req=8 ttl=64 time=34.7 ms
64 bytes from 10.255.255.1: icmp_req=9 ttl=64 time=34.8 ms
^C
--- 10.255.255.1 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8013ms
rtt min/avg/max/mdev = 34.770/35.223/35.717/0.460 ms
IP archivée

Ycarus

  • Abonné MilkyWan
  • *
  • Messages: 837
  • Coligny (01) K-Net + Milkywan FTTH + Starlink
    • OpenMPTCProuter
OpenMPTCProuteur : agréger plusieurs lignes internet
« Réponse #281 le: 08 janvier 2019 à 17:56:02 »
Citation de: Bidibulle le 08 janvier 2019 à 17:49:21
Depuis le VPS :
Code: [Sélectionner]
ping 10.255.255.2
PING 10.255.255.2 (10.255.255.2) 56(84) bytes of data.
64 bytes from 10.255.255.2: icmp_seq=1 ttl=64 time=35.1 ms
64 bytes from 10.255.255.2: icmp_seq=2 ttl=64 time=35.1 ms
64 bytes from 10.255.255.2: icmp_seq=3 ttl=64 time=34.7 ms
64 bytes from 10.255.255.2: icmp_seq=4 ttl=64 time=36.1 ms
64 bytes from 10.255.255.2: icmp_seq=5 ttl=64 time=44.6 ms
64 bytes from 10.255.255.2: icmp_seq=6 ttl=64 time=34.4 ms
64 bytes from 10.255.255.2: icmp_seq=7 ttl=64 time=30.8 ms
64 bytes from 10.255.255.2: icmp_seq=8 ttl=64 time=44.3 ms
64 bytes from 10.255.255.2: icmp_seq=9 ttl=64 time=31.3 ms
64 bytes from 10.255.255.2: icmp_seq=10 ttl=64 time=30.9 ms
64 bytes from 10.255.255.2: icmp_seq=11 ttl=64 time=31.7 ms
64 bytes from 10.255.255.2: icmp_seq=12 ttl=64 time=35.4 ms
64 bytes from 10.255.255.2: icmp_seq=13 ttl=64 time=38.0 ms
64 bytes from 10.255.255.2: icmp_seq=14 ttl=64 time=34.9 ms
^C
--- 10.255.255.2 ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 13020ms
rtt min/avg/max/mdev = 30.843/35.577/44.621/4.183 ms

Depuis OpenMPTCProuter :

Code: [Sélectionner]
ping 10.255.255.1
PING 10.255.255.1 (10.255.255.1) 56(84) bytes of data.
64 bytes from 10.255.255.1: icmp_req=1 ttl=64 time=35.3 ms
64 bytes from 10.255.255.1: icmp_req=2 ttl=64 time=34.7 ms
64 bytes from 10.255.255.1: icmp_req=3 ttl=64 time=35.4 ms
64 bytes from 10.255.255.1: icmp_req=4 ttl=64 time=35.6 ms
64 bytes from 10.255.255.1: icmp_req=5 ttl=64 time=35.6 ms
64 bytes from 10.255.255.1: icmp_req=6 ttl=64 time=35.7 ms
64 bytes from 10.255.255.1: icmp_req=7 ttl=64 time=34.8 ms
64 bytes from 10.255.255.1: icmp_req=8 ttl=64 time=34.7 ms
64 bytes from 10.255.255.1: icmp_req=9 ttl=64 time=34.8 ms
^C
--- 10.255.255.1 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8013ms
rtt min/avg/max/mdev = 34.770/35.223/35.717/0.460 ms
Donc tout semble ok à ce niveau la.
Le ping d'une IP (autre que celle du VPS) reste normal ?
En DNS tu utilises l'IP d'OpenMPTCProuter ou autre chose ?
IP archivée

Vinc32

  • Abonné Free adsl
  • *
  • Messages: 52
  • Savenay 44
OpenMPTCProuteur : agréger plusieurs lignes internet
« Réponse #282 le: 08 janvier 2019 à 18:02:31 »
Tue Jan  8 18:01:11 2019 kern.err kernel: [  292.522655] mptcp_close: Close of meta_sk with tok 0x82ddc7f6
Tue Jan  8 18:01:11 2019 kern.err kernel: [  292.536484] mptcp_del_sock: Removing subsock tok 0x40b2053f pi:1 state 7 is_meta? 0
Tue Jan  8 18:01:11 2019 kern.err kernel: [  292.536706] mptcp_sock_destruct destroying meta-sk token 0x40b2053f
Tue Jan  8 18:01:11 2019 kern.err kernel: [  292.537457] mptcp_del_sock: Removing subsock tok 0x82ddc7f6 pi:1 state 7 is_meta? 0
Tue Jan  8 18:01:12 2019 kern.err kernel: [  292.571419] mptcp_del_sock: Removing subsock tok 0x82ddc7f6 pi:2 state 7 is_meta? 0
Tue Jan  8 18:01:12 2019 kern.err kernel: [  292.571641] mptcp_sock_destruct destroying meta-sk token 0x82ddc7f6
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.196480] mptcp_alloc_mpcb: created mpcb with token 0x19bc643c
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.196632] mptcp_add_sock: token 0x19bc643c pi 1, src_addr:192.168.10.10:50811 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.212391] mptcp_add_sock: token 0x19bc643c pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.212618] mptcp_init4_subsockets: token 0x19bc643c pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.213263] mptcp_alloc_mpcb: created mpcb with token 0x204a194f
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.213401] mptcp_add_sock: token 0x204a194f pi 1, src_addr:192.168.10.10:50813 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.228097] mptcp_alloc_mpcb: created mpcb with token 0xc3d597a5
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.228239] mptcp_add_sock: token 0xc3d597a5 pi 1, src_addr:192.168.10.10:50815 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.230757] mptcp_add_sock: token 0x204a194f pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.230981] mptcp_init4_subsockets: token 0x204a194f pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.346095] mptcp_alloc_mpcb: created mpcb with token 0x1a6c3d83
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.346242] mptcp_add_sock: token 0x1a6c3d83 pi 1, src_addr:192.168.10.10:50817 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.378347] mptcp_add_sock: token 0xc3d597a5 pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.378574] mptcp_init4_subsockets: token 0xc3d597a5 pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.396358] mptcp_alloc_mpcb: created mpcb with token 0x112df68a
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.396498] mptcp_add_sock: token 0x112df68a pi 1, src_addr:192.168.10.10:50819 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.596074] mptcp_add_sock: token 0x112df68a pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.596305] mptcp_init4_subsockets: token 0x112df68a pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.609631] mptcp_alloc_mpcb: created mpcb with token 0xac39e949
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.609771] mptcp_add_sock: token 0xac39e949 pi 1, src_addr:192.168.10.10:50821 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.615526] mptcp_alloc_mpcb: created mpcb with token 0x35cfa574
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.615665] mptcp_add_sock: token 0x35cfa574 pi 1, src_addr:192.168.10.10:50823 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.628887] mptcp_add_sock: token 0xac39e949 pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.629112] mptcp_init4_subsockets: token 0xac39e949 pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.734724] mptcp_add_sock: token 0x35cfa574 pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.734952] mptcp_init4_subsockets: token 0x35cfa574 pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:15 2019 kern.err kernel: [  296.384550] mptcp_alloc_mpcb: created mpcb with token 0x547eb900
Tue Jan  8 18:01:15 2019 kern.err kernel: [  296.384697] mptcp_add_sock: token 0x547eb900 pi 1, src_addr:192.168.10.10:50825 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:15 2019 kern.err kernel: [  296.405016] mptcp_add_sock: token 0x547eb900 pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:15 2019 kern.err kernel: [  296.405242] mptcp_init4_subsockets: token 0x547eb900 pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:16 2019 kern.err kernel: [  296.559334] mptcp_alloc_mpcb: created mpcb with token 0xb5e5c5c5
Tue Jan  8 18:01:16 2019 kern.err kernel: [  296.559478] mptcp_add_sock: token 0xb5e5c5c5 pi 1, src_addr:192.168.10.10:50827 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:16 2019 kern.err kernel: [  296.575345] mptcp_add_sock: token 0xb5e5c5c5 pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:16 2019 kern.err kernel: [  296.575572] mptcp_init4_subsockets: token 0xb5e5c5c5 pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:16 2019 kern.err kernel: [  297.075369] mptcp_close: Close of meta_sk with tok 0xb5e5c5c5
Tue Jan  8 18:01:16 2019 kern.err kernel: [  297.103202] mptcp_del_sock: Removing subsock tok 0xb5e5c5c5 pi:1 state 7 is_meta? 0
Tue Jan  8 18:01:16 2019 kern.err kernel: [  297.132742] mptcp_del_sock: Removing subsock tok 0xb5e5c5c5 pi:2 state 7 is_meta? 0
Tue Jan  8 18:01:16 2019 kern.err kernel: [  297.132966] mptcp_sock_destruct destroying meta-sk token 0xb5e5c5c5
Tue Jan  8 18:01:18 2019 kern.err kernel: [  299.253901] mptcp_add_sock: token 0x1a6c3d83 pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:18 2019 kern.err kernel: [  299.254134] mptcp_init4_subsockets: token 0x1a6c3d83 pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:18 2019 kern.err kernel: [  299.389542] mptcp_close: Close of meta_sk with tok 0x1a6c3d83
Tue Jan  8 18:01:18 2019 kern.err kernel: [  299.417531] mptcp_del_sock: Removing subsock tok 0x1a6c3d83 pi:1 state 7 is_meta? 0
Tue Jan  8 18:01:18 2019 kern.err kernel: [  299.451860] mptcp_del_sock: Removing subsock tok 0x1a6c3d83 pi:2 state 7 is_meta? 0
Tue Jan  8 18:01:18 2019 kern.err kernel: [  299.452079] mptcp_sock_destruct destroying meta-sk token 0x1a6c3d83
Tue Jan  8 18:01:19 2019 kern.err kernel: [  299.577483] mptcp_alloc_mpcb: created mpcb with token 0x85060bbd
Tue Jan  8 18:01:19 2019 kern.err kernel: [  299.577628] mptcp_add_sock: token 0x85060bbd pi 1, src_addr:192.168.10.10:50829 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:19 2019 kern.err kernel: [  299.702144] mptcp_add_sock: token 0x85060bbd pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:19 2019 kern.err kernel: [  299.702373] mptcp_init4_subsockets: token 0x85060bbd pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:19 2019 kern.err kernel: [  300.526285] mptcp_alloc_mpcb: created mpcb with token 0xde73a64f
Tue Jan  8 18:01:19 2019 kern.err kernel: [  300.526430] mptcp_add_sock: token 0xde73a64f pi 1, src_addr:192.168.10.10:50831 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:20 2019 kern.err kernel: [  300.592778] mptcp_add_sock: token 0xde73a64f pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:20 2019 kern.err kernel: [  300.593008] mptcp_init4_subsockets: token 0xde73a64f pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:21 2019 kern.err kernel: [  302.352147] mptcp_alloc_mpcb: created mpcb with token 0x7be72928
Tue Jan  8 18:01:21 2019 kern.err kernel: [  302.352295] mptcp_add_sock: token 0x7be72928 pi 1, src_addr:192.168.10.10:50833 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:21 2019 kern.err kernel: [  302.418082] mptcp_close: Close of meta_sk with tok 0x7be72928
Tue Jan  8 18:01:21 2019 kern.err kernel: [  302.431508] mptcp_del_sock: Removing subsock tok 0x7be72928 pi:1 state 7 is_meta? 0
Tue Jan  8 18:01:21 2019 kern.err kernel: [  302.431743] mptcp_sock_destruct destroying meta-sk token 0x7be72928


Quelqu'un peut m'expliquer ?
IP archivée

Ycarus

  • Abonné MilkyWan
  • *
  • Messages: 837
  • Coligny (01) K-Net + Milkywan FTTH + Starlink
    • OpenMPTCProuter
OpenMPTCProuteur : agréger plusieurs lignes internet
« Réponse #283 le: 08 janvier 2019 à 18:11:02 »
Citation de: Vinc32 le 08 janvier 2019 à 18:02:31
Tue Jan  8 18:01:11 2019 kern.err kernel: [  292.522655] mptcp_close: Close of meta_sk with tok 0x82ddc7f6
Tue Jan  8 18:01:11 2019 kern.err kernel: [  292.536484] mptcp_del_sock: Removing subsock tok 0x40b2053f pi:1 state 7 is_meta? 0
Tue Jan  8 18:01:11 2019 kern.err kernel: [  292.536706] mptcp_sock_destruct destroying meta-sk token 0x40b2053f
Tue Jan  8 18:01:11 2019 kern.err kernel: [  292.537457] mptcp_del_sock: Removing subsock tok 0x82ddc7f6 pi:1 state 7 is_meta? 0
Tue Jan  8 18:01:12 2019 kern.err kernel: [  292.571419] mptcp_del_sock: Removing subsock tok 0x82ddc7f6 pi:2 state 7 is_meta? 0
Tue Jan  8 18:01:12 2019 kern.err kernel: [  292.571641] mptcp_sock_destruct destroying meta-sk token 0x82ddc7f6
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.196480] mptcp_alloc_mpcb: created mpcb with token 0x19bc643c
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.196632] mptcp_add_sock: token 0x19bc643c pi 1, src_addr:192.168.10.10:50811 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.212391] mptcp_add_sock: token 0x19bc643c pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.212618] mptcp_init4_subsockets: token 0x19bc643c pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.213263] mptcp_alloc_mpcb: created mpcb with token 0x204a194f
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.213401] mptcp_add_sock: token 0x204a194f pi 1, src_addr:192.168.10.10:50813 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.228097] mptcp_alloc_mpcb: created mpcb with token 0xc3d597a5
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.228239] mptcp_add_sock: token 0xc3d597a5 pi 1, src_addr:192.168.10.10:50815 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.230757] mptcp_add_sock: token 0x204a194f pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.230981] mptcp_init4_subsockets: token 0x204a194f pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.346095] mptcp_alloc_mpcb: created mpcb with token 0x1a6c3d83
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.346242] mptcp_add_sock: token 0x1a6c3d83 pi 1, src_addr:192.168.10.10:50817 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.378347] mptcp_add_sock: token 0xc3d597a5 pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.378574] mptcp_init4_subsockets: token 0xc3d597a5 pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.396358] mptcp_alloc_mpcb: created mpcb with token 0x112df68a
Tue Jan  8 18:01:14 2019 kern.err kernel: [  295.396498] mptcp_add_sock: token 0x112df68a pi 1, src_addr:192.168.10.10:50819 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.596074] mptcp_add_sock: token 0x112df68a pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.596305] mptcp_init4_subsockets: token 0x112df68a pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.609631] mptcp_alloc_mpcb: created mpcb with token 0xac39e949
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.609771] mptcp_add_sock: token 0xac39e949 pi 1, src_addr:192.168.10.10:50821 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.615526] mptcp_alloc_mpcb: created mpcb with token 0x35cfa574
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.615665] mptcp_add_sock: token 0x35cfa574 pi 1, src_addr:192.168.10.10:50823 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.628887] mptcp_add_sock: token 0xac39e949 pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.629112] mptcp_init4_subsockets: token 0xac39e949 pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.734724] mptcp_add_sock: token 0x35cfa574 pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:15 2019 kern.err kernel: [  295.734952] mptcp_init4_subsockets: token 0x35cfa574 pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:15 2019 kern.err kernel: [  296.384550] mptcp_alloc_mpcb: created mpcb with token 0x547eb900
Tue Jan  8 18:01:15 2019 kern.err kernel: [  296.384697] mptcp_add_sock: token 0x547eb900 pi 1, src_addr:192.168.10.10:50825 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:15 2019 kern.err kernel: [  296.405016] mptcp_add_sock: token 0x547eb900 pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:15 2019 kern.err kernel: [  296.405242] mptcp_init4_subsockets: token 0x547eb900 pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:16 2019 kern.err kernel: [  296.559334] mptcp_alloc_mpcb: created mpcb with token 0xb5e5c5c5
Tue Jan  8 18:01:16 2019 kern.err kernel: [  296.559478] mptcp_add_sock: token 0xb5e5c5c5 pi 1, src_addr:192.168.10.10:50827 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:16 2019 kern.err kernel: [  296.575345] mptcp_add_sock: token 0xb5e5c5c5 pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:16 2019 kern.err kernel: [  296.575572] mptcp_init4_subsockets: token 0xb5e5c5c5 pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:16 2019 kern.err kernel: [  297.075369] mptcp_close: Close of meta_sk with tok 0xb5e5c5c5
Tue Jan  8 18:01:16 2019 kern.err kernel: [  297.103202] mptcp_del_sock: Removing subsock tok 0xb5e5c5c5 pi:1 state 7 is_meta? 0
Tue Jan  8 18:01:16 2019 kern.err kernel: [  297.132742] mptcp_del_sock: Removing subsock tok 0xb5e5c5c5 pi:2 state 7 is_meta? 0
Tue Jan  8 18:01:16 2019 kern.err kernel: [  297.132966] mptcp_sock_destruct destroying meta-sk token 0xb5e5c5c5
Tue Jan  8 18:01:18 2019 kern.err kernel: [  299.253901] mptcp_add_sock: token 0x1a6c3d83 pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:18 2019 kern.err kernel: [  299.254134] mptcp_init4_subsockets: token 0x1a6c3d83 pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:18 2019 kern.err kernel: [  299.389542] mptcp_close: Close of meta_sk with tok 0x1a6c3d83
Tue Jan  8 18:01:18 2019 kern.err kernel: [  299.417531] mptcp_del_sock: Removing subsock tok 0x1a6c3d83 pi:1 state 7 is_meta? 0
Tue Jan  8 18:01:18 2019 kern.err kernel: [  299.451860] mptcp_del_sock: Removing subsock tok 0x1a6c3d83 pi:2 state 7 is_meta? 0
Tue Jan  8 18:01:18 2019 kern.err kernel: [  299.452079] mptcp_sock_destruct destroying meta-sk token 0x1a6c3d83
Tue Jan  8 18:01:19 2019 kern.err kernel: [  299.577483] mptcp_alloc_mpcb: created mpcb with token 0x85060bbd
Tue Jan  8 18:01:19 2019 kern.err kernel: [  299.577628] mptcp_add_sock: token 0x85060bbd pi 1, src_addr:192.168.10.10:50829 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:19 2019 kern.err kernel: [  299.702144] mptcp_add_sock: token 0x85060bbd pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:19 2019 kern.err kernel: [  299.702373] mptcp_init4_subsockets: token 0x85060bbd pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:19 2019 kern.err kernel: [  300.526285] mptcp_alloc_mpcb: created mpcb with token 0xde73a64f
Tue Jan  8 18:01:19 2019 kern.err kernel: [  300.526430] mptcp_add_sock: token 0xde73a64f pi 1, src_addr:192.168.10.10:50831 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:20 2019 kern.err kernel: [  300.592778] mptcp_add_sock: token 0xde73a64f pi 2, src_addr:0.0.0.0:0 dst_addr:0.0.0.0:0, cnt_subflows now 2
Tue Jan  8 18:01:20 2019 kern.err kernel: [  300.593008] mptcp_init4_subsockets: token 0xde73a64f pi 2 src_addr:192.168.11.10:0 dst_addr:51.15.235.30:65101 ifidx: 8
Tue Jan  8 18:01:21 2019 kern.err kernel: [  302.352147] mptcp_alloc_mpcb: created mpcb with token 0x7be72928
Tue Jan  8 18:01:21 2019 kern.err kernel: [  302.352295] mptcp_add_sock: token 0x7be72928 pi 1, src_addr:192.168.10.10:50833 dst_addr:51.15.235.30:65101, cnt_subflows now 1
Tue Jan  8 18:01:21 2019 kern.err kernel: [  302.418082] mptcp_close: Close of meta_sk with tok 0x7be72928
Tue Jan  8 18:01:21 2019 kern.err kernel: [  302.431508] mptcp_del_sock: Removing subsock tok 0x7be72928 pi:1 state 7 is_meta? 0
Tue Jan  8 18:01:21 2019 kern.err kernel: [  302.431743] mptcp_sock_destruct destroying meta-sk token 0x7be72928


Quelqu'un peut m'expliquer ?
Tu as activé le debug pour MPTCP ? Dans Réseau->MPTCP Multipath Debug.
IP archivée

Bidibulle

  • Abonné Free fibre
  • *
  • Messages: 179
  • CAEN (14)
OpenMPTCProuteur : agréger plusieurs lignes internet
« Réponse #284 le: 08 janvier 2019 à 18:13:24 »
Citation de: Ycarus le 08 janvier 2019 à 17:56:02
Donc tout semble ok à ce niveau la.
Le ping d'une IP (autre que celle du VPS) reste normal ?
En DNS tu utilises l'IP d'OpenMPTCProuter ou autre chose ?
Là, le ping vers google.com par exemple refonctionne correctement, que ce soit du routeur ou d'un pc. C'est aléatoire.
Pour les DNS j'ai rien changé coté routeur, et coté client que ce soit configuré avec l'ip du routeur, en 8.8.8.8, ou en auto (smartphone/tablette), quand ca lag ou que ca me renvoie des erreurs de DNS, ca le fait sur n'importe quel appareil/machine.
IP archivée

Vinc32

  • Abonné Free adsl
  • *
  • Messages: 52
  • Savenay 44
OpenMPTCProuteur : agréger plusieurs lignes internet
« Réponse #285 le: 08 janvier 2019 à 18:17:50 »
Citation de: Ycarus le 08 janvier 2019 à 18:11:02
Tu as activé le debug pour MPTCP ? Dans Réseau->MPTCP Multipath Debug.

Effectivement il était activé. Désolé pour ce post  :P Tout est rentré dans l'ordre hors-mis l'IPV6 qui ne passe pas par le VPN ???
IP archivée

Bidibulle

  • Abonné Free fibre
  • *
  • Messages: 179
  • CAEN (14)
OpenMPTCProuteur : agréger plusieurs lignes internet
« Réponse #286 le: 08 janvier 2019 à 18:19:10 »
Ha tiens :
Code: [Sélectionner]
root@OpenMPTCProuter:~# ping google.com
PING google.com (216.58.206.238) 56(84) bytes of data.
64 bytes from par10s34-in-f14.1e100.net (216.58.206.238): icmp_req=1 ttl=50 time=4687 ms
64 bytes from par10s34-in-f14.1e100.net (216.58.206.238): icmp_req=2 ttl=50 time=4320 ms
64 bytes from par10s34-in-f14.1e100.net (216.58.206.238): icmp_req=3 ttl=50 time=4163 ms
64 bytes from par10s34-in-f14.1e100.net (216.58.206.238): icmp_req=4 ttl=50 time=4386 ms
64 bytes from par10s34-in-f14.1e100.net (216.58.206.238): icmp_req=5 ttl=50 time=4164 ms
64 bytes from par10s34-in-f14.1e100.net (216.58.206.238): icmp_req=6 ttl=50 time=3915 ms
64 bytes from par10s34-in-f14.1e100.net (216.58.206.238): icmp_req=7 ttl=50 time=3753 ms
^C
--- google.com ping statistics ---
10 packets transmitted, 7 received, 30% packet loss, time 9078ms
rtt min/avg/max/mdev = 3753.751/4198.895/4687.385/285.179 ms, pipe 5
Le seul truc anormal, c'est que ça upload sur le wan 2 (environ à 3Mb/s sur les 4 disponibles).
IP archivée

Bidibulle

  • Abonné Free fibre
  • *
  • Messages: 179
  • CAEN (14)
OpenMPTCProuteur : agréger plusieurs lignes internet
« Réponse #287 le: 08 janvier 2019 à 18:20:59 »
Et juste après :
Code: [Sélectionner]
Tue Jan  8 17:18:10 2019 user.notice post-tracking-post-tracking: omrvpn down. Replace default route by 192.168.10.1 dev wan1
Tue Jan  8 17:18:10 2019 user.notice post-tracking-post-tracking: omrvpn down because gateway down
Tue Jan  8 17:18:38 2019 user.notice post-tracking-post-tracking: Tunnel up : Replace default route by 10.255.255.1 dev tun0
Tue Jan  8 17:19:43 2019 user.notice post-tracking-post-tracking: omrvpn down. Replace default route by 192.168.10.1 dev wan1
Tue Jan  8 17:19:43 2019 user.notice post-tracking-post-tracking: omrvpn down because gateway down
Tue Jan  8 17:20:03 2019 user.notice post-tracking-post-tracking: Tunnel up : Replace default route by 10.255.255.1 dev tun0
Edit :
Code: [Sélectionner]
Tue Jan  8 17:21:40 2019 user.notice post-tracking-post-tracking: omrvpn down. Replace default route by 192.168.10.1 dev wan1
Tue Jan  8 17:21:40 2019 user.notice post-tracking-post-tracking: omrvpn down because gateway down
Tue Jan  8 17:22:03 2019 user.notice post-tracking-post-tracking: Tunnel up : Replace default route by 10.255.255.1 dev tun0
Tue Jan  8 17:22:07 2019 daemon.info glorytun[5117]: STOPPED tun0
Tue Jan  8 17:22:08 2019 daemon.err glorytun[5117]: 51.xx.xx.xx.65001: connected
Tue Jan  8 17:22:08 2019 daemon.info glorytun[5117]: STARTED tun0Edit2 :
Code: [Sélectionner]
root@OpenMPTCProuter:~# ping google.com
ping: unknown host google.com
Code: [Sélectionner]
Tue Jan  8 17:24:28 2019 user.notice post-tracking-post-tracking: omrvpn down. Replace default route by 192.168.10.1 dev wan1
Tue Jan  8 17:24:28 2019 user.notice post-tracking-post-tracking: omrvpn down because gateway down
Tue Jan  8 17:24:52 2019 user.notice post-tracking-post-tracking: Tunnel up : Replace default route by 10.255.255.1 dev tun0
Tue Jan  8 17:24:58 2019 user.notice post-tracking-post-tracking: Get status and settings for wan2...
Tue Jan  8 17:25:51 2019 user.notice post-tracking-post-tracking: Get status and settings for wan2... Done
Tue Jan  8 17:26:51 2019 user.notice post-tracking-post-tracking: omrvpn down. Replace default route by 192.168.10.1 dev wan1
Tue Jan  8 17:26:51 2019 user.notice post-tracking-post-tracking: omrvpn down because gateway down
Tue Jan  8 17:27:11 2019 user.notice post-tracking-post-tracking: Tunnel up : Replace default route by 10.255.255.1 dev tun0
Je suppose que ce n'est pas normal... ? ???
IP archivée
Pages: 1 ... 19 20 21 22 23 [24] 25 26 27 28 29 ... 322   En haut