From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: RES: [LARTC] ADVANCED ROUTING USING IPROUTE2 -> Multiple Firewalls
Date: Sat, 15 Jun 2002 17:20:33 +0000 [thread overview]
Message-ID: <marc-lartc-102416163221868@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102415997220736@msgid-missing>
Hello,
On Sat, 15 Jun 2002, Roni Reicher wrote:
> Output.c: in function 'cipe_xmit'
> Output.c:175 too few arguments to function 'ip_route_output'
> Make[3]: *** [output.o] error 1
> Make[3]: leaving directory '/usr/src/linux-2.4.18-3/drivers/addon/cipe'
> Make[2]: *** [_modsubdir_cipe] error 2
> Make[2]: leaving directory '/usr/src/linux-2.4.18-3/drivers/addon'
> Make[1]: *** [_modsubdir_addon] error 2
> Make[1]: leaving directory '/usr/src/linux-2.4.18-3/drivers
> Make: *** [_mod_drivers] error 2
IIRC, Roberto Nibali provided patch for cipe to use it
together with the "routes" patch, it is on the web page:
cipe-1.5.2-routes-1.diff
> After I got that error, a formatted and reinstalled redhat 7.3. Then I
> used the newer patch (routes-2.4.19-8.diff), and I got error installing,
> and of course I couldn't recompile it.
You can use routes-2.4.19-8.diff after 2.4.19pre8. It does
not have the problem to change the interface of the routing functions,
so such problems with applying extra patches to code out of the
plain kernel should not exist.
> Ron
Regards
--
Julian Anastasov <ja@ssi.bg>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-06-15 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-15 16:52 RES: [LARTC] ADVANCED ROUTING USING IPROUTE2 -> Multiple Firewalls Roni Reicher
2002-06-15 17:20 ` Julian Anastasov [this message]
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-102416163221868@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 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.