From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Host blocking
Date: Wed, 18 May 2005 11:08:26 -0400 [thread overview]
Message-ID: <20050518150826.GA4863@bender.817west.com> (raw)
In-Reply-To: <000901c55b78$87815390$f00aa9c0@winxp>
On Wed, May 18, 2005 at 10:09:27AM +0300, Wennie V. Lagmay wrote:
> Hi Jason,
>
> I try the the configuration and it is not working the way I want, maybe I
> need to elaborate my config.
>
> The 1st linux server is the firewall: It do forwarding, firewalling and
> natting it has 2 NIC card. The 1st NIC card IP is 203.172.xxx.97 / 30 which
> is connected to the internet , The 2nd NIC card is 203.172.xxx.105 / 28
> connected to LAN. local IP block for the clients 192.168.10.0/24 which is
> NAtted to 203.172.xxx.112-114.
>
> The second is a linux server is a proxy server: It also have 2 NIC card.
> 1st NIC card is 203.172.xxx.102 /30 which is connected to the internet, the
> 2nd NIC card is 203.172.xxx.106 / 28 connected to LAN.
>
> The process work like this: a client with ip address 192.168.10.2 wants to
> connect to the internet it will pass through firewall, the firewall then
> forward it to proxy and the will get the page then return it back to the
> client. in this case no natting is involve. the proxy server gets the page
> by its ip address then return it to 192.168.10.2. On the other hand if the
> same client want to chat, it will go to firewall, the firewall then
> translate the ip 192.168.10.2 to 203.172.xxx.112 then the client can chat.
>
> Our system work this way, As I mention they client can define our own proxy
> or our ISP's proxy, But I want every body to use our own proxy becaus we
> have dalay_pool.
k--slight modification of previous rules:
# allow internal machines to connect to our proxy
iptables -A FORWARD -p tcp --syn -s 192.168.10.0/24 \
-d $OUR_PROXY_IP --dport $PROXY_PORT -j ACCEPT
# drop packets from inside net to ISP Proxy
iptables -A FORWARD -p tcp --syn -s 192.168.10.0/24 \
-d $ISP_PROXY_IP -j DROP
if your FORWARD policy is set to DROP, and you only allow specific
services through the firewall from the internal network, keeping your
users from connecting to things they shouldn't connect to becomes much
easier.
-j
--
"Black Knight: You see kids? Your father's nothing but a fizzle!
Peter: Hey, pal, nobody calls me a fizzle and gets away with it! Except
for that one guy who called me a fizzle and then he ran off. But
nobody else has ever called me a fizzle and got away with it! Actually
though, he was the only one who ever called me a fizzle. But after
today, only half the people who've called me a fizzle will have gotten
away with it!"
--Family Guy
next prev parent reply other threads:[~2005-05-18 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 10:30 Host blocking Wennie V. Lagmay
2005-05-17 11:12 ` Jörg Harmuth
2005-05-17 13:09 ` Askar
2005-05-17 13:17 ` wlagmay
2005-05-17 13:14 ` Jason Opperisano
2005-05-17 13:39 ` Wennie V. Lagmay
2005-05-17 13:44 ` Jason Opperisano
2005-05-17 13:50 ` Wennie V. Lagmay
2005-05-18 7:09 ` Wennie V. Lagmay
2005-05-18 15:08 ` Jason Opperisano [this message]
2005-05-19 4:10 ` Wennie V. Lagmay
2005-05-19 18:38 ` Jason Opperisano
2005-05-17 16:06 ` Taylor, Grant
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=20050518150826.GA4863@bender.817west.com \
--to=opie@817west.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