public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jpiszcz <jpiszcz@lucidpixels.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@lists.netfilter.org,
	Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: Question with printk warnings in ip_conntrack with 2.4.20.]
Date: Fri, 06 Dec 2002 09:27:46 -0500	[thread overview]
Message-ID: <3DF0B3E2.8060104@lucidpixels.com> (raw)
In-Reply-To: Pine.LNX.4.33.0212061448500.2648-100000@blackhole.kfki.hu

Sure:

http://installkernel.tripod.com/tcpdump.log.bz2

Jozsef Kadlecsik wrote:

>On Thu, 5 Dec 2002, jpiszcz wrote:
>
>  
>
>>Stange?  I am just using vcheck (perl script) that goes out and checks
>>out software for the latest versions.
>>    
>>
>
>If the script uses active mode FTP and when that is refused by the server
>reverts back to passive mode, that is a natural explanation for such log
>entries.
>
>Could you record by tcpdump at least one such FTP session?
>
>  
>
>>Will there possibly be a /proc or kernel config option for warnings such
>>as these?
>>    
>>
>
>In my opinion a new directory tree /proc/sys/net/ipv4/netfilter is
>required so that tuning options could be easily added to the system.
>But that implies backward (in)compatibily issues...
>
>Regards,
>Jozsef
>-
>E-mail  : kadlec@blackhole.kfki.hu, kadlec@sunserv.kfki.hu
>PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
>Address : KFKI Research Institute for Particle and Nuclear Physics
>          H-1525 Budapest 114, POB. 49, Hungary
>
>
>
>  
>



  reply	other threads:[~2002-12-06 14:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3DEFE07D.4020909@lucidpixels.com>
2002-12-06 13:59 ` [Fwd: Question with printk warnings in ip_conntrack with 2.4.20.] Jozsef Kadlecsik
2002-12-06 14:27   ` jpiszcz [this message]
2002-12-05 23:29 jpiszcz
     [not found] <1038618763.22065.1.camel@rth.ninka.net>
2002-12-05 20:07 ` Harald Welte

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=3DF0B3E2.8060104@lucidpixels.com \
    --to=jpiszcz@lucidpixels.com \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox