Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Wennie V. Lagmay" <wlagmay@yanbulink.net>
To: Jason Opperisano <opie@817west.com>, netfilter@lists.netfilter.org
Subject: Re: SNAT or SAME logging
Date: Thu, 23 Jun 2005 20:27:14 +0300	[thread overview]
Message-ID: <000a01c57818$cc097fd0$130aa8c0@win2kpro> (raw)
In-Reply-To: 20050623142009.GA16600@bender.817west.com

Hi Jason,

Is there a way to log it for sucurity reasons.

Thanks,

Wennie


----- Original Message -----
From: "Jason Opperisano" <opie@817west.com>
To: <netfilter@lists.netfilter.org>
Sent: Thursday, June 23, 2005 5:20 PM
Subject: Re: SNAT or SAME logging


> On Thu, Jun 23, 2005 at 08:13:43AM +0300, Wennie V. Lagmay wrote:
> > Hi all,
> >
> > Im using Iptables (SAME) to translate my private IP address to Public IP
> > address, I just want to know how can I monitor and log which Public IP
> > address is used by a specific private IP address.
> >
> > Example:
> >
> > -A POSTROUTING -s 192.168.10.0/255.255.255.0 -j SAME --nodst --to
> > 212.xxx.xxx.113-212.xxx.xxx.114
> > -A POSTROUTING -s 192.168.11.0/255.255.255.0 -j SAME --nodst --to
> > 212.xxx.xxx.115-212.xxx.xxx.116
> >
> > On the example above private IP block 192.168.10.0/24  was map to used
> > 212.xxx.xxx.113  to 212.xxx.xxx.114. How can I idenfify lets say
> > 192.168.10.10/24 is using xxx.113 or xxx.114 at any given time.
>
>   grep $SRCIP /proc/net/ip_conntrack
>
> the last dst= is the SNAT IP.
>
> -j
>
> --
> "Stewie: What the hell is this?
>  Lois: Stewie that's tuna salad.
>  Stewie: Really? I could have sworn it was cat food."
>         --Family Guy
>
>




      reply	other threads:[~2005-06-23 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23  5:13 SNAT or SAME logging Wennie V. Lagmay
2005-06-23 14:20 ` Jason Opperisano
2005-06-23 17:27   ` Wennie V. Lagmay [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='000a01c57818$cc097fd0$130aa8c0@win2kpro' \
    --to=wlagmay@yanbulink.net \
    --cc=netfilter@lists.netfilter.org \
    --cc=opie@817west.com \
    /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