From: "hare ram" <hareram@sol.net.in>
To: netfilter@lists.netfilter.org
Subject: Re: Newbie Question -forcing to pass in squid
Date: Mon, 14 Oct 2002 17:08:45 +0530 [thread overview]
Message-ID: <028c01c27376$41225760$7cfcc5cb@nextto> (raw)
In-Reply-To: 771DD65729F96D41B132C6189EE644553D19CD@sydexch1
yes thats true
better u deny all going directly
deny them all who want to go directly in the rule
allow them who are going through the proxy
best of luck
hare
----- Original Message -----
From: "Kevin Saenz" <ksaenz@citistreet.com.au>
To: "Flávio Brito" <flavio@gral.com.br>; <netfilter@lists.netfilter.org>
Sent: Monday, October 14, 2002 10:16 AM
Subject: RE: Newbie Question -forcing to pass in squid
I guess there are a few things I can see here, there are a number of
solutions for this problem.
first you deny web access to all but one machine, through the firewall.
This will stop users from cheating by removing the proxy settings.
second, you could also install squid on your firewall and allow the users
through that
-----Original Message-----
From: Flávio Brito [mailto:flavio@gral.com.br]
Sent: Monday, October 14, 2002 12:03 PM
To: netfilter@lists.netfilter.org
Subject: Newbie Question -forcing to pass in squid
Dear Friends
I have two machines, and I trying to force all port 80 traffic to pass
in SQUID 3128. But when people unset proxy in browser, they bypass SQUID
to the Internet . I cannot put transparent proxy, because SQUID is
authenticating.
Suggestions?
Thanks
Flávio
----------------------------------------------------------------------
FW
|-------------------------------|
| eth0 - 200.1.2.3 |----------------------> [INTERNET]
| eth1 - 192.168.1.1 |
|-------------------------------|
|
|
SQUID
|
|-------------------------------|
| eth0 - 192.168.1.33 |
|-------------------------------|
|
|
INTERNAL_LAN
|
|-------------------------------|
| 192.168.1.0/24 |
|-------------------------------|
My Example
iptables -F
iptables -A INPUT -i lo -p all -j ACCEPT # - Allow
self access by loopback interface
iptables -A OUTPUT -o lo -p all -j ACCEPT
iptables -A INPUT -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT
#- Accept established connections
iptables -A FORWARD -o eth0 -j ACCEPT
iptables -t nat -A POSTROUTING -s $INTERNAL_NET -o $EXT -j MASQUERADE
iptables -t nat -A PREROUTING -p tcp --dport 80 -j ACCEPT -d
192.168.1.33
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT
--to-port 3128
next prev parent reply other threads:[~2002-10-14 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 4:46 Newbie Question -forcing to pass in squid Kevin Saenz
2002-10-14 11:38 ` hare ram [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-14 2:03 Flávio Brito
2002-10-14 9:10 ` Antony Stone
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='028c01c27376$41225760$7cfcc5cb@nextto' \
--to=hareram@sol.net.in \
--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