From: Peter Surda <shurdeek@routehat.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routing incoming port 82
Date: Mon, 27 Jun 2005 18:32:24 +0000 [thread overview]
Message-ID: <2005527203224577@mail.routehat.org> (raw)
In-Reply-To: <42C03336.7000209@phreaker.net>
On Tue, 28 Jun 2005 01:11:18 +0800 ro0ot <ro0ot@phreaker.net> wrote:
>Hi,
hi,
[cut]
>$IPTABLES -t nat -A PREROUTING -i eth1 -p tcp --dport 82 -j DNAT --to
>10.59.2.2:80
>$IPTABLES -t nat -A PREROUTING -i eth2 -p tcp --dport 82 -j DNAT --to
>10.59.2.2:80
>
>The problem is sometimes when I access the Server A's web service using
>the following link below, after like few minutes...it cannot be accessible.
This looks like bad routing, so I expect you should set up policy based routing.
You could use CONNMARK to remember the interface the connection is coming in and
then use a separate routing table for each of the marked packets coming the
other direction. I assume there are another options if you don't have CONNMARK,
but this looks like the most straigthforward solution.
>Regards,
>rootlinux
Yours sincerely,
Peter
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-06-27 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 17:11 [LARTC] routing incoming port 82 ro0ot
2005-06-27 18:32 ` Peter Surda [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=2005527203224577@mail.routehat.org \
--to=shurdeek@routehat.org \
--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.