Linux Netfilter discussions
 help / color / mirror / Atom feed
From: horape@tinuviel.compendium.com.ar
To: Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: DNATing packets sent to the NATing box
Date: Sun, 14 Dec 2003 12:26:13 -0300	[thread overview]
Message-ID: <20031214152613.GA14170@tinuviel.compendium.com.ar> (raw)
In-Reply-To: <200312140919.04832.JALaramie@Loudoun-Fairfax.com>

> > I'm really replacing the DNAT rule with the LOG one (only rule in the chain
> > is the LOG one)

> If there are no other rules in the nat PREROUTING chain and assuming that you 
> don't have and mangle PREROUTING rules (you don't, do you?) then that log 
> rule will see every single packet that comes in off the wire. Try this:

> iptables -A PREROUTING -p all -j LOG --log-prefix "PREROUTING: "

I do:

iptables -t nat -A PREROUTING -p udp -j LOG --log-prefix "PREROUTING: "
iptables -t filter -A INPUT -p udp -j LOG --log-prefix "INPUT: "

(I'm logged in that box via ssh, so I prefer not to do -p all)

There are no more rules than these ones.

In the log I see the INPUT ones but not the PREROUTING (only see on
PREROUTING packets to port 137, maybe some worm...)

> You should see tons output in /var/log/messages including the packets you're 
> looking for. If the packets aren't there, then they aren't making it to the 
> box.

But the packets got to the INPUT rule, that should be after PREROUTING. And
got to my socket.

> Jeff

Saludos,
					HoraPe
---
Horacio J. Peña
horape@compendium.com.ar
horape@uninet.edu


  parent reply	other threads:[~2003-12-14 15:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-14 13:52 DNATing packets sent to the NATing box horape
2003-12-14 14:28 ` Jeffrey Laramie
     [not found] ` <200312140919.04832.JALaramie@Loudoun-Fairfax.com>
2003-12-14 15:26   ` horape [this message]
2003-12-14 15:51     ` Jeffrey Laramie
2003-12-14 16:04       ` horape
2003-12-14 16:55         ` Jeffrey Laramie
2003-12-14 17:16           ` Antony Stone
2003-12-14 17:35             ` Jeffrey Laramie
2003-12-14 17:51             ` horape
  -- strict thread matches above, loose matches on Subject: below --
2003-12-14 18:02 horape
2003-12-14 15:39 horape
2003-12-14  0:52 horape
2003-12-14  4:55 ` Joel Newkirk
2003-12-14  8:42 ` Antony Stone
2003-12-14 12:32   ` horape
2003-12-21  4:49 ` horape

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=20031214152613.GA14170@tinuviel.compendium.com.ar \
    --to=horape@tinuviel.compendium.com.ar \
    --cc=JALaramie@Loudoun-Fairfax.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox