Jump to content
Not connected, Your IP: 3.237.87.69
Sign in to follow this  
jamesdoe

ANSWERED Connection/Disconnection issues with WZR-600DHP (Buffalo) running build 20180

Recommended Posts

Hi,

 

I am running Buffalo WZR-600DHP on DD-WRT 20180. I successfully used the config generator to connect to Arrakis. I always *seem* to be connected (speedtests and other geolocations report me in Virginia and the OPENVPN status always says "connected" when I check).

 

But I was sometimes getting erratic behaviour so I checked the logs and found what appears to be an unstable connection (see below for copy/paste of the OpenVPN status tab.

 

The question is: Should I try other Open VPN servers? Downgrade my DD-WRT to the previous buffalo supported build (looks oldish) or install

the only build on the DD-WRT web site that is made for my router (BrainSlayer-V24-preSP2/2013/04-01-2013-r21153/)

 

 

I am looking for 

 

a) Confirmation that my VPN is "flapping" (I am not familiar with OpenVPN logging....for all I know this is normal and my issues are elsewhere)

Advice on the OpenVPN

c) Advice on how to "switch" OpenVPN servers easily...is there an easier way than changing the connection IP in my setup? Is the rest of my config valid across the opther servers?

 

Thanks

 

 

 

StateServer: : Local Address: Remote Address: Client: CONNECTED: SUCCESS Local Address: 10.4.25.150 Remote Address: 10.4.25.149

 

Status

 

LogServerlog Clientlog 20130615 14:20:20 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:20:20 D MANAGEMENT: CMD 'log 500' 
20130615 14:20:20 MANAGEMENT: Client disconnected 
20130615 14:25:01 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:25:01 D MANAGEMENT: CMD 'state' 
20130615 14:25:01 MANAGEMENT: Client disconnected 
20130615 14:25:01 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:25:01 D MANAGEMENT: CMD 'state' 
20130615 14:25:01 MANAGEMENT: Client disconnected 
20130615 14:25:01 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:25:01 D MANAGEMENT: CMD 'state' 
20130615 14:25:01 MANAGEMENT: Client disconnected 
20130615 14:25:01 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:25:01 D MANAGEMENT: CMD 'log 500' 
20130615 14:25:01 MANAGEMENT: Client disconnected 
20130615 14:28:02 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:28:02 D MANAGEMENT: CMD 'state' 
20130615 14:28:02 MANAGEMENT: Client disconnected 
20130615 14:28:02 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:28:02 D MANAGEMENT: CMD 'state' 
20130615 14:28:02 MANAGEMENT: Client disconnected 
20130615 14:28:02 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:28:02 D MANAGEMENT: CMD 'state' 
20130615 14:28:02 MANAGEMENT: Client disconnected 
20130615 14:28:02 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:28:02 D MANAGEMENT: CMD 'log 500' 
20130615 14:28:02 MANAGEMENT: Client disconnected 
20130615 14:28:45 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:28:45 D MANAGEMENT: CMD 'state' 
20130615 14:28:45 MANAGEMENT: Client disconnected 
20130615 14:28:45 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:28:45 D MANAGEMENT: CMD 'state' 
20130615 14:28:45 MANAGEMENT: Client disconnected 
20130615 14:28:45 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:28:45 D MANAGEMENT: CMD 'state' 
20130615 14:28:45 MANAGEMENT: Client disconnected 
20130615 14:28:45 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:28:45 D MANAGEMENT: CMD 'log 500' 
20130615 14:28:45 MANAGEMENT: Client disconnected 
20130615 14:41:07 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:41:07 D MANAGEMENT: CMD 'state' 
20130615 14:41:07 MANAGEMENT: Client disconnected 
20130615 14:41:07 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:41:07 D MANAGEMENT: CMD 'state' 
20130615 14:41:07 MANAGEMENT: Client disconnected 
20130615 14:41:07 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:41:07 D MANAGEMENT: CMD 'state' 
20130615 14:41:07 MANAGEMENT: Client disconnected 
20130615 14:41:07 MANAGEMENT: Client connected from 127.0.0.1:5001 
20130615 14:41:07 D MANAGEMENT: CMD 'log 500' 
19700101 00:00:00 

 

Share this post


Link to post

Hello!

 

a) It might be a problem in the management, not in the OpenVPN client connection itself. Chances are that your connection is actually always on, but of course further investigation is mandatory. Could you please post the complete logs for an additional check?

 

c) Unfortunately not with the DD-WRT web interface alone.

 

Kind regards

Share this post


Link to post

***

 

a) It might be a problem in the management, not in the OpenVPN client connection itself. Chances are that your connection is actually always on, but of course further investigation is mandatory. Could you please post the complete logs for an additional check?

 

****

 

Could you kindly provide instructions for which additional logs and where they are located? What I attached was the complete log on that page.  I am unsure how to obtain deeper logging information in DD-WRT. I can ssh to the router and run some commands, but don't have a large amount of experience doing this with either OpenVPN, iptables or DD-WRT.

Share this post


Link to post

Hello!

 

a) It might be a problem in the management, not in the OpenVPN client connection itself. Chances are that your connection is actually always on, but of course further investigation is mandatory. Could you please post the complete logs for an additional check?

 

c) Unfortunately not with the DD-WRT web interface alone.

 

Kind regards

 

 

Just checked again and had this. The early part seems to be different/more informative

 

Serverlog Clientlog 20130616 00:25:50 Data Channel MTU parms [ L:1558 D:1450 EF:58 EB:135 ET:0 EL:0 AF:3/1 ] 

20130616 00:25:50 Local Options String: 'V4 dev-type tun link-mtu 1558 tun-mtu 1500 proto UDPv4 comp-lzo cipher AES-256-CBC auth SHA1 keysize 256 key-method 2 tls-client' 

20130616 00:25:50 Expected Remote Options String: 'V4 dev-type tun link-mtu 1558 tun-mtu 1500 proto UDPv4 comp-lzo cipher AES-256-CBC auth SHA1 keysize 256 key-method 2 tls-server' 

20130616 00:25:50 Local Options hash (VER=V4): '22188c5b' 

20130616 00:25:50 Expected Remote Options hash (VER=V4): 'a8f55717' 

20130616 00:25:50 I UDPv4 link local: [undef] 

20130616 00:25:50 I UDPv4 link remote: 192.96.200.18:443 

20130616 00:25:50 TLS: Initial packet from 192.96.200.18:443 sid=5a02be17 512abe92 

20130616 00:25:50 VERIFY OK: depth=1 /C=IT/ST=IT/L=Perugia/O=airvpn.org/CN=airvpn.org_CA/emailAddress=info@airvpn.org 

20130616 00:25:50 VERIFY OK: nsCertType=SERVER 

20130616 00:25:50 NOTE: --mute triggered... 

20130616 00:25:50 6 variation(s) on previous 3 message(s) suppressed by --mute 

20130616 00:25:50 I [server] Peer Connection Initiated with 192.96.200.18:443 

20130616 00:25:52 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1) 

20130616 00:25:52 PUSH: Received control message: 'PUSH_REPLY redirect-gateway def1 dhcp-option DNS 10.4.0.1 comp-lzo no route 10.4.0.1 topology net30 ping 10 ping-restart 60 ifconfig 10.4.25.150 10.4.25.149' 

20130616 00:25:52 OPTIONS IMPORT: timers and/or timeouts modified 

20130616 00:25:52 NOTE: --mute triggered... 

20130616 00:25:52 4 variation(s) on previous 3 message(s) suppressed by --mute 

20130616 00:25:52 I TUN/TAP device tun1 opened 

20130616 00:25:52 TUN/TAP TX queue length set to 100 

20130616 00:25:52 I /sbin/ifconfig tun1 10.4.25.150 pointopoint 10.4.25.149 mtu 1500 

20130616 00:25:52 /sbin/route add -net 192.96.200.18 netmask 255.255.255.255 gw 72.53.115.105 

20130616 00:25:52 /sbin/route add -net 0.0.0.0 netmask 128.0.0.0 gw 10.4.25.149 

20130616 00:25:52 /sbin/route add -net 128.0.0.0 netmask 128.0.0.0 gw 10.4.25.149 

20130616 00:25:52 /sbin/route add -net 10.4.0.1 netmask 255.255.255.255 gw 10.4.25.149 

20130616 00:25:52 I Initialization Sequence Completed 

20130616 00:29:17 MANAGEMENT: Client connected from 127.0.0.1:5001 

20130616 00:29:17 D MANAGEMENT: CMD 'state' 

20130616 00:29:17 MANAGEMENT: Client disconnected 

20130616 00:29:17 MANAGEMENT: Client connected from 127.0.0.1:5001 

20130616 00:29:17 D MANAGEMENT: CMD 'state' 

20130616 00:29:17 MANAGEMENT: Client disconnected 

20130616 00:29:17 MANAGEMENT: Client connected from 127.0.0.1:5001 

20130616 00:29:17 D MANAGEMENT: CMD 'state' 

20130616 00:29:17 MANAGEMENT: Client disconnected 

20130616 00:29:18 MANAGEMENT: Client connected from 127.0.0.1:5001 

20130616 00:29:18 D MANAGEMENT: CMD 'log 500' 

20130616 00:29:18 MANAGEMENT: Client disconnected 

20130616 00:31:53 Replay-window backtrack occurred [1] 

20130616 00:33:58 MANAGEMENT: Client connected from 127.0.0.1:5001 

20130616 00:33:58 D MANAGEMENT: CMD 'state' 

20130616 00:33:58 MANAGEMENT: Client disconnected 

20130616 00:33:58 MANAGEMENT: Client connected from 127.0.0.1:5001 

20130616 00:33:58 D MANAGEMENT: CMD 'state' 

20130616 00:33:58 MANAGEMENT: Client disconnected 

20130616 00:33:58 MANAGEMENT: Client connected from 127.0.0.1:5001 

20130616 00:33:58 D MANAGEMENT: CMD 'state' 

20130616 00:33:58 MANAGEMENT: Client disconnected 

20130616 00:33:58 MANAGEMENT: Client connected from 127.0.0.1:5001 

20130616 00:33:58 D MANAGEMENT: CMD 'log 500' 

19700101 00:00:00

Share this post


Link to post

Hello!

 

The logs show that the initial connection is just fine. The management seems to provide misleading information, though, during those 4-5 seconds at 0:29 and 0:33. Can you please check that during the whole time in between two series of similar entries your connection in reality has not dropped?

 

Kind regards

Share this post


Link to post

I am not sure that verifying the connection "manually" is possible. From most of the logs I looked at, the connection is re-established inside 3 seconds. You pointed out 1 example where minutes seem to occur, but this looks like an exception. I checked again a few minutes ago and the connection seems to fail every 5 minutes, but is re-established inside 0-1-2 seconds.  I don't know of a good method of checking the VPN status inside this timeframe? I can't just refresh the log page to wait for another window of a few minutes...

 

Do you have any experience with the more recent build of DD-WRT I mentioned earlier (21153?). Is this something that can get fixed by another build?  

Share this post


Link to post

Hello!

 

To begin with, you should check not within those 3 seconds, but in the time between two occurrences of those management "connect/disconnect" brief cycles. Realistically, it's not possible that a VPN connection is dropped, routing table restored, connection re-established with TLS handshake, routes pushed again etc. in 3-4 seconds, so it might just be a management misleading behavior.

 

Kind regards

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image
Sign in to follow this  

×
×
  • Create New...