Postagens

Windows 11 não conecta na rede 5G do synology router.

Imagem
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

error: exec plugin: invalid apiVersion "client.authentication.k8s.io/v1alpha1"

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

Kubernetes - apiserver advertise address

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

Kubernetes - memcache.go:265] couldn't get current server API group list

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

GPG error: https://packages.cloud.google.com/apt kubernetes-xenial InRelease: The following signatures couldn't be verified because the public key is not available

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

Proxmox -> TrueNAS Scale - Your CPU does not support KVM extensions - como resolver

Imagem
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. 

Pfsense - qemu agent on proxmox

Imagem
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.