From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Source routing two services in the intranet
Date: Thu, 18 Dec 2003 00:34:06 +0000 [thread overview]
Message-ID: <marc-lartc-107170791419357@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107167842112466@msgid-missing>
Hello,
: This solution above has a drawback. If i have to provide a different
: service on a different computer in the internal network I can't, since
: every package that reaches the linux router is being redirected to the
: same computer in the internal network. Assume that besides the web
: service in 192.168.100.10-192.168.100.17 (IP alias used here) we want
: to to provide ssh service on 192.168.100.20-192.168.100.21 and want to
: source routing both services in the linux. I believe that to solve this
: i need to operate with iptables and iproute together and DNAT the
: requests according to the port it is addressed to. It seems that
: iproute by itself cannot do that. But to accomplish this i thing that a
: solid knowledge of how the packages traverse the kernel is necessary
: and that is what I am not sure about. So I would really appreciate if
: anyone could help me write the iptables and iproute rules for the
: example just mentioned. That would be a great help.
With regard to describing how a packet traverses the kernel, you will find
the KPTD and docum.org very helpful [0]. I would also suggest considering
(for your described application of the technology) that you look at the
--ctorigdst conntrack patch to netfilter [1].
-Martin
[0] http://www.docum.org/stef.coene/qos/kptd/
[1] http://www.netfilter.org/documentation/HOWTO/netfilter-extensions-HOWTO-3.html#ss3.3
Try googling for ctorigdst also!
http://www.google.com/search?q=ctorigdst
--
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/
prev parent reply other threads:[~2003-12-18 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 14:57 [LARTC] Source routing two services in the intranet azeredo
2003-12-18 0:34 ` Martin A. Brown [this message]
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-107170791419357@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.