Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Ulysses Almeida <ulysses.almeida@gmail.com>
To: Samuel Jean <sj-netfilter@cookinglinux.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: Two links and a SMTP sever.
Date: Tue, 18 Jan 2005 17:52:21 -0300	[thread overview]
Message-ID: <d645356050118125243d12dfb@mail.gmail.com> (raw)
In-Reply-To: <26550.142.169.215.10.1106081679.squirrel@142.169.215.10>

Thanks for the answer....


On Tue, 18 Jan 2005 15:54:39 -0500 (EST), Samuel Jean
<sj-netfilter@cookinglinux.org> wrote:
> On Tue, January 18, 2005 8:39 am, Ulysses Almeida said:
>
> (After looking attached file)
> Did you enable NAT of local connection in your kernel ?
> To be honest, I don't know anything about Lartc. And can't tell you
> how it should behave (my guess is it should pickup the right IP, of course)
> 
> However, the (ugly) SNAT work-around should work with
> NAT of local connection enabled.

  Hmm. the NAT/SNAT is working fine, when I recive the SMTP answer
(LOG on PREROUTING and INPUT of filter, nat and mangle) the packet
arrives with the correct ip on dst addr. But I can only see it, on
mangle PREROUTING, but can't on other hooks. I don't know if it is
related with some sanity check or checksum....

  That's another doubt, dos nat PREROUTING called with syn+ack
packets, or only with sym packets?

  I have these modules loaded:
ipt_LOG                 5760  7 
ipt_mark                1792  0 
ipt_MARK                2176  1 
iptable_mangle          2944  1 
ipt_state               2048  8 
iptable_filter          2944  1 
ipt_MASQUERADE          3840  4 
iptable_nat            23980  2 ipt_MASQUERADE
ip_conntrack           33072  3 ipt_state,ipt_MASQUERADE,iptable_nat
ip_tables              17920  8
ipt_LOG,ipt_mark,ipt_MARK,iptable_mangle,ipt_state,iptable_filter,ipt_MASQUERADE,iptable_nat

  
> 
> >
> >   I explaint it on the attachment (i sent this attachment, because I
> > don't thin it will cause any trouble, since it's text/plain, if does,
> > say and I won't send again).
> 
> Please put it in the body so we can comment some part.
> 
Ok, I used to use MUA that shows-me the text/plain attachments as the
e-mail body (like mutt). But now I see it won't happen all the time.
My mistake, sorry.

-- 
 - Ulysses Almeida


  reply	other threads:[~2005-01-18 20:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-18 13:39 Two links and a SMTP sever Ulysses Almeida
2005-01-18 20:54 ` Samuel Jean
2005-01-18 20:52   ` Ulysses Almeida [this message]
2005-01-18 21:17     ` Samuel Jean
2005-01-18 21:14       ` Ulysses Almeida
2005-01-18 22:02         ` Samuel Jean
2005-01-19 12:26           ` Ulysses Almeida
2005-01-18 23:28     ` Jason Opperisano
2005-02-07 22:53 ` Ulysses Almeida

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=d645356050118125243d12dfb@mail.gmail.com \
    --to=ulysses.almeida@gmail.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=sj-netfilter@cookinglinux.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