Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am using NETGEAR Wireless-N-300 Router Model among a couple of people to share internet connectivity.

I blocked facebook.com, but the users are access on protocol https, I blocked some ip´s of facebook but they have many IPs. I would like to block https://www.facebook.com/

Is there a way to do this with the above router.

share|improve this question

closed as off topic by HopelessN00b, petrus, gWaldo, Michael Hampton, rnxrx Oct 4 '12 at 18:42

Questions on Server Fault are expected to relate to professional server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

    
Could you go through your questions and accept an answer if they solved your problem - a low accept rate discourages people from answering. –  tombull89 Oct 4 '12 at 9:35
    
from the description it doesn't look like this device is suitable as a company firewall. check the manual if it supports advanced firewall rules at all. and get your accept rate up. –  Gryphius Oct 4 '12 at 9:37
    
"0% accept rate" - You should work on that. –  Chris S Oct 4 '12 at 13:34
    
To block facebook is to throw an ineffective technical solution at a social problem. –  Falcon Momot Jun 29 '13 at 5:21
add comment

2 Answers 2

It doesn't look like you can on that model.

But it's easy enough to accomplish what you want - I'd tackle it by setting the company DNS server (or, if you don't have one, heaven forbid... client hosts files) to resolve facebook.com to a loopback address. I typically don't use 127.0.0.1, because that can be confusing when troubleshooting, but something odd in that /8, like 127.127.127.127 works well.

share|improve this answer
add comment

You may (depending on your environment) be able to get away with blocking 443 altogether, or allowing only specific IPs. With routers such as this, your choices will be limited.

The DNS solution is reasonable, and cheap.

If you want more granularity and ease of management or reporting down the line, you're going to need a better router (something more in the UTM vein perhaps) or to run a web proxy (which you could build with squid, or buy).

share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.