From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] transparent PAT
Date: Wed, 27 Nov 2002 20:40:01 +0000 [thread overview]
Message-ID: <marc-lartc-103842970908061@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103842383732507@msgid-missing>
Nickola,
: Well, in fact I tried a solution with doing DNAT (i.e. destination NAT) in
: both directions - from the client to the server and vice versa. With tcpdump
: I saw that packet are going both diorections, but the client application
: refused to accept them. I'm talking about irc. I mean there weren't any
: errors, given by the client, just silence. :)
OK! Now I'm confused. Why would you need to do DNAT in both directions?
I thought you said you were using ipchains? If you have iptables, DNAT is
really the answer.....you would DNAT anything inbound from machine A to
machine B. Then let the connection tracking take care of the rest.
If you are using DNAT both directions, I'm guessing I don't quite
understand your intended configuration or you don't quite understand DNAT.
Either way, if you can use DNAT, read up on how to use DNAT at
http://iptables-tutorial.frozentux.net/ and try again.
-- OR --
<snip>
: Ehm, yes, I tried with priorities 200 and the default ones, which ip rule
: puts at the end - i.e. around 32765 and below.
So, we are agreed....policy based routing probably isn't the answer in
this case.
: > After you have done:
: > # echo 1 > /proc/sys/net/ipv4/ip_nonlocal_bind
: > can you do something like this:
: > # nc -nlvv -p 3001 -s 77.77.77.77
: > Where 77.77.77.77 is an IP not in use anywhere on your box?
: Yes, I can, but do I have a way to check that someone is indeed
: listening on this port? Except locally, I mean. Beacuse netcat is
: binding to the port with no complaints.
You should be able to use "netstat -ntl" to display the listening sockets
on your system.
: > If you were using redir, why doesn't the following work:
: > # redir --laddr=x.x.x.x --lport™3 --caddr=y.y.y.y --cport™3 --transproxy
: No, it yells
: target: connect: Invalid argument
The poor thing is in pain--that's why it's yelping! I don't have any
problem with the above command line....are you certain that transproxy
support was compiled into your redir?
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-27 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 19:02 [LARTC] transparent PAT Nickola Kolev
2002-11-27 19:20 ` Martin A. Brown
2002-11-27 20:15 ` Nickola Kolev
2002-11-27 20:40 ` Martin A. Brown [this message]
2002-11-27 21:29 ` Nickola Kolev
2002-11-27 22:39 ` Julian Anastasov
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=marc-lartc-103842970908061@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--cc=lartc@vger.kernel.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.