All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: DNAT, Is it possible to find the original destination?
Date: Tue, 2 Nov 2004 08:39:15 -0500	[thread overview]
Message-ID: <20041102133915.GA22009@bender.817west.com> (raw)
In-Reply-To: <001d01c4c0a2$c61a3de0$2e01a8c0@minka>

On Tue, Nov 02, 2004 at 01:11:19AM -0500, Lumberjack wrote:
> Couple follow ups.  I searched back the last two or three months and didn't 
> find any "no nos" on using /proc/net/ip_conntrack.  All I can figure is 
> that it could be a hit to read through if very large.  Not sure yet how 
> /proc fs might lock things either (if that might be an issue).  So any 
> reason for using this to be a "bad thing" please provide some sort of hint 
> if possible.

the thread that it ended up coming out in that i was thinking of:

  http://marc.theaimsgroup.com/?l=netfilter&m=109649105915501&w=2

and yes--it has to do with read locking.

> Another.  If I do something to read in the contents of 
> /proc/net/ip_conntrack and then do something to send some output to stdin 
> of iptables-restore/iptables does my app need to be GPL based?  Boarders 
> here seem rather grey.  I am not modifying any GPL code nor extending it so 
> it doesn't seem to me be something that "modifies" and thus requires to be 
> released under the GPL.

can't help ya there...

-j

--
"Here we have an ordinary square.
 Whoa! Slow down egghead!"
        --The Simpsons


  reply	other threads:[~2004-11-02 13:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-01 15:30 DNAT, Is it possible to find the original destination? lumberjack
2004-11-01 16:10 ` Jason Opperisano
2004-11-02  6:11   ` Lumberjack
2004-11-02 13:39     ` Jason Opperisano [this message]
2004-11-08 23:09 ` Jason Lunz
  -- strict thread matches above, loose matches on Subject: below --
2004-11-08 23:14 Daniel Chemko

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=20041102133915.GA22009@bender.817west.com \
    --to=opie@817west.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 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.