From: Kostadin Karaivanov <larry@minfin.bg>
To: linux-kernel@vger.kernel.org
Subject: Re: ipsec-tools 0.1 + kernel 2.5.64
Date: Wed, 05 Mar 2003 18:05:16 +0200 [thread overview]
Message-ID: <3E66203C.7070504@minfin.bg> (raw)
In-Reply-To: <3E65E45E.8090401@minfin.bg>
Kostadin Karaivanov wrote:
>> Hi,
>>
>> both manual keying and automatic keying with racoon (pre-shared secret)
>> are working fine. No need to patch or modify anything. I tried only
>> ipv4.
>>
>> But: don't "setkey -DP" while racoon is running, it crashes
>> my machine. Sorry, could not get any details.
>
>>
>> Andreas
>
> BTW "ipsec-tools 0.1" from where ???
If you mention www.sf.net/projects/ipsec-tools
they does not compiles for me I cot following error
grabmyaddr.c:69:1: warning: "HAVE_GETIFADDRS" redefined
<command line>:1:1: warning: this is the location of the previous definition
grabmyaddr.c:88: redefinition of `struct ifaddrs'
grabmyaddr.c:200: warning: static declaration for `getifaddrs' follows
non-static
grabmyaddr.c:254: warning: static declaration for `freeifaddrs' follows
non-static
make[3]: *** [grabmyaddr.o] Error 1
make[3]: Leaving directory `/usr/src/ipsec-tools-0.1/src/racoon'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/ipsec-tools-0.1/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/ipsec-tools-0.1'
make: *** [all] Error 2
I can provide additional info if needed (gcc-3.2.2)
>
>
> wwell Larry
>
>
next prev parent reply other threads:[~2003-03-05 15:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 11:49 ipsec-tools 0.1 + kernel 2.5.64 Kostadin Karaivanov
2003-03-05 16:05 ` Kostadin Karaivanov [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-05 18:15 Derek Atkins
2003-03-05 18:27 ` Christoph Hellwig
2003-03-05 18:43 ` Derek Atkins
2003-03-05 18:51 ` Christoph Hellwig
2003-03-05 19:00 ` Derek Atkins
2003-03-05 19:55 ` Derek Atkins
2003-03-05 11:29 Andreas Jellinghaus
2003-03-05 11:28 ` bert hubert
2003-03-05 14:52 ` Derek Atkins
2003-03-05 12:47 ` James Morris
2003-03-05 19:33 ` Andreas Jellinghaus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E66203C.7070504@minfin.bg \
--to=larry@minfin.bg \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox