From: Mike Fedyk mfedyk@matchmail.com
To: lartc@vger.kernel.org
Subject: [LARTC] Advanced Routing Problem
Date: Fri, 02 Mar 2001 22:58:18 +0000 [thread overview]
Message-ID: <marc-lartc-98373940417083@msgid-missing> (raw)
<PRE>Daniel Jay wrote:
><i>
</I>><i> I'm sorry if this is to the wrong emailing list, if it is, please directly
</I>><i> me where to post this question.
</I>><i>
</I>><i> I'm going to start this email with saying I _think_ I've read everything I
</I>><i> can get my hands on about this subject, I've tried every example I can find,
</I>><i> with no luck. The second issue is that I can not upgrade to
</I>><i> netfilter/iptables because one of the applications I need requires "loose
</I>><i> udp routing". Either the examples in the mailing list do not apply or I
</I>><i> must be doing something wrong.
</I>><i>
</I>><i> Here is my problem, everything "works" but _all_ traffic goes out the
</I>><i> 207.152.31.185 internet connection. Here is what I need to happen, when
</I>><i> somebody connects to 216.254.12.42 port 80 that all traffic for that
</I>><i> "session" be answered back as 216.254.12.42 plus go out that internet
</I>><i> connection.
</I>><i>
</I>
You will also notice if you're using MASQ, that the responses will come back
from 207.152.31.185 with connections, but not via tcp or udp.
You can choose to have entire computers using the sdsl to access the internet.
Make another routing table (you need policy routing) and use `ip rule` to have
the packets from those comps go to a different table with it's default route set
to come from 216.254.12.42.
If that isn't granular enough, you can route based on IP mark, and have some
rules on your incoming chain (in 2.2) change the mark, and use `ip rule` to use
a different table.
Another thing you can do, is have a port forward daemon do all this for you.
Though, you won't get the masqing and your servers will think all connections
are from the gateway. This can be a temporary measure.
><i> JayC Daniel
</I>><i> Senior Security Engineer
</I>><i> Security Integration
</I>
Hmm, nice title. What'd you have to do to get to that position?
Mike
</PRE>
next reply other threads:[~2001-03-02 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-02 22:58 Mike [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-23 16:02 [LARTC] Advanced Routing Problem Daniel
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-98373940417083@msgid-missing \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox