From: Nickola Kolev <nikky@mnet.bg>
To: lartc@vger.kernel.org
Subject: [LARTC] transparent PAT
Date: Wed, 27 Nov 2002 19:02:26 +0000 [thread overview]
Message-ID: <marc-lartc-103842383732507@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
Hello, everyone!
I would like to solve the following problem. Btw, I'm terribly
sorry about the pseudo-asciiart, but that's all I can paint as
a tropology. I'm hoping it'll be enough.
----Internet----
|
|
|
eth0
machine A
routing+ipchains
eth1
|
------------------ machine B
So, given I'm running kernel 2.4.19 and using ipchains (don't
ask me why, but I'm bounded to this config), I would like to
reroute everything that's passing thru eth1 on machine A
from the internal lan and has dport XXXX to the same port
on machine B. The hole thing has to be completely transparent.
I tried some "advanced routing" stuff, like marking those packets
with fwmark and building a separate routing table for them,
but alas. Notice that the two machines are on the same LAN segment.
I've already tried also some userspace solutions, which didn't
work, like redir, tircproxy, transproxy, etc. but they didn't
work either, complaining abount not able to bind to non-local
port. And yes (mr. Brown), I know about the
/proc/sys/net/ipv4/ip_nonlocal_bind switch, listed in
plorf.net/linux-ip/.
Any suggestions (or help) are very much welcome.
10q for your time,
Nickola
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2002-11-27 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 19:02 Nickola Kolev [this message]
2002-11-27 19:20 ` [LARTC] transparent PAT Martin A. Brown
2002-11-27 20:15 ` Nickola Kolev
2002-11-27 20:40 ` Martin A. Brown
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-103842383732507@msgid-missing \
--to=nikky@mnet.bg \
--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.