UniFi-API-client VS kubernetes-pfsense-controller

UniFiClientAlerts is a Dockerized application that monitors UniFi networks for new device connections and sends alerts via Telegram. It leverages PHP code from the Art-of-WiFi/UniFi-API-client for interfacing with UniFi Controllers.

Take a look at the API Client here, https://github.com/Art-of-WiFi/UniFi-API-client. You can use the client to create a cron job or scheduled task to run a script to cycle the port.

I'm using a UDM SE (runs Unifi OS) and have cloud management up and running via a fixed external IP, and an external captive portal using port 443. SSL certificate installed and up to date. I'm trying to connect to using the API as 'documented' at https://ubntwiki.com/products/software/unifi-controller/api. I haven't been a dev for a long, long time, and although I think I could probably mug my way through using the stuff at https://github.com/Art-of-WiFi/UniFi-API-client, I'm first trying simply to connect to the API using curl. I'm falling at the first hurdle: I just can't connect to the API at all.

Personally, I have scraped together a custom portal before using the PHP API client - https://github.com/Art-of-WiFi/UniFi-API-client - UniFi passes the MAC address of the device as a GET parameter called 'id'

We try to avoid external classes and dependencies to reduce the potential for trouble. Especially with something rather simple like a REST API. But based on the UniFi API situation, we decided to make an exception and go with the fantastic UniFi-API-client class for PHP by Art-of-WiFi that can be found over on Github https://github.com/Art-of-WiFi/UniFi-API-client. It’s actively maintained and offers the benefit of people reporting broken stuff so it’s a community thing to make the UniFi API usable even if Ubiquiti decides to change or remove stuff.

There is a well-documented and maintained (though unofficial) PHP API for managing/talking to the controller. We use it for automating mundane tasks like loading lots of Mac-to-vlan bindings. It is quite feature complete. https://github.com/Art-of-WiFi/UniFi-API-client

PHP API library: https://github.com/Art-of-WiFi/UniFi-API-client

It's over-engineered, but I wanted to try running k8s in my homelab to continue learning about networking; deploying a blog seemed like a perfect test case. The cluster uses Traefik, https://github.com/travisghansen/kubernetes-pfsense-controll... to sync service definitions to HAProxy, and MetalLB. The k8s service IPs are routable from my local network, as well as the MetalLB IPs, and MetalLB handles syncing them to pfSense using BGP. pfSense sends DNS for any *.k8s.home.arpa to k8s, so I can resolve e.g. blog.default.svc.k8s.home.arpa on my local network.

One interesting hiccup: I had to introduce a NAT at pfSense because MacBooks don't listen to ICMP redirects, the packet would go laptop -> router -> k8s and then k8s -> laptop. Since the MacBook ignored the ICMP redirect, it drops the reply packet.