All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Corrêa de Azevedo" <nielca@linkexpress.com.br>
To: netfilter-devel@lists.netfilter.org
Subject: Re: /proc/net/ip_conntrack
Date: Wed, 30 Jun 2004 11:28:25 -0300	[thread overview]
Message-ID: <20040630130806.M61849@linkexpress.com.br> (raw)
In-Reply-To: <Pine.LNX.4.44.0406301236030.3767-100000@filer.marasystems.com>

   Hi Henrik. 
 
> > I wonder if any one could help me with figuring out a way to write to the  
> > proc file "/proc/net/ip_conntrack". 
>  
> You can't. It is not a file, it is a window into the connection  
> tracking function of the kernel showing you what is going on "right  
> now". This window is bulletproof and you cant take things out or put  
> things in via this window, only look at how they look. 
 
  I've just figured that out spending the hole night studing ip_conntrack source. Since I'm 
really starting with advanced programming, it took me some time to figured out that 
ip_conntrack matching works as a LKM (Loable Kernel Module) and that to write to the 
/proc/net/ip_conntrack file, it should be a LKM too. 
  Tough, I still wonder if is there a solution to this problem. I was thinking of LKMs and 
wondering if it is possible to one write a LKM that interacts with the ip_conntrack LKM to 
write entries to /proc/net/ip_conntrack? Or even write directly to it? 
   I've just loaded ip_conntrack LKM indirectly by inserting a statefull rule to iptables and 
checkout what symbols it makes available. There are a few that, by their names, looks like 
inserts entries to ip_conntrack file (just guessing), like: 
 
d0901c50  GPLONLY_ip_conntrack_put_Re9c6735e  [ip_conntrack] 
 
   Any way, what do you think about this? Does it sound like nonsense (I've just my first 
contact with LKM...) or it maybe possible? 
 
>  
> > What I need is to replicate this file  
> > from one computer to another. 
>  
> See discussions on conntrack replication/syncronisation. There is an  
> ongoing (not yet finished) project implementing this kind of  
> function. There is a whole lot more involved than just "copying". 
 
   I'll look into google for "conntrack replication/syncronisation" and see what I can figure out, 
and also be waiting to see what you think about this considerations. 
   Thank's for your help, 
 
                        Daniel C. Azevedo 

  reply	other threads:[~2004-06-30 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 21:40 /proc/net/ip_conntrack Daniel Corrêa de Azevedo
2004-06-30 10:38 ` /proc/net/ip_conntrack Henrik Nordstrom
2004-06-30 14:28   ` Daniel Corrêa de Azevedo [this message]
2004-06-30 13:37     ` /proc/net/ip_conntrack Pablo Neira
2004-06-30 16:32       ` /proc/net/ip_conntrack Henrik Nordstrom
  -- strict thread matches above, loose matches on Subject: below --
2003-03-20 13:38 /proc/net/ip_conntrack Martin Zdila

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=20040630130806.M61849@linkexpress.com.br \
    --to=nielca@linkexpress.com.br \
    --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.