Messages

Same issue here. Log file looks indentical.

I think you need to create AWS AMI. Hashicorp's Packer is a popular option. I found an old Github repository that seems to be a good starting point: https://github.com/remlabm/opnsense-packer

I'm using Calico for CNI.

Hi all,

Here's how I got Metallb working with OpnSense. I'm running a home lab with Kubernetes 1.19 on a single Ubuntu node based on Intel NUC hardware. OpnSense 20.1 is running on fitlet2. I have separate VLAN for Metallb but I think the process is similar if you want to use LAN ip range.

The Metallb side of things is pretty much "standard" and similar to what thoth is using so I won't dive into that in much detail. On OpnSense I'm running the frr-plugin to enable BGP.

Steps to enable BGP based routing between Metallb and OpnSense:

0. Have Metallb running with desired configuration
1. Install ffr-plugin on OpnSense
2. Enable both Routing and BGPv4 from OpnSense admin gui
3. Configure BGPv4 as follows (edit AS number as needed):



4. Add Neighbor to BGPv4 as follows (edit host ip and AS number as needed):



After setup the Routing -> Diagnostics -> BGPv4 page should be populated with the routed ip:s from Metallb which is a good sign that everything is working as expected.

I also tried Metallb with Layer2 but it wasn't reliable enough for me. The BGP approach works much better.