Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection status incorrect and Cannot create udp socket error #28

Closed
GoogleCodeExporter opened this issue Aug 9, 2015 · 2 comments
Closed

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.Connect the VPN
2.Make or receive a phone call

What is the expected output? What do you see instead?

I have 2 issues that seem to be related:

1. When I tap on the box where it says "select to turn on OpenVPN tunel" it
blinks for a second but it doesn't appear to connect.  If I open up a shell
however the tunnel IS up an running.  If I click again it shows some
connection progress and then shows up as connected in the UI.

2.  Sometimes when I make or receive a call the VPN will Pause and pick
back up again after the call is finished.  Other times I see a brief error
message "Cannot create udp socket" on the screen and the vpn disconnects
and must be manually restarted.

The reason I'm listing these together is that the second problem seems to
happen mostly when the openvpn-settings software is showing that the tunnel
is up.  If I only click on client.conf once and just trust that the vpn is
up even though it isn't showing in the UI the tunnel is more likely to stay
up through a phone call.

What version of the product are you using? On what operating system?
Version 0.4.4 of Openvpn-Settings.  Openvpn binary from Openvpn Installer
app.  Rom, Bugless Beast 1.1.  Motorola Droid.


Please provide any additional information below.
Attached is a log showing both problems.

Original issue reported on code.google.com by sonictec...@gmail.com on 3 Jun 2010 at 4:32

Attachments:

@GoogleCodeExporter
Copy link
Author

OK, it looks like the main problem was that my client.conf had the following 
section:

# Downgrade privileges after initialization (non-Windows only)
user nobody
#group nobody

Commenting out the "user nobody" seems to have corrected the problem of not 
re-connecting after a voice call.  

Original comment by sonictec...@gmail.com on 10 Jun 2010 at 5:22

@GoogleCodeExporter
Copy link
Author

Original comment by friedrich.schaeuffelhut on 11 Jun 2010 at 3:39

  • Changed state: Invalid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant