All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Leonardo Rodrigues Magalhães" <leolistas@solutti.com.br>
To: Adam Rosi-Kessel <adam@rosi-kessel.org>, netfilter@lists.netfilter.org
Subject: Re: Why would certain packets not reach nat PREROUTING chain?
Date: Sun, 18 Dec 2005 03:42:43 -0300	[thread overview]
Message-ID: <43A504E3.9070706@solutti.com.br> (raw)
In-Reply-To: <20051118015254.GA21128@bostoncoop.net>


>
># iptables -t nat -L -n
>Chain PREROUTING (policy ACCEPT)
>target     prot opt source               destination         
>
>Chain POSTROUTING (policy ACCEPT)
>target     prot opt source               destination         
>SNAT       all  --  192.168.98.0/24      0.0.0.0/0           to:EXTERNAL_IP_OF_NAT_BOX 
>  
>

    Adam, have you tried adding a properly PREROUTING rule for this 
specific traffic ? It would be like

iptables -t nat -A PREROUTING -p udp -d EXTERNAL_IP_OF_NAT_BOT --dport 
500 -j DNAT --to LOCAL_CLIENT

    Other test I would suggest ....... have you tried some other UDP 
traffic, just like DNS and see if it works ? Have you tried some TCP 
traffic and see if it works fine ?

-- 


	Atenciosamente / Sincerily,
	Leonardo Rodrigues
	Solutti Tecnologia
	http://www.solutti.com.br

	Minha armadilha de SPAM, NÃO mandem email
	gertrudes@solutti.com.br
	My SPAMTRAP, do not email it






  parent reply	other threads:[~2005-12-18  6:42 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10  1:57 Why would certain packets not reach nat PREROUTING chain? Adam Rosi-Kessel
2005-11-10  1:59 ` Adam Rosi-Kessel
2005-11-10  3:18   ` Alexander Samad
2005-11-10  3:27     ` Adam Rosi-Kessel
     [not found]       ` <3063e50511100055m41abd50hc3af78a67896db7d@mail.gmail.com>
2005-11-10 12:44         ` Adam Rosi-Kessel
2005-11-10 10:15 ` Sandro Dentella
2005-11-10 16:44   ` Jozsef Kadlecsik
2005-11-14 14:53     ` Adam Rosi-Kessel
2005-11-14 15:03       ` Jozsef Kadlecsik
2005-11-14 15:09         ` Adam Rosi-Kessel
2005-11-15  9:07           ` Jozsef Kadlecsik
2005-11-15 13:43             ` Adam Rosi-Kessel
2005-11-15 14:00               ` Jozsef Kadlecsik
2005-11-15 23:53                 ` Adam Rosi-Kessel
2005-11-15 23:57                   ` Adam Rosi-Kessel
2005-11-16  0:02                     ` Adam Rosi-Kessel
2005-11-16  9:42                   ` Jozsef Kadlecsik
2005-11-18  1:52                     ` Adam Rosi-Kessel
2005-11-18 11:07                       ` Jozsef Kadlecsik
2005-11-19  3:46                         ` Adam Rosi-Kessel
2005-11-19 20:34                           ` Jozsef Kadlecsik
2005-11-20 17:20                             ` Adam Rosi-Kessel
2005-11-24 11:00                               ` Jozsef Kadlecsik
2005-11-24 13:36                                 ` Adam Rosi-Kessel
2005-12-17 22:59                         ` Adam Rosi-Kessel
2005-12-18  6:42                       ` Leonardo Rodrigues Magalhães [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-10 13:13 Gabriel
2005-11-10 13:45 Adam Rosi-Kessel
2005-11-10 14:50 ` Sandro Dentella
     [not found] <20051218055403.002CDA00EA@bostoncoop.net>
2005-12-18 13:16 ` Adam Rosi-Kessel
2005-12-19 15:39   ` Re[2]: " Marcin Krol
2005-12-19 15:40     ` Adam Rosi-Kessel
2006-01-25  1:16     ` Adam Rosi-Kessel

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=43A504E3.9070706@solutti.com.br \
    --to=leolistas@solutti.com.br \
    --cc=adam@rosi-kessel.org \
    --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.