From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Nano-Howto and IPSec
Date: Thu, 13 Dec 2001 17:21:02 +0000 [thread overview]
Message-ID: <marc-lartc-100826390225825@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100826342524601@msgid-missing>
Hello,
On Thu, 13 Dec 2001, Jason A. Pattie wrote:
> I patched my kernel with the new routing code for 2.4.14 which already
> had been patched with a FreeS/WAN snapshot. However, the compilation
> gave me an error stating that:
>
> ipsec_tunnel.c: In function `ipsec_tunnel_start_xmit':
> ipsec_tunnel.c:1883: too few arguments to function `ip_route_output'
> make[3]: *** [ipsec_tunnel.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.4.14/net/ipsec'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.4.14/net/ipsec'
> make[1]: *** [_subdir_ipsec] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.14/net'
> make: *** [_dir_net] Error 2
>
> Has anyone else run into this problem of mixing the new multipath
> routing code with FreeS/WAN? or am I missing something?
Yes but I still didn't received patch for this. Just add
one 0 as last argument to ip_route_output, make a diff -u and I'll
upload it on the site. Of course, if everything else works.
Regards
--
Julian Anastasov <ja@ssi.bg>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2001-12-13 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 17:09 [LARTC] Nano-Howto and IPSec Jason A. Pattie
2001-12-13 17:21 ` Julian Anastasov [this message]
2001-12-20 2:18 ` Whit Blauvelt
2001-12-20 21:04 ` Julian Anastasov
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=marc-lartc-100826390225825@msgid-missing \
--to=ja@ssi.bg \
--cc=lartc@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