All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Krzysztof Oledzki <ole@ans.pl>
Cc: lartc@mailman.ds9a.nl, netfilter-devel@lists.netfilter.org,
	Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: [LARTC] Re: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues
Date: Wed, 10 Jan 2007 05:58:31 +0000	[thread overview]
Message-ID: <45A48087.8090200@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0612282158360.16672@bizon.gios.gov.pl>

Krzysztof Oledzki wrote:
>> Its still down, but the ROUTE patch is unmaintained anyway.
> 
> 
> How about attached (and inlined) patch. BTW - is it possible to add a
> Kconfig entry after a specific text, like with Makefile.ladd?
> 
> 
> [POM-NG] ROUTE: 2.6.19 compatibility fix
> 
> Make both IPv4 and IPv6 versions compatible with 2.6.19


Thanks Krzysztof, applied.

I would prefer to have someone maintain it externally though. Jan, are
you still interested in doing that? If you need help or webspace for
an external repository please let me know.



_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: Krzysztof Oledzki <ole@ans.pl>
Cc: lartc@mailman.ds9a.nl, netfilter-devel@lists.netfilter.org,
	Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: Re: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues
Date: Wed, 10 Jan 2007 06:58:31 +0100	[thread overview]
Message-ID: <45A48087.8090200@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0612282158360.16672@bizon.gios.gov.pl>

Krzysztof Oledzki wrote:
>> Its still down, but the ROUTE patch is unmaintained anyway.
> 
> 
> How about attached (and inlined) patch. BTW - is it possible to add a
> Kconfig entry after a specific text, like with Makefile.ladd?
> 
> 
> [POM-NG] ROUTE: 2.6.19 compatibility fix
> 
> Make both IPv4 and IPv6 versions compatible with 2.6.19


Thanks Krzysztof, applied.

I would prefer to have someone maintain it externally though. Jan, are
you still interested in doing that? If you need help or webspace for
an external repository please let me know.

  reply	other threads:[~2007-01-10  5:58 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-11 19:44 [LARTC] iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues ArcosCom Linux User
2006-12-11 19:44 ` ArcosCom Linux User
2006-12-12  8:24 ` [LARTC] " ArcosCom Linux User
2006-12-12  8:24   ` ArcosCom Linux User
2006-12-12  8:33   ` Lutz Jaenicke
2006-12-12  8:34   ` [LARTC] " Patrick McHardy
2006-12-12  8:34     ` Patrick McHardy
2006-12-13  8:31     ` [LARTC] " ArcosCom Linux User
2006-12-13  8:31       ` ArcosCom Linux User
2006-12-13  8:38       ` [LARTC] " Patrick McHardy
2006-12-13  8:38         ` Patrick McHardy
2006-12-13  9:12         ` [LARTC] " ArcosCom Linux User
2006-12-13  9:12           ` ArcosCom Linux User
2006-12-13  9:17           ` [LARTC] " Patrick McHardy
2006-12-13  9:17             ` Patrick McHardy
2006-12-13 11:00             ` Jan Engelhardt
2006-12-13 10:56         ` Jan Engelhardt
2006-12-28 21:10         ` Krzysztof Oledzki
2007-01-10  5:58           ` Patrick McHardy [this message]
2007-01-10  5:58             ` Patrick McHardy
2007-01-10 11:53             ` Jan Engelhardt
2007-01-10 12:53               ` [LARTC] " Patrick McHardy
2007-01-10 12:53                 ` Patrick McHardy
2007-01-10 13:15               ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, ArcosCom Linux User
2007-01-10 13:15                 ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] ArcosCom Linux User
2007-01-10 14:08                 ` Jan Engelhardt
2007-01-10 13:21               ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, ArcosCom Linux User
2007-01-10 13:21                 ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] ArcosCom Linux User
2007-01-25 17:41                 ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, Andrew Beverley
2007-01-25 17:41                   ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] Andrew Beverley
2007-01-31  2:58                   ` [LARTC] " Pablo Neira Ayuso
2007-02-09 13:37                     ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, Andrew Beverley
2007-02-09 13:37                       ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] Andrew Beverley
2007-02-09 16:57                       ` Krzysztof Oledzki
2007-02-09 17:03                         ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, kernel Patrick McHardy
2007-02-09 17:03                           ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] Patrick McHardy
2007-02-09 17:30                         ` [LARTC] Opinions about pom/patches [was: iptables 1.3.7, Andrew Beverley
2007-02-09 17:30                           ` Opinions about pom/patches [was: iptables 1.3.7, kernel 2.6.19, ROUTE and Layer7 issues] Andrew Beverley

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=45A48087.8090200@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@linux01.gwdg.de \
    --cc=lartc@mailman.ds9a.nl \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=ole@ans.pl \
    /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.