Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Redes Sociales

    Scheduled Pinned Locked Moved Español
    13 Posts 4 Posters 4.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      javcasta
      last edited by

      Hola.

      Debes tener reglas que:

      Permita consutas dns de tu lan a tu servidor/es DNS
      Permita conectarse desde tu lan a la ip del proxy (normalmente la ip lan del pfSense) al puerto que use (estandard 3128 o 8080)
      Deniegue (block o reject) el tráfico http (tcp80) y https (tcp 443) <= de esta froma te aseguras que nadie navegue sin proxy

      Y si usas wpad un wpad.dat/proxy.pac bien configurado.

      Salu2

      Javier Castañón
      Técnico de comunicaciones, soporte y sistemas.

      Mi web: https://javcasta.com/

      Soporte scripting/pfSense https://javcasta.com/soporte/

      1 Reply Last reply Reply Quote 0
      • A
        ardax
        last edited by

        La verdad he intentado de todo, y como les comente soy novato autodidacta. Si alguien pudiese ser un poco mas didactico para decirme como hacerlo, se lo agradeceria mucho.

        1 Reply Last reply Reply Quote 0
        • F
          Finger
          last edited by

          no vas a poder bloquear las redes sociales solo con squid. pues es muy facil saltarselo.

          facebook dispone de muchos servidores y hay que darse la tarea de bloquearlo uno a uno

          en Firewall: Aliases crea un alias que se llame FacebookIPs

          desde tu cmd haz ping a facebook.com y www.facebook.com

          y veras que cadas vez te saldrá un Ip diferente. pues bien todas esas Ips debes agregarlas en este alias
          yo actualmente tengo identificadas 36 ips diferentes y las agrego a este listado.

          y ya luego creas una regla en LAN para bloquear todo acceso.

          a mi esto me ha funcionado a la perfección.

          solo ten en cuenta que si de pronto se vuelve a mostrar facebook es porque los genios de face incorporaron un nuevo servidor y tu solo tienes que añadirlo a tus lista y ya se bloquea nuevamente.

          espero ayudar..

          saludos.

          1 Reply Last reply Reply Quote 0
          • J
            javcasta
            last edited by

            Hola.

            Las formas de bloquear un dominio, la indica pfSense en su DOC.

            https://doc.pfsense.org/index.php/Blocking_websites

            • Usando DNS overrides (como hacen los DNSBL, como el de pfBlockerNG, por ejemplo), resolviendo el dominio a 127.0.0.x

            Using DNS

            If the built in DNS Forwarder or DNS Resolver are in use, an override can be configured which will resolve the website to block to an invalid IP address (such as 127.0.0.1).

            • Como te dice Finger :Bloqueando por  lista de subredes de Facebook , haciendo una consulta a un servidor whois para encontrarlas vía su AS y hacer un alias con las subredes y bloquearlas

            Según la doc de pfsense el AS de Facebook es AS32934, (habria que asegurarse si ha cambiado << confirmado, si  es el ASN de FB el AS32934)

            To find the most current list of Facebook subnets, query a server to find subnets for their AS and make an alias from there.
            whois -h whois.radb.net – '-i origin AS32934' | awk '/^route:/ {print $2;}' | sort | uniq

            Esta es la lista de subredes que me da el AS32934

            [ mywebserver]$ whois -h whois.radb.net -- '-i origin AS32934' | awk '/^route:/ {print $2;}' | sort | uniq
            103.4.96.0/22
            129.134.0.0/16
            157.240.0.0/16
            173.252.64.0/18
            173.252.64.0/19
            173.252.70.0/24
            173.252.96.0/19
            179.60.192.0/22
            179.60.192.0/24
            179.60.193.0/24
            179.60.194.0/24
            179.60.195.0/24
            185.60.216.0/22
            185.60.216.0/24
            185.60.217.0/24
            185.60.218.0/24
            185.60.219.0/24
            204.15.20.0/22
            31.13.24.0/21
            31.13.64.0/18
            31.13.64.0/19
            31.13.64.0/24
            31.13.65.0/24
            31.13.66.0/24
            31.13.67.0/24
            31.13.68.0/24
            31.13.69.0/24
            31.13.70.0/24
            31.13.71.0/24
            31.13.72.0/24
            31.13.73.0/24
            31.13.74.0/24
            31.13.75.0/24
            31.13.76.0/24
            31.13.77.0/24
            31.13.78.0/24
            31.13.79.0/24
            31.13.80.0/24
            31.13.81.0/24
            31.13.82.0/24
            31.13.83.0/24
            31.13.84.0/24
            31.13.85.0/24
            31.13.86.0/24
            31.13.87.0/24
            31.13.88.0/24
            31.13.89.0/24
            31.13.90.0/24
            31.13.91.0/24
            31.13.92.0/24
            31.13.93.0/24
            31.13.94.0/24
            31.13.95.0/24
            31.13.96.0/19
            45.64.40.0/22
            66.220.144.0/20
            66.220.144.0/21
            66.220.152.0/21
            66.220.159.0/24
            69.171.224.0/19
            69.171.224.0/20
            69.171.239.0/24
            69.171.240.0/20
            69.171.253.0/24
            69.171.255.0/24
            69.63.176.0/20
            69.63.176.0/21
            69.63.176.0/24
            69.63.178.0/24
            69.63.184.0/21
            69.63.186.0/24
            74.119.76.0/22
            
            • Y otra forma, con squid, en su  ACLs > BlackList > (ver img)

            La más rápida y que menos afecta al rendimiento del pfSense es la del DNS (override o con pfBlockerNG), pero no informa de acceso restringido al usuario, como mucho un time out (el squid) y un not found 404 (eso el pfBlockerNG), con squid se puede informar al usuario en su página de redirección o info, de que esta denegada esa web y de esa forma el usuario no crea "incidencias" en el Dpto de informática de : "No puedo ver mi FB" :)

            Yo uso la de squid y me va bien

            Salu2

            =====

            Añadido:
            Determinar subredes de un dominio por su ASN vía whois:

            https://www.javcasta.com/determinar-subredes-de-un-dominio-por-su-asn-via-whois/

            Javier Castañón
            Técnico de comunicaciones, soporte y sistemas.

            Mi web: https://javcasta.com/

            Soporte scripting/pfSense https://javcasta.com/soporte/

            1 Reply Last reply Reply Quote 0
            • A
              ardax
              last edited by

              Tengo hecho todo eso y no me funciona nada .

              En el blacklist tengo puesto
              facebook
              facebook.com
              facebook

              y nada de nada…

              no se que podra ser, intente poner All en las redes y no me deja.. asi que puse 192.168.0.1/24

              Ya no se que puede ser...

              1 Reply Last reply Reply Quote 0
              • BBcan177B
                BBcan177 Moderator
                last edited by

                You can also auto collect ASNs with pfblockerNG. IPv4/6 Tab.  ;)

                "Experience is something you don't get until just after you need it."

                Website: http://pfBlockerNG.com
                Twitter: @BBcan177  #pfBlockerNG
                Reddit: https://www.reddit.com/r/pfBlockerNG/new/

                1 Reply Last reply Reply Quote 0
                • J
                  javcasta
                  last edited by

                  Of course,  BBcan 177.

                  PfBlockerNG is the best package in pfSense for advanced filter (Layer 3 IPv4 / IPv6, Layer 4 TCP / UDP, and Layer 7 DNSBL)

                  But if anyone does not know basic principles for filtering, at the beginning the best and the first is to learn;)
                  Thanks for the info.

                  If pfBlockerNG had a report generator as Sarg, I'm sure some administrators would change to Squid / squidGuard by pfBlockerNG, I use both.

                  regards
                  –-

                  add: An example, how to I use pfBlockerNG for block Tor >> https://www.javcasta.com/pfsense-bloqueando-tor-con-pfblockerng/ is a wonderfull tool pfBlockerNG :)

                  Javier Castañón
                  Técnico de comunicaciones, soporte y sistemas.

                  Mi web: https://javcasta.com/

                  Soporte scripting/pfSense https://javcasta.com/soporte/

                  1 Reply Last reply Reply Quote 0
                  • BBcan177B
                    BBcan177 Moderator
                    last edited by

                    @javcasta:

                    Of course,  BBcan 177.

                    PfBlockerNG is the best package in pfSense for advanced filter (Layer 3 IPv4 / IPv6, Layer 4 TCP / UDP, and Layer 7 DNSBL)

                    But if anyone does not know basic principles for filtering, at the beginning the best and the first is to learn;)
                    Thanks for the info.

                    If pfBlockerNG had a report generator as Sarg, I'm sure some administrators would change to Squid / squidGuard by pfBlockerNG, I use both.

                    regards
                    –-

                    add: An example, how to I use pfBlockerNG for block Tor >> https://www.javcasta.com/pfsense-bloqueando-tor-con-pfblockerng/ is a wonderfull tool pfBlockerNG :)

                    Thanks!

                    I have to add an option to send DNSBL alert entries to the firewall.log. I think for Logging/Reporting, its best to run a secondary Syslog software (Security Onion-ELSA, ELK, etc …) Those tools will give you so much more detail and insight into the logs. All the pfBNG IP alerts also contain a Tracker ID, which can be used as a unique identifier for a syslog application. There are a lot of other Lists that can be added to pfBNG apart from TOR... There is a script in the pfBNG thread about that...

                    I am always glad to help and learn at the same time ;)

                    "Experience is something you don't get until just after you need it."

                    Website: http://pfBlockerNG.com
                    Twitter: @BBcan177  #pfBlockerNG
                    Reddit: https://www.reddit.com/r/pfBlockerNG/new/

                    1 Reply Last reply Reply Quote 0
                    • J
                      javcasta
                      last edited by

                      Hello.

                      Are you, BBcan177, the developer of pfBlockerNG?.

                      Haha, what a surprise!!, very good and nice job, pfBlockerNG :)

                      OK, now I have no time, but when i can, I'll read pfBNG thread.

                      I am sure everybody will goes to learn with this packet, for me is very very OK.

                      Thanks and regards

                      Javier Castañón
                      Técnico de comunicaciones, soporte y sistemas.

                      Mi web: https://javcasta.com/

                      Soporte scripting/pfSense https://javcasta.com/soporte/

                      1 Reply Last reply Reply Quote 0
                      • BBcan177B
                        BBcan177 Moderator
                        last edited by

                        ;D  I have no immediate intentions to learn Español …. So I teach you and you teach the others... ok Deal :)

                        "Experience is something you don't get until just after you need it."

                        Website: http://pfBlockerNG.com
                        Twitter: @BBcan177  #pfBlockerNG
                        Reddit: https://www.reddit.com/r/pfBlockerNG/new/

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.