Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Can't apply Julian's patches to 2.4.18
Date: Mon, 29 Apr 2002 11:17:42 +0000	[thread overview]
Message-ID: <marc-lartc-102007904922501@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102000434912878@msgid-missing>


	Hello,

On Mon, 29 Apr 2002, Carlo Borelli wrote:

> I've the same problem with a plain 2.4.17 patched to 2.4.18-pre3 with
> FreeS/WAN 1.97 and ext3 patch.
>
> [root@fw linux]# patch -p1 < ../routes-2.4.16-6.diff
> patching file include/net/ip_fib.h
> patching file include/net/route.h
> patching file include/linux/netfilter_ipv4/ip_nat.h
> patching file include/linux/rtnetlink.h
> patching file net/atm/clip.c
> patching file net/ipv4/arp.c
> patching file net/ipv4/fib_frontend.c
> Hunk #6 succeeded at 590 (offset -4 lines).
> patching file net/ipv4/fib_hash.c
> Hunk #5 succeeded at 617 (offset -5 lines).
> patching file net/ipv4/fib_rules.c
> patching file net/ipv4/fib_semantics.c
> Hunk #7 succeeded at 888 (offset -4 lines).
> Hunk #9 succeeded at 973 (offset -4 lines).
> Hunk #11 succeeded at 1026 (offset -4 lines).
> patching file net/ipv4/icmp.c
> patching file net/ipv4/igmp.c
> patching file net/ipv4/ipip.c
> patching file net/ipv4/ipmr.c
> Hunk #1 succeeded at 1141 (offset -4 lines).
> patching file net/ipv4/ip_gre.c
> patching file net/ipv4/ip_input.c
> patching file net/ipv4/ip_nat_dumb.c
> patching file net/ipv4/ip_options.c
> patching file net/ipv4/ip_output.c
> patching file net/ipv4/netfilter/ip_fw_compat.c
> Hunk #1 succeeded at 151 (offset 10 lines).
> patching file net/ipv4/netfilter/ip_fw_compat_masq.c
> patching file net/ipv4/netfilter/ip_nat_core.c
> Hunk #2 succeeded at 864 (offset 12 lines).
> patching file net/ipv4/netfilter/ip_nat_standalone.c
> patching file net/ipv4/netfilter/ipt_MASQUERADE.c
> patching file net/ipv4/netfilter/ipt_MIRROR.c
> Hunk #1 succeeded at 49 (offset 5 lines).
> patching file net/ipv4/netfilter/ipt_REJECT.c
> patching file net/ipv4/raw.c
> patching file net/ipv4/route.c
> Hunk #26 succeeded at 2183 (offset -1 lines).
> patching file net/ipv4/syncookies.c
> patching file net/ipv4/tcp_ipv4.c
> Hunk #2 succeeded at 1785 (offset 3 lines).
> patching file net/ipv4/udp.c
> patching file net/ipv6/sit.c
> [root@fw linux]#

	I don't see problem. The problems come for pre5.

Regards

--
Julian Anastasov <ja@ssi.bg>

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

      parent reply	other threads:[~2002-04-29 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-28 14:32 [LARTC] Can't apply Julian's patches to 2.4.18 tslayer
2002-04-28 14:42 ` Julian Anastasov
2002-04-29 11:08 ` Carlo Borelli
2002-04-29 11:17 ` 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-102007904922501@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