svn commit: r197687 - head/sys/net

Qing Li qingli at
Fri Oct 2 07:22:34 UTC 2009

I believe this patch will fix your issue. In fact two other users of
openvpn reports
the exact same problem symptom. Please give it a try and let me know how
it works out for you.

-- Qing

On Thu, Oct 1, 2009 at 11:22 PM, Tom Judge <tom at> wrote:
> Qing Li wrote:
>> Author: qingli
>> Date: Thu Oct  1 20:32:29 2009
>> New Revision: 197687
>> URL:
>> Log:
>>  The flow-table associates TCP/UDP flows and IP destinations with
>>  specific routes. When the routing table changes, for example,
>>  when a new route with a more specific prefix is inserted into the
>>  routing table, the flow-table is not updated to reflect that change.
>>  As such existing connections cannot take advantage of the new path.
>>  In some cases the path is broken. This patch will update the affected
>>  flow-table entries when a more specific route is added. The route
>>  entry is properly marked when a route is deleted from the table.
>>  In this case, when the flow-table performs a search, the stale
>>  entry is updated automatically. Therefore this patch is not
>>  necessary for route deletion.
> Hi,
> Will this fix the issue that I see visualising  its self as packet loss over
> a VPN tunnel?
> The tunnel is an openvpn (tun mode) tunnel providing a route to
> however when I ping an address in this network with
> flowtable enabled I see 2-3 out of every 5-6 packets end up being sent out
> of bge0 (IP 172.17.XX.XX/23 GW 172.17.XX.1) to the default gateway (which
> responds with destination host unreachable) rather than down tun0.
> Thanks
> Tom

More information about the svn-src-head mailing list