From: Michael Gale <mgale@utilitran.com>
To: netfilter@lists.netfilter.org
Subject: Re: Help with iptables
Date: Wed, 10 Dec 2003 17:46:24 -0700 [thread overview]
Message-ID: <20031210174624.010db97c.mgale@utilitran.com> (raw)
In-Reply-To: <FB11F223A1DE69499D299308731DD413014A2A@mail.SBPC>
Hello,
Why not run squid only on the internal interface .. can you not provide squid with the IP or interface to listen on ?
Also iptables -A INPUT -i external_interface -p tcp --dport 3128 -j DROP
should do the trick .... if you set a default policy to DROP and only pass the things you want. That would be better :)
iptables --policy INPUT ACCEPT
iptables --policy OUTPUT ACCEPT
iptables --policy FORWARD ACCEPT
Michael.
On Wed, 10 Dec 2003 15:45:52 -0800
"Bryan Dyson" <lan_administrator@solanapres.org> wrote:
>
> Hi folks,
>
> I've got my iptables setup and working with one small glitch. My ISP
> says I'm an open proxy.
> What I'm trying to do is set a rule in iptables that will drop port 3128
> requests coming from the outside but still allow my internal network to
> use the proxy on this port.
> I've tried the following, but they seem to shut down routing of e-mail
> from the internal mail server:
>
> -A PREROUTING -I eth1 -p tcp -m tcp --dport 3128 -j DROP
> And
> -A PREROUTING -I x.x.x.x (public IP) -p tcp -m -tcp --dport 3128 -j DROP
>
>
> If anyone could help I'd appreciate it.
>
> Bryan Dyson
> LAN/db Administrator
> Solana Beach Presbyterian Church
> 858-509-2580
> Shelby 5.4.1472
>
>
>
--
Michael Gale
Network Administrator
Utilitran Corporation
next prev parent reply other threads:[~2003-12-11 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 23:45 Help with iptables Bryan Dyson
2003-12-11 0:31 ` John A. Sullivan III
2003-12-11 0:46 ` Michael Gale [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-03 9:22 Tahmid Quazi
2003-06-04 18:32 ` Aldo S. Lagana
2003-06-05 4:41 ` Jerry M. Howell II
2003-06-03 9:22 help " Tahmid Quazi
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=20031210174624.010db97c.mgale@utilitran.com \
--to=mgale@utilitran.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