All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roberto Nibali <ratz@tac.ch>
To: Amin Azez <azez@ufomechanic.net>
Cc: Netfilter Developers <netfilter-devel@lists.netfilter.org>
Subject: Re: Fixed Re: iptables 1.3.1 crashes on iptables-restore
Date: Mon, 08 Aug 2005 17:56:35 +0200	[thread overview]
Message-ID: <42F780B3.3030102@tac.ch> (raw)
In-Reply-To: <42F77E2E.2090307@ufomechanic.net>

> Yes, I need the latest and greatest conntrack stuff, naturally ;-)

So you run a 2.6.14 kernel :)

>>What's the output /lib/libc.so.6? 
>  
> I'm not sure what you mean here, but ls -l shows:
> /lib/libc.so.6 -> libc-2.3.2.so

Invoke /lib/libc.so.6 like a command. It won't destroy your system but
it will display how your libc was crafted.

>>Just out of curiosity. And maybe if you set LD_DEBUG=all and run iptables?
>  
> It doesn't show anything interesting, iptables-restore does when
> restoring L7 rules that use fopen/fclose, they show:
> ...
> ...
>      25033:     binding file /lib/libnss_files.so.2 to
> /lib/tls/libc.so.6: normal symbol `fclose' [GLIBC_2.1]
>      25033:     file=/lib/iptables/libipt_tcp.so;  generating link map
>      25033:       dynamic: 0xb7fd727c  base: 0xb7fd4000   size: 0x0000335c
>      25033:         entry: 0xb7fd4788  phdr: 0xb7fd4034  phnum:          3
> ...
> ...
> 
> I have to say I'm not sure what libnss* is about here, I thought libnss
> stuff was for yp/niss/ldap lookup and the like for getXXXbyYYY libc
> calls, libnss_files.so starts to look like a filesystem redirector for
> user-filesystems which I thought glibc folk were dead against.  Anyway....

libnss is a long and sad story in glibc development, especially when it
comes to linking ...

>>Also the ldd /sbin/iptables 
> 
> ldd iptables shows:
>         libdl.so.2 => /lib/libdl.so.2 (0xb7fe1000)
>         libc.so.6 => /lib/tls/libc.so.6 (0x42000000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xb7feb000)
>  
>>and LD_TRACE_LOADED_OBJECTS=1 setting may give you more input.
> 
> 
> LD_DEBUG=all LD_TRACE_LOADED_OBJECTS=1 iptables-restore < ~/IPTABLES.BAD

I don't see anything obviously strange, so I can't help you here, sorry.

Regards,
Roberto Nibali, ratz
-- 
-------------------------------------------------------------
addr://Rathausgasse 31, CH-5001 Aarau  tel://++41 62 823 9355
http://www.terreactive.com             fax://++41 62 823 9356
-------------------------------------------------------------
terreActive AG                       Wir sichern Ihren Erfolg
-------------------------------------------------------------

  reply	other threads:[~2005-08-08 15:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30  3:46 iptables 1.3.1 crashes on iptables-restore Alexander Samad
2005-03-31  8:18 ` Roberto Nibali
2005-08-04 16:24   ` Amin Azez
2005-08-05 10:08     ` Amin Azez
2005-08-05 12:57       ` Fixed " Amin Azez
2005-08-05 13:22         ` Roberto Nibali
2005-08-08 15:45           ` Amin Azez
2005-08-08 15:56             ` Roberto Nibali [this message]
2005-08-08 16:03               ` Amin Azez
2005-08-08 16:19                 ` Roberto Nibali
2005-08-08 16:28                   ` Amin Azez
2005-08-08 16:46                     ` Roberto Nibali

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=42F780B3.3030102@tac.ch \
    --to=ratz@tac.ch \
    --cc=azez@ufomechanic.net \
    --cc=netfilter-devel@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 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.