All of lore.kernel.org
 help / color / mirror / Atom feed
From: sean darcy <seandarcy2@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: why can't I DNAT SIP?
Date: Sun, 11 May 2008 10:53:02 -0400	[thread overview]
Message-ID: <g0718e$cpl$1@ger.gmane.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0805101041210.19952@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Saturday 2008-05-10 04:04, sean darcy wrote:
>>> - What helpers are loaded (both NAT and conntrack)
>> ?? How would I find out? If you mean modules:
>>
>> lsmod | grep nat
>> iptable_nat            11461  1
>> nf_nat                 22381  1 iptable_nat
>> nf_conntrack_ipv4      21837  5 iptable_nat
>> nf_conntrack           64585  4 xt_state,iptable_nat,nf_nat,nf_conntrack_ipv4
>> nfnetlink               9945  3 nf_nat,nf_conntrack_ipv4,nf_conntrack
>> ip_tables              16517  3 iptable_raw,iptable_nat,iptable_filter
>> x_tables               18629  5 xt_state,ipt_LOG,xt_tcpudp,iptable_nat,ip_tables
> 
> I would have expected to find nf_nat_sip here.
> --

I've seen references to nf_nat_sip, but no docs, howto or examples. What 
does it do that simple port forwarding doesn't? and how do you use it?

sean


  reply	other threads:[~2008-05-11 14:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08  1:10 why can't I DNAT SIP? sean darcy
2008-05-08 19:31 ` Grant Taylor
2008-05-08 22:24   ` sean darcy
2008-05-09  1:18     ` sean darcy
2008-05-09 14:15     ` Grant Taylor
2008-05-09 14:23       ` Patrick McHardy
2008-05-10  2:04         ` sean darcy
2008-05-10  8:43           ` Jan Engelhardt
2008-05-11 14:53             ` sean darcy [this message]
2008-05-11 14:58               ` Jan Engelhardt
2008-05-11 18:02                 ` sean darcy
2008-05-11 18:12                   ` Jan Engelhardt
2008-05-12 16:01           ` Patrick McHardy
2008-05-09  0:31 ` Mike Wright

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='g0718e$cpl$1@ger.gmane.org' \
    --to=seandarcy2@gmail.com \
    --cc=netfilter@vger.kernel.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.