Freebox Player (Revolution / V6)

  • Status Nouveau
  • Percent Complete
    0%
  • Task Type Anomalie
  • Category Applications
  • Assigned To No-one
  • Operating System Freebox Player V6 (Revolution)
  • Severity High
  • Priority Very Low
  • Reported Version 1.3.18
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Freebox Player (Revolution / V6)
Opened by Y44p - 26/04/2019

FS#27050 - Plus de connexion Client VPN - Revolution v6 - Rev 1.3.5

Une des bugs de cette nouvelle rev parmi d’autres : Plus de connexion possible du client VPN.

L’etat de la Connexion VPN est : Deconnecté - Erreur interne.

Cela n’a rien à voir avec le VPN auquel je me connecte sans aucun problème via mes ordinateurs ni avec le réseau. C’est une erreur SW interne.

Il faut ajouter que je perds la liste des me VPN (liste vide) et qu’ils réapparaissent qq mn plus tard. Une fois la liste vide, il est impossible d’ajouter une nouvelle connexion.

les Logs :
2019-04-26 16:50:31 starting
2019-04-26 16:50:31 calling helper script at ‘/etc/fbxconnman/conn.pre-up’ 2019-04-26 16:50:31 l3 state change ‘l3_start’ ⇒ ‘l3_wait_preup_helper’ 2019-04-26 16:50:31 l3 state change ‘l3_wait_preup_helper’ ⇒ ‘l3_wait_stable’ 2019-04-26 16:50:31 openvpn: openvpn process died (159)
2019-04-26 16:50:31 l3 is now stable
2019-04-26 16:50:31 l3 does not fulfil config requirement
2019-04-26 16:50:31 l3 state change ‘l3_wait_stable’ ⇒ ‘l3_bring_down’ 2019-04-26 16:50:31 waiting for l3 providers to go down
2019-04-26 16:50:31 l3 state change ‘l3_bring_down’ ⇒ ‘l3_wait_down’ 2019-04-26 16:50:31 l3 state change ‘l3_wait_down’ ⇒ ‘l3_cleanup_start’ 2019-04-26 16:50:31 calling helper script at ‘/etc/fbxconnman/conn.post-down’ 2019-04-26 16:50:31 l3 state change ‘l3_cleanup_start’ ⇒ ‘l3_wait_postdown_helper’ 2019-04-26 16:50:31 l3 state change ‘l3_wait_postdown_helper’ ⇒ ‘l3_cleanup_finish’ 2019-04-26 16:50:31 l3 state change ‘l3_cleanup_finish’ ⇒ ‘l3_finished’ 2019-04-26 16:50:31 state change ‘wait_l3_up’ ⇒ ‘wait_l3_down’ 2019-04-26 16:50:31 l3 state change ‘l3_finished’ ⇒ ‘l3_down’ 2019-04-26 16:50:31 state is now DOWN
2019-04-26 16:50:31 state change ‘wait_l3_down’ ⇒ ‘l3_finished’ 2019-04-26 16:50:31 state change ‘l3_finished’ ⇒ ‘wait_l2_down’ 2019-04-26 16:50:31 l2 state change ‘l2_up’ ⇒ ‘l2_cleanup’ 2019-04-26 16:50:31 l2 state change ‘l2_cleanup’ ⇒ ‘l2_down’

J'ai exactement la même chose

2019-04-27 17:05:59 starting
2019-04-27 17:05:59 calling helper script at '/etc/fbxconnman/conn.pre-up'
2019-04-27 17:05:59 l3 state change 'l3_start' => 'l3_wait_preup_helper'
2019-04-27 17:05:59 l3 state change 'l3_wait_preup_helper' => 'l3_wait_stable'
2019-04-27 17:05:59 openvpn: openvpn process died (159)
2019-04-27 17:05:59 l3 is now stable
2019-04-27 17:05:59 l3 does not fulfil config requirement
2019-04-27 17:05:59 l3 state change 'l3_wait_stable' => 'l3_bring_down'
2019-04-27 17:05:59 waiting for l3 providers to go down
2019-04-27 17:05:59 l3 state change 'l3_bring_down' => 'l3_wait_down'
2019-04-27 17:05:59 l3 state change 'l3_wait_down' => 'l3_cleanup_start'
2019-04-27 17:05:59 calling helper script at '/etc/fbxconnman/conn.post-down'
2019-04-27 17:05:59 l3 state change 'l3_cleanup_start' => 'l3_wait_postdown_helper'
2019-04-27 17:05:59 l3 state change 'l3_wait_postdown_helper' => 'l3_cleanup_finish'
2019-04-27 17:05:59 l3 state change 'l3_cleanup_finish' => 'l3_finished'
2019-04-27 17:05:59 state change 'wait_l3_up' => 'wait_l3_down'
2019-04-27 17:05:59 l3 state change 'l3_finished' => 'l3_down'
2019-04-27 17:05:59 state is now DOWN
2019-04-27 17:05:59 state change 'wait_l3_down' => 'l3_finished'
2019-04-27 17:05:59 state change 'l3_finished' => 'wait_l2_down'
2019-04-27 17:05:59 l2 state change 'l2_up' => 'l2_cleanup'
2019-04-27 17:05:59 l2 state change 'l2_cleanup' => 'l2_down'
2019-04-27 17:05:59 state change 'wait_l2_down' => 'down'
2019-04-27 17:06:22 state change 'down' => 'wait_l2_up'
2019-04-27 17:06:22 l2 state change 'l2_down' => 'l2_up'
2019-04-27 17:06:22 state change 'wait_l2_up' => 'l2_up'
2019-04-27 17:06:22 state change 'l2_up' => 'wait_l3_up'
2019-04-27 17:06:22 l3 state change 'l3_down' => 'l3_start'

Bug corrigé dans la version 4.0.5.1 du freebox server.
Ticket à fermer

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing