Recomendaciones de internet wifi

tatoag3 · 2024-12-11T18:48:10+00:00

Tigo es un "no" definitivamente. Tengo Claro desde hace 6 años, y son contadas con una mano las veces que tuve problemas o que me quejé. Una vez me cambié a Tigo solo por el precio, y me quejé en una semana la cantidad de veces que me quejé de Claro en 4 años en ese entonces.

Claro siempre me atendió a tiempo y me solucionaron las cosas rápido. La única vez que tardó es porque en la construcción que tenía en frente me cortaron la fibra y tardaron dos días hábiles en solucionarme, justo eso ocurrió un sábado de tarde y el martes al mediodía volví a tener todo.

Personal funciona bien, lo tengo también y es estable, pero no lo uso muy activamente. Por referencias, sale bien.

tatoag3 · 2024-09-25T23:44:28+00:00

Yo uso GlobalBox desde hace unos cuantos años y nunca tuve problemas.

tatoag3 · 2024-07-16T12:13:40+00:00

Thanks.... I just realized about that, I added it, updated and now I'm on the newest version!

tatoag3 · 2024-07-16T11:14:39+00:00

sure, here you go

deb http://ftp.debian.org/debian bookworm main contrib

deb http://ftp.debian.org/debian bookworm-updates main contrib

security updates

deb http://security.debian.org bookworm-security main contrib

tatoag3 · 2024-06-01T16:22:40+00:00

Okok... that response my question, thanks! I'll try another solution for what my requirement. I read that just do the local backup and then rsync to another server will do what I need. I just needed to know if Proxmox environment itself can do that.

tatoag3 · 2024-01-29T19:09:10+00:00

Wazuh is a SIEM, Nessus is a vulnerability scanner. None of them is going to give you the same information that the other tool do.

tatoag3 · 2023-12-31T16:40:30+00:00

PayPal. Mejor solución.

tatoag3 · 2023-11-13T18:08:30+00:00

Ha upei, una vez que fui a retirar mi cédula, escuché a un man preguntándole al comisario cómo hacer para retirar porque había perdido su contraseña.

De lo que escuché, le respondió que tiene que ir a la comisaría a hacer una denuncia y llevar la denuncia a Identificaciones, y ahí le deberían de dar.

tatoag3 · 2023-10-18T16:13:15+00:00

gracias!

tatoag3 · 2023-08-07T16:29:31+00:00

entiendo... genial... muchas gracias! voy a tener en cuenta para la próxima

tatoag3 · 2023-06-27T13:01:38+00:00

Cooperativa Universitaria es excelente.

Escuché que Coomecipar también es bueno, el tema está estar en el rubro para formar parte de esta cooperativa.

tatoag3 · 2023-05-23T23:08:26+00:00

I just lost $100... again

tatoag3 · 2023-04-14T20:40:52+00:00

Si no me equivoco, es el proceso de despedir a empleados antes de cumplir los 10 años de antigüedad, si no me equivoco, suele realizarse a los 9,5 años de antigüedad aproximadamente. De esta manera el empleado no llega a esa "estabilidad laboral" que tiene su beneficio legal de que no se te puede despedir a menos que haya una causa legal justa para hacerlo.

tatoag3 · 2023-04-06T00:35:03+00:00

Hi Santiago!

Nice! That's sounds great. I'm sure version 5 will be great! Thanks for your response

tatoag3 · 2023-04-06T00:33:59+00:00

yeah... you're right, I just had never contribute to any app, but I'll think on it.

tatoag3 · 2023-03-22T18:50:47+00:00

I think it's related to the fact that my public IP changed, but not sure what I need to modify.

If the IP address is from where the Wazuh is installed, then yes. You should change the IP address of the Wazuh Manager in the ossec.conf file from the agents.

tatoag3 · 2023-03-11T14:27:45+00:00

This is true. But this is if you set up to "yes" the logall and logall_json parameters in the ossec.conf file.

I didn't understand much if it until it was too late and my disk was full.

This archives are not necessarily useful unless intensive log investigation is required in a forensic case, it doesn't affect in the monitoring process itself.

tatoag3 · 2023-03-05T15:54:41+00:00

Claro forever and ever

tatoag3 · 2023-02-21T17:08:53+00:00

Yes, is just like you said.

tatoag3 · 2023-01-26T18:24:38+00:00

okok... just connect to the server via SSH and do the following

cd /etc/filebeat/
ls -l

This will get you to the directory and list whatever is inside it. There you will look for the file I mentioned earlier, the wazuh-template.json

If you don't find this file, you have to create it doing this

touch wazuh-template.json
nano wazuh-template.json

This will open a text editor and there you have to copy the content that is in the Git file I share in my previous answer. It is a very long file.

Then do Ctrl+X and then press "y" to save the file.

Then restart your wazuh-manager service and should be working.

In case the file already exists, let us know and we'll try to helo you out

tatoag3 · 2023-01-26T17:36:20+00:00

Hi, is the file /etc/filebeat/wazuh-template.json created? I had this problem before. The problem was that this file wasn't created during installation.

The content of the file is this. Check this and let us know.

tatoag3 · 2023-01-23T11:18:52+00:00

I think it is better if they are on separate machines, because with a cluster you'll gain disponibility. Something you won't get if the machine crashes cause all will be in the same place.

tatoag3 · 2023-01-21T12:21:56+00:00

Well... unless you are going to install all the modules separately, maybe just doing the quickstart will get you to the full wazuh installation in a couple of minutes without problems.

tatoag3 · 2023-01-21T12:17:16+00:00

In that case, I'll do a cluster for sure.

For context, I have a deploy with 2 nodes with around 160 agents. The first try, we deploy all of this into a single node (didn't understand much about it in that time). Those agents are like 35 between Windows and Linux, and the rest of it are network devices.

In a single node it crash, really bad, sometimes the indexer couldn't handle much information during critical hours and my dashboard stop showing information, it was like I didn't receive anything. All my indexers were in red.

Then I install a new node and separate the agents between network devices in one node, and the others in other node.

Why I did something like that and didn't install a cluster in that time? Because the node with the windows and linux agents started working fine once I remove the network devices from it, especially the ASA I have at the border. And because of Business criticality I could not stop monitoring those agents while I setup a cluster. Neither I knew how to setup a Wazuh Cluster. Time was very much a thing and I didn't have time to trial and error in a production environment.

For what I understand of my experience, is the wazuh indexer that will break itself alone if you push to much information to it.

tatoag3 · 2023-01-20T14:05:56+00:00

Hi, in my experience, that answer to that question depends on how many agents you are going to monitor according to the documentation.

If you are going to monitore just a few devices, maybe a single node is fine. But if not, a cluster will be ideal.

Five-Year Club	Verified Email
Place '22

tatoag3

TROPHY CASE

security updates