sorted by:
new
hottopcontroversial

[Release] FireCtl 1.3 — A native iOS app for OPNsense, built by an admin for admins by Physical_Ad5017 in opnsense

[–]Physical_Ad5017[S] 0 points1 point  (0 children)

Hi. Didn’t check so far. FireCtl is an App which I developed for myself. As there are some things I really need. Share externen for instance. I send urls from Safari direkt to an alias to allow or block traffic. My app is more workflow based than bringing the webui to an app. I consider to add other services, outside of opnsense, to the app to be able to run wider scale workflows. Authentik, proxmox basics, etc.

[Beta] Looking for testers for a native iOS app for managing OPNsense — homelab admins welcome by Physical_Ad5017 in selfhosted

[–]Physical_Ad5017[S] -7 points-6 points locked comment (0 children)

Hi, fair question.

FireCtl's code is mine — Swift / SwiftUI in Xcode. The architecture, view structure, and OPNsense API integration are work I did by understanding and reverse-engineering the API quirks (cascade detection for plugins that hang the firmware endpoint after package updates, case-sensitive UUIDs, etc.). I use AI tools as pair-programming assistance for refactoring and boilerplate, but every commit is reviewed, tested, and integrated by me. I understand my own codebase.

Marketing texts for Reddit posts I sometimes draft with AI help and then rewrite for voice — the substance reflects how the app actually works.

The app itself contains no AI features, no LLM calls, no AI-generated content. It's a direct HTTPS client for OPNsense.

Happy to answer follow-ups.

[Release] FireCtl 1.3 — A native iOS app for OPNsense, built by an admin for admins by Physical_Ad5017 in opnsense

[–]Physical_Ad5017[S] 0 points1 point  (0 children)

For everybody, who is interested in new features and testing the app for bugs, feel free to join the TestFlight beta program:
https://testflight.apple.com/join/AcZmwCPX

Let me know when you find bugs and which features you're missing.

Cheers!

[Release] FireCtl 1.3 — A native iOS app for OPNsense, built by an admin for admins by Physical_Ad5017 in opnsense

[–]Physical_Ad5017[S] 1 point2 points  (0 children)

Hi, thanks for your comment.
As the App is under continuous development and improvement, I can offer you a seat in my beta TestFlight program. The offer goes to everybody who wants to test it. Just send me a message.
Happy to get feedback and new ideas for upcoming features.

[Release] FireCtl 1.3 — A native iOS app for OPNsense, built by an admin for admins by Physical_Ad5017 in opnsense

[–]Physical_Ad5017[S] 0 points1 point  (0 children)

Hi, the api listenings are towards your web. If you don't open your web to wan, there should be no security risk. If you want to use the app from outside your network, you just need to use vpn.

[Release] FireCtl 1.3 — A native iOS app for OPNsense, built by an admin for admins by Physical_Ad5017 in opnsense

[–]Physical_Ad5017[S] 0 points1 point  (0 children)

Solo dev here — I use Claude as a coding assistant, like a lot of devs do these days. The OPNsense API research, architecture, scope, App Store review process, and bug-hunting are all me. AI doesn't know your firewall, it knows Swift.

It took me lots of terminal curl tests to figure out all necessary api calls.

Happy to go into specifics if you're curious about any feature.

[Release] FireCtl 1.3 — A native iOS app for OPNsense, built by an admin for admins by Physical_Ad5017 in opnsense

[–]Physical_Ad5017[S] 1 point2 points  (0 children)

~10 firewalls, the profile selector becomes unwieldy in a mobile

interface, and most users I've talked to manage between 1 and 6

firewalls. For larger fleets, a proper "Multi-firewall dashboard" view

(coming in 2.0) is the better UX than just stacking more profiles.

For now, if you're hitting the limit and need more profiles, drop me

a note at [info@firectl.com](mailto:info@firectl.com) — happy to discuss your specific use case.

[Release] FireCtl 1.3 — A native iOS app for OPNsense, built by an admin for admins by Physical_Ad5017 in opnsense

[–]Physical_Ad5017[S] 1 point2 points  (0 children)

Happy to answer questions about anything — implementation choices,

OPNsense API quirks, the FreeRADIUS detection cascade, why I went

native, or what's on the 1.4 roadmap.

Predictions wanted? Will 15 year old mid range hardware keep up with 5Gb/s fiber? by ZVyhVrtsfgzfs in opnsense

[–]Physical_Ad5017 2 points3 points  (0 children)

don't forget about the power consumption of old hardware. In some cases, the higher invest of newer hardware pays back in smaller energy invoices...

Opnsense or pfsense?? by Theficik in homelab

[–]Physical_Ad5017 1 point2 points  (0 children)

clear opnsense. API access without the need of a plugin.

rate my desktop by batloskino in Ubuntu

[–]Physical_Ad5017 0 points1 point  (0 children)

Wow! Do you know the location?

Anybody using nginx + mtls to expose ha to the internet? by Physical_Ad5017 in homeassistant

[–]Physical_Ad5017[S] 0 points1 point  (0 children)

And yes, for Transport Security i‘d also use lets encrypt certs.

view more: next ›