From: "Samuel Díaz García" <samueldg@arcoscom.com>
To: netfilter@lists.netfilter.org
Subject: Last patch-o-matic patches status report
Date: Wed, 08 Feb 2006 18:30:13 +0100 [thread overview]
Message-ID: <43EA2AA5.3080401@arcoscom.com> (raw)
Hi all, I want to report to mainteneers some issues with patch-o-matic patches.
Kernel: 2.6.15.3
Iptables: 1.3.5
Aditional patches applied: imq, nf-hipac, layer7
pom: LAST
Patches not mentioned here are applied fine or kernel included and not need pom
patch.
Patches don't apply fine for any reason:
MARK-operations
ACCOUNT
netfilter-docbook
tproxy
TRACE
connrate
conntrack_locking
conntrackc_nonat
goto
ipsec-XXXXX
nat-reservations
owner-socketlookup
Patches that could be applied but broke kernel compilation (at least):
talk-conntrack-nat
Patches that could be applied but broke iptables compilation (at least):
expire
Patches that could be applied but have missing simbols in kernel (at least):
IPV4OPTSSTRIP
XOR
Patches that couldn't be applied into this kernel:
condition (Somebody send me a kernel patch that could be used over 2.6.15.x
kernel series before apply many pom patches).
Patches that could be applied but must be patched before compilation:
mms-conntrack-nat (changing 2 lines in ip_conntrack_mms.c and 1 line in
ip_nat_mms.c)
Patches that could be applied but must be disable from kernel before compilation
(because they don't compile):
IPV4OPTSSTRIP (from IPV4)
expire (from IPV6)
fuzzy (from IPV6)
nth (from IPV6)
random (from IPV6)
rtsp-conntrack (from IPV4)
XOR (from IPV4)
quake3-conntrack-nat (from IPV4)
I only expect this report could be usefull for somebody who wants to use pom
successfully.
Regards
P.D.: Sorry for my English.
--
Samuel Díaz García
Director Gerente
ArcosCom Wireless, S.L.L.
CIF: B11828068
c/ Romero Gago, 19
Arcos de la Frontera
11630 - Cadiz
http://www.arcoscom.com
mailto:samueldg@arcoscom.com
msn: samueldg@arcoscom.com
Móvil: 651 93 72 48
Tlfn.: 956 70 13 15
Fax: 956 70 34 83
next reply other threads:[~2006-02-08 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 17:30 Samuel Díaz García [this message]
2006-02-23 20:05 ` Tuning NAT timeout values Stephen Jones
2006-02-26 11:56 ` ludi
2006-02-26 19:29 ` Stephen Jones
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=43EA2AA5.3080401@arcoscom.com \
--to=samueldg@arcoscom.com \
--cc=netfilter@lists.netfilter.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