[Openswan Users] %hold 0 %acquire-netlink

[Michael Jurney]

Paul Wouters wrote:

> On Fri, 15 Jul 2005, Michael Jurney wrote:
>
>> 000 192.168.8.23/32:0 -1-> 192.168.28.1/32:0 => %hold 0    
>> %acquire-netlink
>> 000 192.168.8.23/32:0 -1-> 192.168.28.1/32:0 => %hold 0    
>> %acquire-netlink
>> 000 192.168.8.23/32:0 -1-> 192.168.28.1/32:0 => %hold 0    
>> %acquire-netlink
>> 000 192.168.8.7/32:0 -1-> 192.168.28.1/32:0 => %hold 0    
>> %acquire-netlink
>> 000 192.168.8.23/32:0 -1-> 192.168.28.1/32:0 => %hold 0    
>> %acquire-netlink
>>
>> And so on.  The IPs on the right vary, and are both in remote offices 
>> as well as on the internet.
>>
>> the only reference to this that I can find in the archives is of a 
>> user saying that including the no_oe config file solved the problem.  
>> I'm already including this, though.
>>
>> This is a debian system with a stock 2.6.12.2 kernel:
>>
>> Linux vpn 2.6.12.2 #1 SMP Wed Jul 13 08:19:36 EDT 2005 i686 GNU/Linux
>> Linux Openswan U2.2.0/K2.6.12.2 (native)
>
>
> Please upgrade openswan. Various acquire fixes went into late rversions.
>
> Paul


I've upgraded to openswan 2.3.1:

Linux Openswan U2.3.1/K2.6.11 (netkey)

I'm still seeing identical behavior.  Is the 2.6 kernel just a bad idea 
(the version number is a little misleading, it's a scratch build with 
all of the debian 2.6.11 patches, the extraversion just wasn't set)?

-- 
Michael D. Jurney
Sysadmin, DataSynapse
mikej at datasynapse.com
p: 212.842.8860

View the DataSynapse email disclaimer here:
<http://www.datasynapse.com/legal/emailprivacy.jsp>