My client VPN on Freebox server is not logging anymore

Hi,
I'm leaving in France, and using a well-known internet provider FREE.
They have built a box that is not only a router, but also a nas, blue-ray, phone server, but also a torrent server. 
it is based on Linux, but as a user, I have no access to the OS it self.

You need also to know that Frrebox OS is not able to retrieve the certificate by inclusion : so I had to copy and paste it in the configuration fils, before lording it in the Freebox.(and removing the ca and crt lines), as explained in en french forum.

In February, I tested PIA for one month, by "declaring" PIA as mys client VPN for the torrents downloads.
It worked perfectly.
So I decided to buy a one year .subscription, beginning of March.
During March no issue.

Since two weeks, the torrents I was asking were locked.
I started to analyse the issue, and I discover that there where an error in the VPN connection (we can see the log in Freebox console)


....
2017-04-17 17:39:01 openvpn: output: Mon Apr 17 17:39:01 2017 [b4cb369bb63585dc91259400f5bd306d] Peer Connection Initiated with [AF_INET]209.95.50.16:1198
2017-04-17 17:39:02 openvpn: rx: >STATE:1492443542,GET_CONFIG,,,,,,0
2017-04-17 17:39:02 openvpn: output: Mon Apr 17 17:39:02 2017 MANAGEMENT: >STATE:1492443542,GET_CONFIG,,,,,,0
2017-04-17 17:39:03 openvpn: output: Mon Apr 17 17:39:03 2017 SENT CONTROL [b4cb369bb63585dc91259400f5bd306d]: 'PUSH_REQUEST' (status=1)
2017-04-17 17:39:03 openvpn: rx: >PASSWORD:Auth-Token:GKq7dOuRy6ZznZXz4aJUC5BB6mA3NZ2xmidTYtHurhA=
2017-04-17 17:39:03 openvpn: asked for unsupported password
2017-04-17 17:39:03 l3 is now stable
2017-04-17 17:39:03 l3 does not fulfil config requirement
2017-04-17 17:39:03 l3 state change 'l3_wait_stable' => 'l3_bring_down'
2017-04-17 17:39:03 waiting for l3 providers to go down
2017-04-17 17:39:03 l3 state change 'l3_bring_down' => 'l3_wait_down'
2017-04-17 17:39:03 l3 state change 'l3_wait_down' => 'l3_cleanup_start'
2017-04-17 17:39:03 calling helper script at '/etc/fbxconnman/conn.post-down'
2017-04-17 17:39:03 l3 state change 'l3_cleanup_start' => 'l3_wait_postdown_helper'
2017-04-17 17:39:03 openvpn: output: Mon Apr 17 17:39:03 2017 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 209.222.18.222,dhcp-option DNS 209.222.18.218,ping 10,comp-lzo no,route 10.88.10.1,topology net30,ifconfig 10.88.10.6 10.88.10.5,auth-token GKq7dOuRy6ZznZXz4aJUC5BB6mA3NZ2xmidTYtHurhA='
2017-04-17 17:39:03 openvpn: output: Mon Apr 17 17:39:03 2017 OPTIONS IMPORT: timers and/or timeouts modified
2017-04-17 17:39:03 openvpn: output: Mon Apr 17 17:39:03 2017 OPTIONS IMPORT: LZO parms modified
2017-04-17 17:39:03 openvpn: output: Mon Apr 17 17:39:03 2017 OPTIONS IMPORT: --ifconfig/up options modified
2017-04-17 17:39:03 openvpn: output: Mon Apr 17 17:39:03 2017 OPTIONS IMPORT: route options modified
2017-04-17 17:39:03 openvpn: output: Mon Apr 17 17:39:03 2017 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
2017-04-17 17:39:03 openvpn: output: Mon Apr 17 17:39:03 2017 ROUTE: default_gateway=UNDEF
2017-04-17 17:39:03 openvpn: output: Mon Apr 17 17:39:03 2017 Initialization Sequence Completed
2017-04-17 17:39:03 openvpn: output: Mon Apr 17 17:39:03 2017 MANAGEMENT: >STATE:1492443543,CONNECTED,SUCCESS,10.88.10.6,209.95.50.16,209.222.18.218,209.222.18.222,1500
2017-04-17 17:39:03 l3 state change 'l3_wait_postdown_helper' => 'l3_cleanup_finish'
2017-04-17 17:39:03 l3 state change 'l3_cleanup_finish' => 'l3_finished'
2017-04-17 17:39:03 state change 'wait_l3_up' => 'wait_l3_down'
2017-04-17 17:39:03 l3 state change 'l3_finished' => 'l3_down'
2017-04-17 17:39:03 state is now DOWN
2017-04-17 17:39:03 state change 'wait_l3_down' => 'l3_finished'
2017-04-17 17:39:03 state change 'l3_finished' => 'wait_l2_down'
2017-04-17 17:39:03 l2 state change 'l2_up' => 'l2_cleanup'
2017-04-17 17:39:03 l2 state change 'l2_cleanup' => 'l2_down'
2017-04-17 17:39:03 state change 'wait_l2_down' => 'down'

This problem is the same if I use New-York Or Norway script.

With My PC on windows 7, or with my Android Tablet, or Phones, it works.

The configuration file (I removed the certificate)

client
dev tun
proto udp
remote no.privateinternetaccess.com 1198
resolv-retry infinite
nobind
persist-key
persist-tun
cipher aes-128-cbc
auth sha1
tls-client
remote-cert-tls server
auth-user-pass
comp-lzo
script-security 2
verb 3
reneg-sec 0
<ca>
-----BEGIN CERTIFICATE-----
MIIFqzRiU....
-----END CERTIFICATE-----
</ca>


Again, it was working before, and I did nothing on the freebox config (and no new version recently).

So if "anybody there can listen to my story", I would really appreciate !
Thanks in advance.
Fred

Comments

  • I have the exact same issue with the same Internet provider. Just to mention it: Free is used by at least 25% of french ppl so it is not a small provider.
  • Hello, I am having the exact same problem. However, it might be coming from the Freebox itself.
     https://dev.freebox.fr/bugs/task/21432

    Hopefully, it will be resolved soon. :)


  • I have exactly the same problem - It just happened an Freebox revolution update 3.4.1, but nothing is working anymore now.
    The same error message problem in the logging file
  • same problem here : freebox 3.4.1 : I had to disable vpn in order to be able to download torrents...
  • Hello,
    If OpenVPN doesn't seem to work, PPTP does.
    I use it since a few days and all is fine even if not the best VPN protocol.
    Once again it looks like a Free dev issue.
    A+

  • Good news everyone for this (starting to get old) thread! I contacted the Freebox developers and have been told it will be fixed in an upcoming Freebox update coming the following week(s). It's OpenVPN's 2.4 Auth-Token that's at cause. It was patched a while ago internally but was delayed for reasons.
  • hi everybody , free have update today the freebox serveur . it's ok now witht the new version 3.5 freebox server.
Sign In or Register to comment.