From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: redirect to webpage
Date: Thu, 01 Nov 2007 11:19:11 -0500 [thread overview]
Message-ID: <4729FC7F.9050602@riverviewtech.net> (raw)
In-Reply-To: <20071031205706.4i9hlqmw008ck4g0@mail.harrisonburg.k12.va.us>
On 10/31/07 19:57, dhottinger@harrisonburg.k12.va.us wrote:
> WOW. Quite a lot of information. Its been my goal to get my proxy
> server and firewall on the same box. Havent got there yet. My firewall
> is running on an old pII ibm workstation with 3 nics, doing routing, nat
> etc. and has worked very well. Hardly ever breaks a sweat, so it hasnt
> been a priority like mail, etc. The main reason I used the url is
> because the ip addresses of the sites change quite a bit also. Im just
> about ready to throw the towel in, there is just to many proxiifier
> sites for people to use to circumvent my filter. I guess the best way
> to do this would not run a transparent proxy, which maybe what I end up
> doing sometime in the future. As always thanks for the advise.
*nod*
That is why I have found a liking of the unix way of thinking where you
lock down everything and just open up what is needed.
Good luck with your problem(s). If you are curious, you could probably
come up with a chain and sub-chain structure that only part of the
sub-chain(s) were updated via cron jobs when things change.
Grant. . . .
prev parent reply other threads:[~2007-11-01 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 15:11 redirect to webpage dhottinger
2007-10-31 16:37 ` Grant Taylor
2007-10-31 17:02 ` dhottinger
2007-10-31 18:34 ` Grant Taylor
2007-11-01 0:57 ` dhottinger
2007-11-01 9:21 ` G.W. Haywood
2007-11-01 9:56 ` Pascal Hambourg
2007-11-01 16:19 ` Grant Taylor [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=4729FC7F.9050602@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@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