blocking sites

[benicio]

---

gusto nako ibutang sa deamon ang script pero muout put ra ug lines sa top command ang argument. which is kung equal to one line ra ang mugawas ug wa ga-access sa net thru firefox ang user, the script should at least delete the appended lines in hosts file.

unsaon nako pagsuwat atu nga script nga mu-grep ug mudelete sa lines?
mas sayun ba kung pidof na lang ang sa argument?

[CentOS]

nganong 127.. man nga localhost man na nga ipstack?

nablock jud ang yahoo?

Katong imong 216.34.250.11 www.istorya.net, di na sya mo work kay di man ikaw si 216.34.250.11. etc/hosts works for incomming access if you use your localhost IP hence, you are (in a way) protecting services on your computer.

127... works because that's the loopback address.

You can also use squid or iptables in this case.

[benicio]

thanks.
naa koy nakit-an nga hosts.allow nna pod hosts.deny para asa man ni sila?

[turbomark]

mahitungod ba ni sa denyhost?

[CentOS]

thanks.
naa koy nakit-an nga hosts.allow nna pod hosts.deny para asa man ni sila?

Before anything else, please take note that /etc/hosts was not really meant for blocking but instead, for mapping. You map an IP to a correspoinding domain name, much like what DNS does. The reason why putting (ex. 127.0.0.1 istorya.net) gives you the impression that it's blocking is because you are telling your machine that istorya.net is your own machine (when obviously it's not). If you were running a web server on that machine, surfing to istorya.net in the example above would actually open the web files from your own machine and won't connect to the remote host (the real istorya.net).

host.deny and host.allow are used to deny and allow hosts from accessing your machine. So pasulod, dili pagawas.

[waterboy0911]

Before anything else, please take note that /etc/hosts was not really meant for blocking but instead, for mapping. You map an IP to a correspoinding domain name, much like what DNS does. The reason why putting (ex. 127.0.0.1 istorya.net) gives you the impression that it's blocking is because you are telling your machine that istorya.net is your own machine (when obviously it's not). If you were running a web server on that machine, surfing to istorya.net in the example above would actually open the web files from your own machine and won't connect to the remote host (the real istorya.net).

host.deny and host.allow are used to deny and allow hosts from accessing your machine. So pasulod, dili pagawas.

heheh na nose bleed ko gamay..seriously gamay lang ako na sabtan.. but anyways at least naa nasabtan.

[benicio]

Before anything else, please take note that /etc/hosts was not really meant for blocking but instead, for mapping. You map an IP to a correspoinding domain name, much like what DNS does. The reason why putting (ex. 127.0.0.1 istorya.net) gives you the impression that it's blocking is because you are telling your machine that istorya.net is your own machine (when obviously it's not). If you were running a web server on that machine, surfing to istorya.net in the example above would actually open the web files from your own machine and won't connect to the remote host (the real istorya.net).

host.deny and host.allow are used to deny and allow hosts from accessing your machine. So pasulod, dili pagawas.

thanks.
mao diay naa sad ang http://localhost diri
murag sama ra sad ni sa pagbrowse ug html files in the machine file:///path/to/files/

[CentOS]

heheh na nose bleed ko gamay..seriously gamay lang ako na sabtan.. but anyways at least naa nasabtan.

Hehe asa man ato ang wala nimo masabtan, basin mas ma klaro pa nako explain.. usahay man gud, dili ko masabtan kung ako mag explain kay naa koy tendency mag tuyok2x

Btw, kanang /etc/hosts file sa linux, it's the same with the hosts file in windows, kanang naa sa \windows\system32\drivers\etc and they perform the same function.