Recent content by bodleytunes

I can see vyos is learning the networks with BGP to go next hop via the 3 proxmox nodes so routing should work, in fact it is in one direction, inbound to the vm's the traffic gets through to the vm on the vnet, its just when the vm reples the packet gets dropped on the return path on the...

Yeah just tried again, the vm can be on any host and as long as only one exit node is selected in zone setup, it will ping out to the network. This can be a remote node to the one that the VM is residing on. However if you select more than one exit node, the ping stops workinging, seems the...

BTW I can see when pinging from outside LAN to a vnet the traffic comes into the vnet, the vm on the vnet replies but the reply never leaves the host, its like it gets dropped/blackholed. It does sound a bit like something that would happen when reverse path verification is enabled and its...

SDN Generated FRR config Building configuration... Current configuration: ! frr version 8.5.1 frr defaults datacenter hostname supa1 log syslog informational no ipv6 forwarding service integrated-vtysh-config ! vrf vrf_zone0 vni 10000 exit-vrf ! router bgp 65010 bgp router-id 10.12.89.10 no...

Main LAN facing bridge auto vmbr0 iface vmbr0 bridge-ports vni7 eno1 bridge-vids 1,7 bridge-vlan-aware yes address 10.12.89.10/24 gateway 10.12.89.1 # mtu 9000

# # /etc/sysctl.conf - Configuration file for setting system variables # See /etc/sysctl.d/ for additional system variables. # See sysctl.conf (5) for information. # #kernel.domainname = example.com # Uncomment the following to stop low-level messages on console #kernel.printk = 3 4 1 3...

I'll check again but pretty sure I set those RP sysctl params early on.

I'm also having some problems with the exit nodes, think I can only get it to work with one exit node? I'm using BGP peering from upstream VyOS router, using ebgp multipath and equal cost for the learned vnets via each proxmox node. (multipath relax) I'm not using any nat, fully routed...

Oh yeah thanks, its working now! Can't belive I missed that. :D :cool:

root@supa1:~# pveversion -v proxmox-ve: 7.4-1 (running kernel: 5.15.108-1-pve) pve-manager: 7.4-15 (running version: 7.4-15/a5d2a31e) pve-kernel-5.15: 7.4-4 pve-kernel-5.13: 7.1-9 pve-kernel-5.15.108-1-pve: 5.15.108-1 pve-kernel-5.15.107-2-pve: 5.15.107-2 pve-kernel-5.15.107-1-pve: 5.15.107-1...

I have the same issue on one of my clusters!! However I've upgraded another 2 single hosts fine? One running ceph the other not. I don't know whats up becasue the sources files look okay? root@supa1:~# cat /etc/apt/sources.list deb https://ftp.debian.org/debian bookworm main contrib deb...

Reboot sorted it! root@Debian-85-jessie-64-minimal:~# modprobe ifb root@Debian-85-jessie-64-minimal:~# ifconfig ifb0 ifb0 Link encap:Ethernet HWaddr 2e:0c:57:39:f2:37 BROADCAST NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0...

Worth a punt to reboot as I did do a dist-upgrade the other day, can't remember about rebooting actually! Cheers, Jon. root@Debian-85-jessie-64-minimal:~# modinfo ifb filename: /lib/modules/4.4.35-1-pve/kernel/drivers/net/ifb.ko alias: rtnl-link-ifb author: Jamal Hadi...

Hi, I tried that but it doesn't work :( root@Debian-85-jessie-64-minimal:~# modprobe ifb modprobe: ERROR: could not insert 'ifb': Exec format error This is a proxmox build at Hetzner.... Could it be they have fudged about with the kernel? Cheers! Jon.

Ok thanks for that! Will try tonight ... it's running on the host itself. Cheers! Jon.