Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Wennie V. Lagmay" <wlagmay@yanbulink.net>
To: Jason Opperisano <opie@817west.com>, netfilter@lists.netfilter.org
Subject: Re: Host blocking
Date: Tue, 17 May 2005 16:50:58 +0300	[thread overview]
Message-ID: <002b01c55ae7$744ebe70$f00aa9c0@winxp> (raw)
In-Reply-To: 20050517134440.GA1022@bender.817west.com

Ok so this configuration will block the ISP proxy both ip address and domain 
name on the subscribers perspective. thank you very much Jason

Ragrds,

Wennie
----- Original Message ----- 
From: "Jason Opperisano" <opie@817west.com>
To: <netfilter@lists.netfilter.org>
Sent: Tuesday, May 17, 2005 4:44 PM
Subject: Re: Host blocking


> On Tue, May 17, 2005 at 04:39:14PM +0300, Wennie V. Lagmay wrote:
>> What if they define the ip address instead of domain name? How can I
>> block/accept  both domain name and ip address?
>
> iptables rules only contain IP addresses, not host names.  in my example
> rules, proxy.ourcompany.net and proxy.ISP.net represent the IP addresses
> for those hosts.  you can use an FQDN in an iptables rule, but the FQDN is
> resolved to an IP address (or addresses) at the time the rule is loaded,
> and the rule will only use that IP address (or addresses) going forward.
>
> -j
>
> --
> "Chris: Dad, what's the blowhole for?
> Peter: I'll tell you what it's not for. And when I do, you'll understand
> why I can never go back to Sea World."
>        --Family Guy
> 



  reply	other threads:[~2005-05-17 13:50 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 [this message]
2005-05-18  7:09   ` Wennie V. Lagmay
2005-05-18 15:08     ` Jason Opperisano
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='002b01c55ae7$744ebe70$f00aa9c0@winxp' \
    --to=wlagmay@yanbulink.net \
    --cc=netfilter@lists.netfilter.org \
    --cc=opie@817west.com \
    /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