Skip to content
Viscosity loses connection after 70 seconds
Got a problem with Viscosity or need help? Ask here!
Hi,
I've just updated to version 1.6 and got strange error. Viscosity loses connection after 70 (or may be 69) seconds.
I have noticed that after 70 seconds some changes appears in network configuration.
Help me please. There are some details below.
ifconfig after connection:
Alex
I've just updated to version 1.6 and got strange error. Viscosity loses connection after 70 (or may be 69) seconds.
I have noticed that after 70 seconds some changes appears in network configuration.
Help me please. There are some details below.
ifconfig after connection:
Code: Select all
ifconfig after 70 seconds:
tap0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether a6:8f:eb:bc:73:8f
inet 10.222.0.2 netmask 0xffffff00 broadcast 10.222.0.255
media: autoselect
status: active
open (pid 78062)
Code: Select all
viscosity config:
tap0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether a6:8f:eb:bc:73:8f
inet 10.222.0.2 netmask 0xffffff00 broadcast 10.222.0.255
inet 169.254.128.223 netmask 0xffff0000 broadcast 169.254.255.255
media: autoselect
status: active
open (pid 78062)
Code: Select all
Thanks,#-- Config Auto Generated By Viscosity --#
#viscosity dnssupport true
#viscosity name ap-net
#viscosity startonopen true
#viscosity usepeerdns true
#viscosity dns automatic
#viscosity ipv6 false
#viscosity dhcp true
remote xx.xx.xx.xx 22001 udp
persist-key
persist-remote-ip
comp-lzo yes
pull
fragment 1460
ca ca.crt
dev tap
persist-tun
cert cert.crt
tls-client
key key.key
persist-local-ip
tun-mtu 1500
route 172.20.0.0 255.255.255.0
sndbuf 131072
mssfix
lport 53380
comp-noadapt
cipher AES-256-CBC
keysize 256
route-method exe
rcvbuf 131072
rport 22001
keepalive 5 40
Alex
Hi Alex,
Either unticking the "Enable DHCP" checkbox for your connection (under the General tab when editing your connection in Viscosity), or updating to the latest beta version, should do the trick.
Instructions for enabling beta updates can be found at:
https://www.sparklabs.com/forum/viewtop ... &t=34#p134
Cheers,
James
Either unticking the "Enable DHCP" checkbox for your connection (under the General tab when editing your connection in Viscosity), or updating to the latest beta version, should do the trick.
Instructions for enabling beta updates can be found at:
https://www.sparklabs.com/forum/viewtop ... &t=34#p134
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
I have the same problem, after around 1 minute without any activity, my VPN tunnel is not working anymore.
Not sure if it's related but in the log I have this line:
How can I rollback to 1.5?
Not sure if it's related but in the log I have this line:
Feb 26 11:16:32: Options error: option 'keepalive' cannot be used in this context ([PUSH-OPTIONS])I'm running 1.6.2b1 (1333) (Same with problem since 1.6)
How can I rollback to 1.5?
Hi analogue,
I'm afraid your drop outs are caused by an incorrect server configuration setup - nothing related to the changes in the update. You'll get the same dropouts with any older version of Viscosity/OpenVPN.
Based off the error message your server is directly attempting to push the "keepalive" command, which is incorrect. It should simply be setting it on the server, which causes the corresponding ping/ping-restart values to be pushed to clients. You should contact your VPN Provider to correct the setup.
Cheers,
James
I'm afraid your drop outs are caused by an incorrect server configuration setup - nothing related to the changes in the update. You'll get the same dropouts with any older version of Viscosity/OpenVPN.
Based off the error message your server is directly attempting to push the "keepalive" command, which is incorrect. It should simply be setting it on the server, which causes the corresponding ping/ping-restart values to be pushed to clients. You should contact your VPN Provider to correct the setup.
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
5 posts
Page 1 of 1