<?xml version="1.0" encoding="UTF-8"?> <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" ><channel><title>NewPush &#187; Tunnelblick</title> <atom:link href="http://newpush.com/tag/tunnelblick/feed/" rel="self" type="application/rss+xml" /><link>http://newpush.com</link> <description>Server Hosting, Data Warehouse Hosting, Collaboration</description> <lastBuildDate>Mon, 30 Jan 2012 15:40:45 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>OpenVPN write UDPv4: Can&#039;t assign requested address (code=49)</title><link>http://newpush.com/2010/01/openvpn-write-udpv4-cant-assign-requested-address-code49/</link> <comments>http://newpush.com/2010/01/openvpn-write-udpv4-cant-assign-requested-address-code49/#comments</comments> <pubDate>Thu, 21 Jan 2010 12:57:18 +0000</pubDate> <dc:creator>Balazs</dc:creator> <category><![CDATA[Mac OS X]]></category> <category><![CDATA[OpenVPN]]></category> <category><![CDATA[OS X 10.6]]></category> <category><![CDATA[Tunnelblick]]></category><guid isPermaLink="false">http://www.wdream.com/?p=451</guid> <description><![CDATA[To solve the problem, the easiest way is to flush the routes by rebooting.  The elegant way however is to shut down the interface connecting the Mac to the Internet, flush the routing table, and bring the interface back up. <a href="http://newpush.com/2010/01/openvpn-write-udpv4-cant-assign-requested-address-code49/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<h4>Problem</h4><p>On Max OS X, when trying to connect to an OpenVPN gateway, you may encounter the following error:<code><br /> 2010-01-21 05:14:59 write UDPv4: Can't assign requested address (code=49)<br /> 2010-01-21 05:15:01 write UDPv4: Can't assign requested address (code=49)<br /> ...<br /> </code><br /> The error would repeat itself indefinitely.</p><h4>Root Cause</h4><p>The TCP stack of the Mac has a bug that can cause the routing table to get corrupted.</p><h4>Solution</h4><p>The routing table needs to be flushed on the interface used to connect to the Internet.  Typically,</p><ul><li><code>en0</code>: ethernet (wired) interface</li><li><code>en1</code>: wlan (wireless) interface</li></ul><p>The easiest way is to flush the routes is to reboot.  The elegant way however is to shut down the interface connecting the Mac to the Internet, flush the routing table, and bring the interface back up.  For example, assuming a wired connection, open a terminal or an X11 xterm window and issue the following commands:<code><br /> sudo ifconfig en0 down<br /> sudo route flush<br /> sudo ifconfig en0 up<br /> </code><br /> In case the command line hangs after the flush command, just open a new terminal and run the last command from there.  When you are done, you can close all terminals.  If you are connecting with wireless, replace <code>en0</code> with <code>en1</code>.</p><h4>References</h4><p><a href="http://my.anuson.com/knowledgebase/1/OpenVPN-error-write-UDPv4-Cant-assign-requested-address-codeequals49.html">OpenVPN error: write UDPv4: Can&#8217;t assign requested address (code=49)</a></p> ]]></content:encoded> <wfw:commentRss>http://newpush.com/2010/01/openvpn-write-udpv4-cant-assign-requested-address-code49/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>Directing all VPN traffic through the OpenVPN concentrator</title><link>http://newpush.com/2009/11/directing-all-vpn-traffic-through-the-openvpn-concentrator/</link> <comments>http://newpush.com/2009/11/directing-all-vpn-traffic-through-the-openvpn-concentrator/#comments</comments> <pubDate>Sun, 29 Nov 2009 07:33:00 +0000</pubDate> <dc:creator>Balazs</dc:creator> <category><![CDATA[Linux]]></category> <category><![CDATA[Mac OS X]]></category> <category><![CDATA[OpenBSD]]></category> <category><![CDATA[OpenVPN]]></category> <category><![CDATA[Schimo]]></category> <category><![CDATA[Tunnelblick]]></category> <category><![CDATA[VPN]]></category><guid isPermaLink="false">http://www.wdream.com/?p=429</guid> <description><![CDATA[Problem It is necessary for some users to have all their traffic directed through the OpenVPN concentrator. The number one reason for such a configuration is to protect the HTTP traffic over unsecured WiFi (a.k.a. hotspots). Solution Add to the &#8230; <a href="http://newpush.com/2009/11/directing-all-vpn-traffic-through-the-openvpn-concentrator/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<h4>Problem</h4><p>It is necessary for some users to have all their traffic directed through the OpenVPN concentrator.  The number one reason for such a configuration is to protect the HTTP traffic over unsecured WiFi (a.k.a. hotspots).</p><h4>Solution</h4><p>Add to the bottom of the connecting client&#8217;s configuration file (typically under <code>/etc/openvpn/clients.d</code> the following line:<code><br /> push "redirect-gateway"<br /> </code></p> ]]></content:encoded> <wfw:commentRss>http://newpush.com/2009/11/directing-all-vpn-traffic-through-the-openvpn-concentrator/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Served from: newpush.com @ 2012-02-09 22:52:01 by W3 Total Cache -->
