From: Michael Tautschnig <michael.tautschnig@zt-consulting.com>
To: Pmishra@in.safenet-inc.com
Cc: netfilter@lists.netfilter.org
Subject: RE: Single IP
Date: Fri, 4 Mar 2005 12:17:09 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.62.0503041209000.7410@L01.THNET> (raw)
In-Reply-To: <20686C579479DC438276A726FE80CDAA0294CBD3@INEXCH1>
>
> - What is the client using to access your services? A web-browser?
> I Open the the portal page and click on the some link then my own service
> start and listen the server.
> - What "services" are you providing? Websites?
> I have two application name is VPX and FNC.
> - You can't have more than one application listening on port 80, so how are
> you dealing with that issue?
> My requirement is OPEN ONE tunnel( between server and client) and all the
> data will send via this tunnel. and In server side I check the packet and
> forward To appropriate server as per FLAG.
So I assume, these packets are not http-requests anymore. If you're able
to control the packets sent by the client, you could, e.g., abuse the
DSCP-field of the IP header. By setting it to some specific value, you
might be able to match it at your site and then, using the
REDIRECT-target, you could send the packets where you want.
If you are unable to control the packets sent by the client, you should
finally tell us what this is all about, i.e., you need to explain the
whole handshake.
Regards,
Michael
next prev parent reply other threads:[~2005-03-04 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 11:00 Single IP Pmishra
2005-03-04 11:17 ` Michael Tautschnig [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-04 3:57 Pmishra
2005-03-04 9:40 ` Michael Tautschnig
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=Pine.LNX.4.62.0503041209000.7410@L01.THNET \
--to=michael.tautschnig@zt-consulting.com \
--cc=Pmishra@in.safenet-inc.com \
--cc=netfilter@lists.netfilter.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