All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henry Ritzlmayr <h.ritzlmayr@gmx.at>
To: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: Redirecting incoming traffic to 127.0.0.1
Date: 21 Mar 2003 17:58:10 +0100	[thread overview]
Message-ID: <1048265890.1492.144.camel@localhost.localdomain> (raw)
In-Reply-To: <016101c2efbb$db2b8360$8201a8c0@daviddesktop>

SNAT ist only valid in the POSTROUTING chain. But even that didn´t do 
the trick. 
Do you know any way to check what really happens with the packet since
tcpdump only shows it before natting? 
If there is no tool/command or anything like that - than it looks like I
found something to refreshen my c/c++ skills.

Henry


Am Fre, 2003-03-21 um 16.09 schrieb David Ruggles:
> I think (if I understand the problem) I would try this:
> 
> iptables -t nat -A PREROUTING -p tcp -d 172.16.172.12 -j
> DNAT --to-destination 127.0.0.1
> iptables -t nat -A PREROUTING -p tcp -d 127.0.0.1 -j SNAT --to-source
> 127.0.0.1
> 
> Please let me know if this works.
> 
> Thanks,
> David Ruggles
> 
> CCNA MCSE (NT) CNA A+
> Network Engineer, Safe Data, Inc
> 910-285-7200    david@safedatausa.com
> 0100011101101111011001000110110001101111011101100110010101110011011110010110
> 111101110101
> ----- Original Message -----
> From: "Henry Ritzlmayr" <h.ritzlmayr@gmx.at>
> To: "Netfilter Mailing List" <netfilter@lists.netfilter.org>
> Sent: Friday, March 21, 2003 9:31 AM
> Subject: Redirecting incoming traffic to 127.0.0.1
> 
> 
> > I have a service running on a box wich is only able to bind to 127.0.0.1
> > (hardcoded and I can´t get the source to change it). Since I want to use
> > it from any other box the only way to solve that I think is to nat
> > incoming packets to 127.0.0.1.
> >
> > IPTABLES -t nat -A PREROUTING -p tcp -d 172.16.172.12 -j DNAT
> > --to-destination 127.0.0.1
> >
> > and many others wich I tried don´t work.
> >
> > If I understood REDIRECT correctly it only changes to the local IP where
> > the packet came in (in my situation 172.16.172.12) wich also not solves
> > the problem.
> >
> > any ideas?
> >
> > Henry
> >
> >
> 



  parent reply	other threads:[~2003-03-21 16:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 14:31 Redirecting incoming traffic to 127.0.0.1 Henry Ritzlmayr
2003-03-21 14:51 ` Negrea Mihai
2003-03-21 17:05   ` Henry Ritzlmayr
     [not found] ` <016101c2efbb$db2b8360$8201a8c0@daviddesktop>
2003-03-21 16:58   ` Henry Ritzlmayr [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-21 17:34 Daniel Chemko

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=1048265890.1492.144.camel@localhost.localdomain \
    --to=h.ritzlmayr@gmx.at \
    --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.