From: Phil C <flah@hell.com>
To: netfilter@lists.netfilter.org
Subject: Re: help accepting unbound addresses
Date: Sat, 15 May 2004 14:51:08 -0400 [thread overview]
Message-ID: <20040515185108.GA82869@adsl195.cofs.net> (raw)
In-Reply-To: <20040515033249.GW78829@adsl195.cofs.net>
A temporary resolution to my question, which is far from ideal (not very
scalable):
Put subnets on the loopback, to accept packets as they come in on 443.
Add a DNAT rule, for the but bound port 80 traffic, which routes traffic
out to the correct destination.
I was really hoping for something far more dynamic than this, but it'll have
to do in a pinch. The ideal solution would be to simply accept any packet
on a single interface and deliver it as local (without modifying the destination
address). That would allow me to simply route new subnets to my stunnel box
and have 0 configuration updates on the stunnel box, but alas it doesn't seem
feasible. :(
If anyone has any suggestions, please let me know.
--
<flah@hell.com>
01101000011000010110110001100110
prev parent reply other threads:[~2004-05-15 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 0:29 help accepting unbound addresses Phil C
2004-05-15 3:32 ` Phil C
2004-05-15 18:51 ` Phil C [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=20040515185108.GA82869@adsl195.cofs.net \
--to=flah@hell.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