Recent content by frybin

I have a 1-node Proxmox environment running 8.2.4 and experiencing a weird issue where I have an EVPN SDN setup, and VM/Containers in that setup can reach out and connect to the host, but the host cannot connect back to the VMs. EX: From a VM, I can SSH into the host and connect properly, but...

It seems that the MTU was the issue. For the zone, I had the MTU set to 1450 but did not set my DHCP server to set the MTU on the VMs so they were defaulting to 1500, after setting the MTU to 1450 on the VMs, everything worked.

So, I have another issue now but I am not sure 100% if this is caused by the SDN. One thing that I am trying to do is set up an openshift cluster by following this guide. The strange behavior that I am experiencing is when I set up the httpd server, and a master or worker tries to request their...

Hi @spirit, First of all, thank you for all the help, I was able to install the 7.4 frr builds and the patched pve-network without an issue. Second, it seems that the patched pve-network seemed to work just fine. If I end up encountering any more issues I will be sure to post about them

So first of all, your spoiler ended up working for me which is really exciting. In addition, trying to install the older version of frr, I get the following issue: The following packages have unmet dependencies: frr : Depends: libjson-c3 (>= 0.11) but it is not installable Depends...

So that ssh command in the vrf context worked but how would I be able to do that by default because I want to use the DNS and OpenID server that exists in the SDN Subnets what that node is the exit node for. From my understanding, adding to /etc/network/interfaces won't work for the same exit...

I am able to sucessfully ping the VM ip from the exit node. Results of ip route root@pve3:~# ip route default via 10.10.0.254 dev vmbr0 proto kernel onlink 10.2.0.0/24 nhid 9 dev myvnet1 proto bgp metric 20 10.3.0.0/24 nhid 4 dev myvnet2 proto bgp metric 20 10.10.0.0/24 dev vmbr0 proto kernel...

Running that command did not allow the exit node to connect to the vm.

Hi @spirit, So applying the packages I now have internet connectivity as before I had updated the system so thank you for that asstiance. Though it seems like the original problem that I was having is still there. Here is a more concrete example of the problem below: I have my PVE node which is...

Hello, I am back at it again with another issue. Yesterday I was having an issue where my PVE was unable to access a OpenID inside one of it's SDNs, where I realized it could not ssh to hosts inside a SDN Network but they could ssh to it. (Seems like the PVE packets never reached the...

HI @spirit It ended up working, thanks for the help. I don't have other nodes added to this cluster since I am still testing new features out.

Running sysctl -w net.ipv4.conf.all.rp_filter=0 on the exit node did not work.

I don't use the proxmox firewall and have it turned off on the Datacenter and Node Level I think.

What I mean is I have a VM in a evpn zone with the IP range 10.2.0.0/24 and the gateway being 10.2.0.254. I have a pve node which is also the exit node for that zone. When I try to ping 10.10.0.3 from let's say a VM with the IP 10.2.0.1 it works. But, when I try to ssh or connect to 10.10.0.3...

Hello Again, I seem to have found another bug where VMs inside an SDN network is unable to connect to the exit node of that network, at least that's what it looks like with my 1 node setup. So I am able to ping the exit nodes from the VMs but if I try to access the WebUI or SSH into the PVE...