De tudo mais um pouco

Introdução: Navegar pelas águas turbulentas da tecnologia Wi-Fi pode ser um desafio. Recentemente, encontrei um problema intrigante que muitos usuários de Wi-Fi podem enfrentar, especialmente ao lidar com as frequências mais recentes e rápidas, como a 5GHz. Neste post, vou compartilhar minha experiência pessoal de como eu resolvi um problema de conexão persistente com a rede Wi-Fi 5GHz no meu dispositivo Windows. O Problema: Tudo começou quando percebi que meu dispositivo Windows não conseguia se conectar à minha rede Wi-Fi de 5GHz, apesar de outros dispositivos se conectarem sem problemas. Curiosamente, a conexão com a rede de 2.4GHz funcionava perfeitamente. Isso me levou a uma série de experimentos e testes para identificar e resolver o problema. Os Testes: Minha jornada de solução de problemas começou com o básico: reiniciar o roteador e o dispositivo, e verificar se o adaptador de rede do Windows suportava a frequência de 5GHz - e sim, ele suportava. A seguir, tentei atualizar os ...

Got this error after installing a EKS cluster on AWS. I already had the aws cli installed using apt on ubuntu 22. After some search, the solution that solved was installing manually the aws cli.  curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip" unzip awscliv2.zip sudo ./aws/install

On vagrant I built a kubernetes cluster with ansible and noticed that the kubeadm init was not using the private interface created on vagrant. So to avoid that, ti changed the command with the parameter --apiserver-advertise-address to use the private ip of the master.  - name : Start the cluster   shell : kubeadm init --apiserver-advertise-address={{ inventory_hostname }} --pod-network-cidr 10.50.0.0/16 --cri-socket /run/containerd/containerd.sock   register : kubeadm_init_output   when : not file_exists.stat.exists

Facing the error below on Ubuntu 22.04 on vagrant. Error showing after halting and powering up the vms again. Checking the journal logs and tested was just a matter to disable swap on ubuntu. root@master:/etc/kubernetes# kubectl get pods E1212 12:55:53.292062    1865 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused E1212 12:55:53.292515    1865 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused E1212 12:55:53.294534    1865 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused E1212 12:55:53.295070    1865 memcache.go:265] couldn't get current server API group list: Get "https://1...

Trying to install Kubernetes on Ubuntu 22.04 and I have the error below: ubuntu@test-vm-1:/etc/apt/sources.list.d$ sudo apt update Hit:1 https://download.docker.com/linux/ubuntu jammy InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:5 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Get:6 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB] Get:2 https://packages.cloud.google.com/apt kubernetes-xenial InRelease [8993 B] Err:2 https://packages.cloud.google.com/apt kubernetes-xenial InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05 Reading package lists... Done W: GPG error: https://packages.cloud.google.com/apt kubernetes-xenial InRelease: The following signatures couldn't be verified because the public key is not...

Bom, tive o erro do titulo, estou testando o TrueNAS Scale no proxmox no meu homelab. Fazendo a verificação direto no shell do node do proxmox, a extensão svm de virtualização da cpu AMD que estou usando estava ativa, então não era necessário ativar nada na BIOS. Foi então que pesquisando melhor encontrei esse excelente tutorial: https://ostechnix.com/enable-nested-virtualization-in-proxmox/ Tem como resolver usando o comando qm, somente precisar configurar a CPU da VM para ser do tipo HOST. No caso, fiz direto pela web interface mesmo.  Antes desligue a VM e ligue de novo após alterar.  Após isso consigo no TrueNAS usar o recurso de virtualizar. 

Ok, will just leave this here. Was trying to get qemu agent running on pfsense 2.7. Just follow the commands on the script on github: https://github.com/Weehooey/pfSense-scripts/blob/main/install-qemu-guest-agent.sh And here the discussion about the issue: https://forum.netgate.com/topic/162083/pfsense-vm-on-proxmox-qemu-agent-installation/12 EDIT: Very important detail. Perform the settings as on the github above but enable the qemu guest agent on the web interface, and AFTER that, power off and power on the VM, DO NOT RESTART.  To apply the settings you need power off and power on.

Bom, chegou o dia, meu monitor 4K que comprei um tempo atrás da Philco está com faixas escuras.  Acabei comprando um LG 32UL750-W. Uma pena que estamos bem carentes de opção.  Ia tentar pegar um MSI G281UV mas além do Display Port ser 1.2 e não 1.4 como no LG não tem como regular a altura e não tem alto falante.  No Philco o alto falante quebra um galho, posso apenas redirecionar o som para ele e começar a ouvir logo de cara.  E a regulação de altura nele é muito boa, construção solida, pena que surgiu esse problema.  Como sempre estou alternando entre Mac mini, laptop do trabalho e laptop pessoal a quantidade de portas do LG além de ter USB-C compatível com o mac ajuda bastante.  Mesmo sendo painel VA não vai me incomodar.  Abaixo imagem do problema que tive. No fórum eletronicabr vi que alguém teve um problema parecido com uma TV da Philco, depois com tempo vou tentar abrir e ver se eu poderia dar um jeito. 

Found a reason here why is almost impossible deal with a react app on wsl.  My repo is located in a windows folder, everything is slow, even using npx.  If you need things fast, move your folder for inside a native folder on the wsl, a linux filesystem.  If I try  npx create-react-app app  In a windows folder, it takes ages to complete and npm start after that is very, very slow.  If I try the same commando on the /tmp on wsl, everything is fast. 

If you trying to login in a server using ssh with user and password and is crazy with messages about too many connections. Check the .ssh folder if yu have many id_rsa key files, ssh when connect try to use each file that it found on the folder. I had this issue here, after remove the file, connection went fine.

This was done on the Pfsense 2.4.5. Check disk size: [2.4.5-RELEASE][root@server1]/root: gpart show =>       63  104857537  da0  MBR  (50G)          63          1       - free -  (512B)          64  104857535    1  freebsd  [active]  (50G)   104857599          1       - free -  (512B) =>        0  104857535  da0s1  BSD  (50G)           0   98566144      1  freebsd-ufs  (47G)    98566144    5242880      2  freebsd-swap  (2.5G)   103809024  ...

I have a situation where: Frames attached on HMC using the dhcp range 192.128 But due network requirements it was necessary change the range. To avoid any problem, I opened a ticket with IBM Support and they give me the following solution: Is not need power off hte lpars on the frame. Is not need power off the frames. Not need to ask a onsite support to remove frames from power and power on again. Just access the network configuration on HMC and change the DHCP range on the interface. After that reboot the HMC. With that the DHCP lease on frame side will expire and get the new IP address. Can last 20 minutes to the frame get the new IP after the HMC rebooted. On the HMC interface you will see the frame lost connection but will be back soon, give it time. If the solution above do not work you or a onsite support will need unplug the cable on the frame side FSP port. Leave unplugged for 3  minutes and plug back. Only unplug on the frame side, not the HMC. Fortunatelly it was not nece...

To configure a project on AWX/Ansible Tower to sync with a github repo you need have: token that permit you access the repo First lets see the credential. You just need create one: Select Source Control as type. use the username git and on password you put your github token. Just click save.   Now create a project. As showed below on the image: Past the https link of you repo, select the credential that you have created, set the branch as master or you can leave blank. And I marked two options to clean and delete local files because I was facing a problem when the project started to sync:   After that, just start syncing and check the logs, everything should work fine.