Tony Stohne wrote:
Yes, putting the domain/IP address in the host file works, but has the
negative side effect of being slower (at least if your host file is big.
Parsing a big hosts file slows down networking overall because of the parsing
process. If the file is small/short it's not a big prob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
pk said the following on 2008-09-14 13:25:
> Ok, good to know. I tried something simpler; putting the domain in
> /etc/hosts pointing to 127.0.0.1 (as suggested by Neil Bothwick). But
> I'll keep this in mind for the future. Thanks for the input!
>
On Sun, 14 Sep 2008 13:25:45 +0200, pk wrote:
> Ok, good to know. I tried something simpler; putting the domain in
> /etc/hosts pointing to 127.0.0.1 (as suggested by Neil Bothwick).
Incidentally, you can get a file to add to your /etc/hosts that blocks all
sorts of ad and popup server from http
Tony Stohne wrote:
HTTP requests are sent over TCP, so try a REJECT with TCP reset instead.
Something like this should do the trick, since the connection would be reset
more or less instantly avoiding the timeout:
iptables -A INPUT -s -p tcp -j REJECT --reject-with tcp-reset
iptables -A
4 matches
Mail list logo