Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Nicolas Ross" <rossnick-lists@cybercat.ca>
To: netfilter@lists.netfilter.org
Subject: Re: DNAT Not working
Date: Mon, 12 Jul 2004 12:13:13 -0400	[thread overview]
Message-ID: <059201c4682b$21f95f90$1a07a8c0@civic2k> (raw)
In-Reply-To: 200407121659.51187.Antony@Soft-Solutions.co.uk



> On Monday 12 July 2004 4:12 pm, Nicolas Ross wrote:
>
> > DNAT to 172.16.190.5, port 80 works fine.
> > DNAT to 172.16.190.143, port 5003 is not.
> >
> > In /proc/net/ip_conntrack, I see :
> >
> > tcp      6 118 SYN_SENT src=x.x.x.x dst=x.x.x.x sport=49502 dport=5003
> > [UNREPLIED] src=172.16.190.143 dst=x.x.x.x sport=5003 dport=49502 use=1
>
> Okay, so that means the firewall passed the SYN packet through from the
client
> to the mac, but hasn't seen the SYN-ACK back from the mac to the client.
>
> > With iptables -nvL, I see packet counter rising for the 2 rules
concerning
> > port 5003
>
> That means packets are going through the firewall (one way, at least).
>
> > On the 172.16.190.143 box, wich is a mac os x box, with netstat -an |
grep
> > 5003, I see :
> >
> > tcp4       0      0  172.16.190.143.5003    x.x.x.x.62382
SYN_RCVD
>
> Okay, so it's received the SYN (and presumably tried to return the
SYN-ACK)
>
> > tcp4       0      0  172.16.190.143.5003    172.16.190.153.49342
> > ESTABLISHED
> > tcp4       0      0  127.0.0.1.5003         127.0.0.1.49184
> > ESTABLISHED
> > tcp4       0      0  127.0.0.1.49184        127.0.0.1.5003
> > ESTABLISHED
> > tcp4       0      0  *.5003                 *.*
LISTEN
>
> Yup, it's listening on TCP port 5003 alright :)
>
> Does the mac have a default route to send reply packets back to the remote
> client through the firewall?
>
> Try a packet sniffer (ethereal is good) on the link between the firewall
and
> the mac, and see if you can see packets both ways (and look at the source
&
> destination addresses).

Between the time I wrote my message, and now, I finally got my hand on it.

The probleme was that the default route on that host was not the RH
firewall, but another box wich connects with a vpn to another network at
another location, so the route back to the source host doesn't pass trough
the firewall, thus the problem...

Thanks anyway !

Nicolas



  reply	other threads:[~2004-07-12 16:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12 15:12 DNAT Not working Nicolas Ross
2004-07-12 15:59 ` Antony Stone
2004-07-12 16:13   ` Nicolas Ross [this message]
2004-07-12 16:33     ` Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2007-04-18 16:26 DNAT not working Payal Rathod
2007-04-18 17:34 ` Martijn Lievaart
2007-04-19  3:31   ` Payal Rathod
2007-04-19 11:15     ` Gáspár Lajos
2007-04-19 17:18       ` Payal Rathod
2006-12-22 15:03 Balazs Fulop
2006-12-22 20:38 ` Grant Taylor
2006-12-22 21:14   ` Pascal Hambourg
2006-12-26 20:54     ` Balazs Fulop
2004-03-18 20:26 Stuart Lamble
2004-03-18 20:49 ` John A. Sullivan III
2004-03-18 21:58   ` Antony Stone
2004-03-18 20:50 ` Antony Stone
2004-03-20 17:47   ` Stuart Lamble
     [not found] <20031224052809.18657.42710.Mailman@netfilter-sponsored-by.noris.net>
2003-12-24 10:24 ` DNAT NOT WORKING madhav bhasin
2003-12-24 10:33   ` Antony Stone
2003-12-25 18:31   ` Thomas Scheffczyk

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='059201c4682b$21f95f90$1a07a8c0@civic2k' \
    --to=rossnick-lists@cybercat.ca \
    --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