Angel Nunez Mencias

the ping to `10.69.1.62` which should be the gateway pod seems to be working. So at least that there is a rule in cilium blocking the vxlan traffic port (4789)...

Could you please also post the logs from the gateway pod init container? This is the one setting up the ip, routes and iptables of the gateway. What is your...

@legalgig - glad you got it working - is there any disadvantages on using native routing? Or why is not vxlan on vxlan working? Ideally we will add the instructions...

What are your network policies? You should have: ``` kind: NetworkPolicy apiVersion: networking.k8s.io/v1 metadata: name: mediaserver spec: podSelector: {} ingress: - from: # Only allow ingress from K8S - ipBlock:...

Just another thing to consider - there are some VPNs that route ALL traffic through them so the DHCP server gets a query but the reply does not arrive. When...

Nice work @ABeltramo ! Maybe is better to have a dedicated .env for AWS (or maybe AWS-nvidia, AWS-AMD, etc). This way these changes might be merged without affecting the defaults.

I approve

Basically you need thunderbolt-net: https://christian.kellner.me/2018/05/24/thunderbolt-networking-on-linux/ In my case I connect 3 Proxmox nodes where I run ceph (Kubernetes uses the traditional Ethernet network - 1 GB). Each of the 3...

I spent some days debugging a problem between RasberryMatic and Glusterfs that resulted in corrupted Homematic devices within rega (while HomeMatic IP worked). While this might be a quite specialized...

The option is `--enable-ino32` which is then used for the fuse program that the gluster client uses natively: `/usr/sbin/glusterfs --enable-ino32 --log-level=ERROR --log-file=/var/snap/microk8s/common/var/lib/kubelet/plugins/kubernetes.io/glusterfs/raspberrymatic-clusterfs/raspberrymatic-0-glusterfs.log --fuse-mountopts=auto_unmount --process-name fuse --volfile-server=192.168.2.86 --volfile-server=192.168.2.84 --volfile-server=192.168.2.86 --volfile-server=192.168.2.87 --volfile-id=ccu...