Messages

I'm going to see if I can get docker working under FreeBSD. Then I can use the docker image for the Ubiquiti Controller directly. The Watchtower docker image solves the problem of keeping up with Ubiquiti releases automatically.

If it all works as advertised, that would be a more general solution and solve the 'frequent releases' problem. docker has worked well for me under Linux, no idea if it works as well under FreeBSD, though.

Perhaps my request should be for docker as a plugin ;)

Does anyone have experience running docker under FreeBSD/OPNsense?

I'm not expecting docker & OPNsense to integrate, I'm just looking for advice about any conflicts or gotchas that others have run into.

I'm thinking that might be a better way to go for installing Ubiquiti Controller, rather than a one-off manual install.

Thanks,

- Paul

While I sympathize, I think that makes the case stronger that it's maintained automatically, doesn't it?

Better that it's handled in one place, and everyone is running the same version installed in the same way, than everyone does it themselves in their own way, so there are multiple versions in the field, each installed in a slightly different way. If folks are installing it manually, then a release candidate can't be tested against all the possible versions and ways it could have been installed.

Besides, doing it manually requires considerably more understanding of FreeBSD than installing an OPNsense plugin does.

Just did a quick search, and https://uptimerobot.com/ looks like it could be one option. The free tier allows you to do various types of tests (more than just ping) and will monitor up to fifty IPs, every five minutes, with email notifications for free. More frequent checks, with SMS and/or voice calls on upgraded plans ($4.50/mo and up).

- Paul

p.s. I don't use them myself, can't endorse (or otherwise) their services.

I'd suggest you try DNS-O-Matic, which is a dynamic DNS aggregator, and set it up with your current dynamic DNS service provider, plus DSLReports line monitoring service. Not quite what you asked for, but may suit your need.

Another possibility is to use an IP monitoring service, provided it could be configured to check for something more specific than 'responds to pings' (because if your current IP is reassigned to someone else, their gear may still respond to the pings). A quick google search will turn up plenty of services that will monitor an IP address, some of which are free for basic service.

At least for me, knowing that using my dynamic DNS name still reaches my gear is the most important thing. If not, I want to know. If everything is working correctly, I don't really need to know my IP address changed.

- Paul

I'd love to see an easy method to set up the Ubiquiti Controller software on the same host running OPNsense. Given that FreeBSD is lagging on the native wireless card support, an external access point seems like the logical solution.

Ubiquiti makes access points in the same class as OPNsense (in my opinion), and I assume that at least some OPNsense users have paired the two.

It seems logical to me to have my OPNsense box also run the Ubiquiti Controller software. However, while I'm comfortable with Linux, I'm a newbie with FreeBSD.

Upgraded to 17.7.12_1, then 18.1, through the web interface. Everything seems to be working just fine for me.

- Paul

I realize that OPNsense can't do anything until stable FreeBSD drivers are available, but once they are, does the OPNsense project regard it as a priority to implement 802.11ac support once FreeBSD enables it?

- Paul

I would also love to to be able to set up OpenConnect client VPN from the web UI, too.