Can't assign requested address
Tuinslak
to connect to my VPN (sometimes from a different location, sometimes
from the same location), I often get these error:
2010-03-27 18:23:13 Attempting to establish TCP connection with
85.12.6.160:443 [nonblock]
2010-03-27 18:23:13
2010-03-27 18:23:13 will try again in 5 seconds: Can't assign
requested address
2010-03-27 18:23:18
2010-03-27 18:23:18
2010-03-27 18:23:18 will try again in 5 seconds: Can't assign
requested address
2010-03-27 18:23:20 process exiting
2010-03-27 18:23:20
The only work around I have found so far is to reboot my Mac to get it
to work again. However, I really hate to reboot eachtime I want to
connect to the VPN.
I have had this problem for quite a few versions already.
Version: 3.0 (build 1437), openvpn 2.1.1
Any different work around or solution?
Kind regards,
Tuinslak
jkbull...gmail.com
actually something in OpenVPN itself having to do with routing -- it
affects some configurations, but not others.
Instead of rebooting, you can try resetting the network interface:
For a wired connection, remove and replace the network connector.
For a wireless connection, turn Airport off, then back on again.
You can do this from the command line (the following is for a wired
connection; for wireless use en1 instead of en0):
sudo ifconfig en0 down
sudo route flush
sudo ifconfig en0 up
This came from http://www.wdream.com/2010/01/openvpn-write-udpv4-cant-assign-requested-address-code49,
which references
http://my.anuson.com/knowledgebase/1/OpenVPN-error-write-UDPv4-Cant-assign-requested-address-codeequals49.html
Tuinslak
this issues as well.
But thank you for the reply. I'll test it out next time it happens, as
for now I cannot seem to repeat the problem.
On Mar 27, 7:00 pm, "jkbull...gmail.com" <jkbull...@gmail.com> wrote:
> This is supposedly due to a bug in OS X, although I suspect that it is
> actually something in OpenVPN itself having to do with routing -- it
> affects some configurations, but not others.
>
> Instead of rebooting, you can try resetting the network interface:
> For a wired connection, remove and replace the network connector.
> For a wireless connection, turn Airport off, then back on again.
>
> You can do this from the command line (the following is for a wired
> connection; for wireless use en1 instead of en0):
> sudo ifconfig en0 down
> sudo route flush
> sudo ifconfig en0 up
> This came fromhttp://www.wdream.com/2010/01/openvpn-write-udpv4-cant-assign-request...,
> which referenceshttp://my.anuson.com/knowledgebase/1/OpenVPN-error-write-UDPv4-Cant-a...
Tuinslak
Big thanks!
jkbull...gmail.com
then I think it is something else.
The two things that Tunnelblick does when quit are to unload the tun/
tap .kexts, and forcibly terminate all openvpn processes.
The next time this happens, before trying to correct it, please check
to see if any processes named "openvpn" are active. There should be
one openvpn process for each VPN connection that is connected, but if
everything is disconnected, there shouldn't be any "openvpn"
processes.
To check for an "openvpn" process, launch "Activity Monitor" (it is in
Applications/Utilities). Then type openvpn into the Filter box in the
top right corner.
If you find any, please let us know. And you might be able to solve
the problem by terminating all such processes.
If this is the situation, maybe Tunnelblick can do something about it.
Tuinslak
Actually this seems to happen each time I change IP range. I managed
to reproduce this problem at home using two different access points
(and two different IP ranges).
2010-05-05 15:32:07 Attempting to establish TCP connection with
85.12.6.160:443 [nonblock]
2010-05-05 15:32:07
2010-05-05 15:32:07 will try again in 5 seconds: Can't assign
requested address
2010-05-05 15:32:12
2010-05-05 15:32:12
2010-05-05 15:32:12 will try again in 5 seconds: Can't assign
requested address
Searching for openvpn in terminal:
$ ps aux | grep vpn
yeri 13793 0.0 0.0 2435036 528 s000 S+ 3:34PM 0:00.00
grep -i vpn
Same for Activity Monitor, there are no "openvpn" processes active
(and Tunnelblick is still running).
And I am currently not connected to any VPN connections.
- http://www.flickr.com/photos/tuinslak/4580798225/sizes/o/
- http://www.flickr.com/photos/tuinslak/4581426946/sizes/o/
- http://www.flickr.com/photos/tuinslak/4581427264/sizes/o/
On Mar 29, 1:03 pm, "jkbull...gmail.com" <jkbull...@gmail.com> wrote:
> Hmmm. If quitting and relaunching Tunnelblick also fixes this problem,
> then I think it is something else.
>
> The two things that Tunnelblick does when quit are to unload the tun/
> tap .kexts, and forcibly terminate all openvpn processes.
>
> The next time this happens, before trying to correct it, please check
> to see if any processes named "openvpn" are active. There should be
> one openvpn process for each VPN connection that is connected, but if
> everything is disconnected, there shouldn't be any "openvpn"
> processes.
>
> To check for an "openvpn" process, launch "Activity Monitor" (it is in
> Applications/Utilities). Then type openvpn into the Filter box in the
> top right corner.
>
> If you find any, please let us know. And you might be able to solve
> the problem by terminating all such processes.
>
> If this is the situation, maybe Tunnelblick can do something about it.
>
>
>
>
> > All right, seems to work indeed.
> > Big thanks!
>
>
> > > I've seen that quitting tunnelblick instead of disconnecting fixes
> > > this issues as well.
>
> > > But thank you for the reply. I'll test it out next time it happens, as
> > > for now I cannot seem to repeat the problem.
>
> > > On Mar 27, 7:00 pm, "jkbull...gmail.com" <jkbull...@gmail.com> wrote:
>
> > > > This is supposedly due to a bug in OS X, although I suspect that it is
> > > > actually something in OpenVPN itself having to do with routing -- it
> > > > affects some configurations, but not others.
>
> > > > Instead of rebooting, you can try resetting the network interface:
> > > > For a wired connection, remove and replace the network connector.
> > > > For a wireless connection, turn Airport off, then back on again.
>
> > > > You can do this from the command line (the following is for a wired
> > > > connection; for wireless use en1 instead of en0):
> > > > sudo ifconfig en0 down
> > > > sudo route flush
> > > > sudo ifconfig en0 up
> > > > This came fromhttp://www.wdream.com/2010/01/openvpn-write-udpv4-cant-assign-request...,
> > > > which referenceshttp://my.anuson.com/knowledgebase/1/OpenVPN-error-write-UDPv4-Cant-a...
>
>
> > > > > Whenever I use Tunnelblick to connect to my VPN, disconnect, and retry
> > > > > to connect to my VPN (sometimes from a different location, sometimes
> > > > > from the same location), I often get these error:
>
> > > > > 2010-03-27 18:23:13 Attempting to establish TCP connection with
> > > > > 85.12.6.160:443 [nonblock]
> > > > > 2010-03-27 18:23:13
> > > > > 2010-03-27 18:23:13 will try again in 5 seconds: Can't assign
> > > > > requested address
> > > > > 2010-03-27 18:23:18
> > > > > 2010-03-27 18:23:18
> > > > > 2010-03-27 18:23:18 will try again in 5 seconds: Can't assign
> > > > > requested address
> > > > > 2010-03-27 18:23:20 process exiting
> > > > > 2010-03-27 18:23:20
>
> > > > > The only work around I have found so far is to reboot my Mac to get it
> > > > > to work again. However, I really hate to reboot eachtime I want to
> > > > > connect to the VPN.
> > > > > I have had this problem for quite a few versions already.
>
> > > > > Version: 3.0 (build 1437), openvpn 2.1.1
>
> > > > > Any different work around or solution?
>
> > > > > Kind regards,
> > > > >Tuinslak
You received this message because you are subscribed to the Google Groups "tunnelblick-discuss" group.
To post to this group, send email to tunnelbli...@googlegroups.com.
To unsubscribe from this group, send email to tunnelblick-dis...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tunnelblick-discuss?hl=en.