Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Willy TARREAU <willy@w.ods.org>
Cc: Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	Netfilter Mailinglist <netfilter@lists.netfilter.org>
Subject: Re: [ANNOUNCE] call for testing of patch-o-matic-ng
Date: Sun, 29 Feb 2004 14:33:08 +0100	[thread overview]
Message-ID: <20040229133308.GO7790@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20040229101116.GA10012@pcw.home.local>

[-- Attachment #1: Type: text/plain, Size: 1968 bytes --]

On Sun, Feb 29, 2004 at 11:11:16AM +0100, Willy TARREAU wrote:
> Hi Harald,
> 
> Just tested it on top of 2.4.25, like this :
> 
>     KERNEL_DIR=/usr/src/linux-2.4.25-pomng ./runme --batch extra
> 
> and I got a few problems :
> 
>   - first, I didn't find how to specify where my iptables sources is
>     installed, so I had to enter it by hand each time I restarted it.
>     I did not find any env variable in the perl code, and I must say
>     that my understanding of perl is, hmmm.. very limited.

I've now introduced the IPTABLES_DIR environment variable (or the
--iptables-path option)

>   - ROUTE and TRACE told me :
>     "unable to find ladd slot in src /usr/src/linux-2.4.25-pomng/./net/ipv6/Makefile"
>     I think they wanted to add a line in the Makefile but didn't find
>     the right place to do so. 

Yes, indeed.  They were in the wrong directory, should be fixed now.

> BTW, is there a way to install a patch only for ipv4 or for ipv6 like before ?

no.

>   - I observed usual conflicts :
>     present 'CONNMARK' conflicts with to-be-installed 'connbytes'
>     present 'raw' conflicts with to-be-installed 'conntrack-seqfile'
>     present 'CONNMARK' conflicts with to-be-installed 'conntrack_arefcount'

yes, that is normal and perfectly ok.

>   - and finally, trying to apply conntrack_locking litterally killed my
>     box in out of memory within a few tens of seconds (I could not even
>     run ps) :

ouch.  That needs to be fixed.  I'll try to reproduce that.

> Cheers,
> Willy

Thanks for your testing so far.

-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-02-29 13:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25 18:28 [ANNOUNCE] call for testing of patch-o-matic-ng Harald Welte
2004-02-25 19:31 ` rruegner
2004-02-25 20:28   ` Harald Welte
2004-02-26 16:00     ` RRuegner
2004-02-26 20:24       ` Henrik Nordstrom
2004-02-26 20:31         ` RRuegner
2004-02-26 20:28       ` call for testing of patch-o-matic-ng tested with kernel 2.4.25 failed for h323 RRuegner
2004-02-29 10:11 ` [ANNOUNCE] call for testing of patch-o-matic-ng Willy TARREAU
2004-02-29 10:25   ` Henrik Nordstrom
2004-02-29 13:33   ` Harald Welte [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=20040229133308.GO7790@sunbeam.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=willy@w.ods.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