Update, I Was never able to get this working properly, but Now that the 2.7.0 update has been released, once I updated, everything is working as expected. not sure if it was some sort of Hyper-V Driver issue, or some other bug that was fixed in this release.... just glad I can utilize my secondary internet connection better now. thanks for all the help!

@benjaminbeckcsl said in PfSense Hetzner Dedicated Proxmox:

Nun habe ich eine dritte IP. welche die 66.77.88.3 ist. Wie bekomme ich die da auch noch drauf? Dadurch dass das GW von Hetzner bsp. 66.77.88.14 ist kann ich kein 32er Netz nehmen.

Was hat da genau das Gateway mit zu tun? So wie du das zeigst sind alle 3 IPs aus dem gleichen Netz? Dann haben die doch keine unterschiedlichen Gateways?

Ansonsten was @viragomann sagt, wenn die alle aus dem gleichen Subnetz sind, dann wird die Subnetzmaske des Netzes genommen, nicht /32. Ansonsten IP Alias und let's go. :)

It can depend on the switch/router on the other end of the cable. For instance with Comcast routers often when replacing a router in an office (inside the Comcast router) I've found it's fastest to power off or reboot the Comcast router so it learns the IP has a new MAC. If you have the second router on, and are just plugging in cables, I would wonder if restarting the second router (or just leaving it off and powering it on) would help.

But overall CARP set up properly works basically instantly so that would be preferred. https://docs.netgate.com/pfsense/en/latest/book/highavailability/index.html

With IPAliases you can usually use either /32 or the correct subnet size. The important thing is you have at least one IP defined on the interface with the correct subnet in order to add the correct routing.

https://docs.netgate.com/pfsense/en/latest/firewall/virtual-ip-address-feature-comparison.html#ip-alias

Steve

P.S. I take it back - you may need firewall rules for IPSec to allow BGP traffic. You can create them from the firewall logs if you see blocked BGP traffic on IPSec.