All of lore.kernel.org
 help / color / mirror / Atom feed
From: Whit Blauvelt <whit@transpect.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Nano-Howto and IPSec
Date: Thu, 20 Dec 2001 02:18:52 +0000	[thread overview]
Message-ID: <marc-lartc-100881501324468@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100826342524601@msgid-missing>

This a change in the file freeswan-1.94/klips/net/ipsec/ipsec_tunnel.c

The difference is a 0 added like (plain diff):

1831c1831
<                                   physdev->iflink /* rgb: should this be 0? */))) {
---
>                                   physdev->iflink, 0 /* rgb: should this be 0? */))) {

Here's the diff -u

--- ipsec_tunnel.c.orig	Wed Dec  5 04:36:10 2001
+++ ipsec_tunnel.c	Wed Dec 19 21:11:55 2001
@@ -1828,7 +1828,7 @@
 				    skb->nh.iph->daddr,
 				    pass ? 0 : skb->nh.iph->saddr,
 				    RT_TOS(skb->nh.iph->tos),
-				    physdev->iflink /* rgb: should this be 0? */))) {
+				    physdev->iflink, 0 /* rgb: should this be 0? */))) {
 		stats->tx_errors++;
 		KLIPS_PRINT(debug_tunnel & DB_TN_XMIT,
 			    "klips_debug:ipsec_tunnel_start_xmit: "



On Thu, Dec 13, 2001 at 07:21:02PM +0200, Julian Anastasov wrote:
> 
> 	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>

Whit

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  parent reply	other threads:[~2001-12-20  2:18 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
2001-12-20  2:18 ` Whit Blauvelt [this message]
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-100881501324468@msgid-missing \
    --to=whit@transpect.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.