Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - HappyDoer

#1
Development and Code Review / MCP Server
November 03, 2026, 12:39:39 AM
Has there been any consideration of an official MCP (Model Context Protocol) server for OPNsense? MCP is the open standard AI assistants (Claude, ChatGPT, Copilot, local LLMs etc.) use to talk to external tools, and since OPNsense already has a comprehensive REST API it seems a natural fit.

This could be either a first-class project or a vetted community project linked from the documentation's "Community Plugins > Other" list.

From a quick review, these are the most developed projects at the moment:


An official server would help me with:

  • Security and trust - a firewall is the last place you want an unvetted tool holding admin credentials. An official server could use the API only, with least-privilege API users and a clear read-only mode, rather than relying on SSH or shell access.
  • Keeping up with releases - community servers fall behind as the API changes between releases. If one was maintained alongside OPNsense, it would track those changes.
  • Troubleshooting and auditing - asking "why can't VLAN 20 reach the NAS?" or "which rules are unused or overlapping?" and getting an answer based on the live config, logs and states.
  • Safer changes - describing a change in plain language, then reviewing the exact rules, aliases or NAT entries proposed before they are applied.

A quick GitHub search already turns up 42 OPNsense MCP server projects, so there's clearly demand. Unfortunately, effort is spread across many partial implementations rather than one complete, up-to-date server. Would the team consider either building one or working with an external maintainer to list a recommended community option in the docs?
#2
Quote from: doktornotor on September 02, 2024, 04:57:08 AM
Has no influence on disconnects probably. Different APNs may have different results, some being IPv4 only, some have public IPs while some stick you behind CGNAT. IPv6 may require a special APN and can influence IPv4 as well. You need to check with VF.

Definitely have the correct APN. Just happened to me again, understand I need to be watching /var/log/ppps/latest.log. When it stops responding:


<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="1"] [opt1_link0] MODEM: can't ioctl(TIOCMGET) /dev/cuaU0.2: Device not confi
gured
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="1"] [opt1_link0] MODEM: can't ioctl(TIOCMGET) /dev/cuaU0.2: Device not confi
gured
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="2"] [opt1_link0] Link: DOWN event
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="3"] [opt1_link0] LCP: Down event
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="4"] [opt1_link0] LCP: state change Opened --> Starting
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="5"] [opt1_link0] Link: Leave bundle "opt1"
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="6"] [opt1] Bundle: Status update: up 0 links, total bandwidth 9600 bps
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="7"] [opt1] IPCP: Close event
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="8"] [opt1] IPCP: state change Opened --> Closing
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="9"] [opt1] IPCP: SendTerminateReq #4
<30>1 2024-09-02T05:55:32+00:00 hostname ppp 62108 - [meta sequenceId="10"] [opt1] IPCP: LayerDown
<13>1 2024-09-02T05:55:32+00:00 hostname ppp 31425 - [meta sequenceId="11"] ppp-linkdown: executing on ppp0 for inet
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="12"] [opt1] IFACE: Down event
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="13"] [opt1] IFACE: Rename interface ppp0 to ppp0
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="14"] [opt1] IPV6CP: Close event
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="15"] [opt1] IPV6CP: state change Stopped --> Closed
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="16"] [opt1] IPCP: Down event
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="17"] [opt1] IPCP: LayerFinish
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="18"] [opt1] Bundle: No NCPs left. Closing links...
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="19"] [opt1] IPCP: state change Closing --> Initial
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="20"] [opt1] IPV6CP: Down event
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="21"] [opt1] IPV6CP: state change Closed --> Initial
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="22"] [opt1_link0] LCP: LayerDown
<30>1 2024-09-02T05:55:33+00:00 hostname ppp 62108 - [meta sequenceId="23"] [opt1_link0] Link: reconnection attempt 1 in 2 seconds


Then  connection failure attempts repeated indefinitely:


<30>1 2024-09-02T07:36:30+00:00 hostname ppp 88658 - [meta sequenceId="8560"] [opt1_link0] MODEM: chat script failed
<30>1 2024-09-02T07:36:30+00:00 hostname ppp 88658 - [meta sequenceId="8561"] [opt1_link0] Link: DOWN event
<30>1 2024-09-02T07:36:30+00:00 hostname ppp 88658 - [meta sequenceId="8562"] [opt1_link0] LCP: Down event
<30>1 2024-09-02T07:36:30+00:00 hostname ppp 88658 - [meta sequenceId="8563"] [opt1_link0] Link: reconnection attempt 2 in 4 seconds
<30>1 2024-09-02T07:36:34+00:00 hostname ppp 88658 - [meta sequenceId="8564"] [opt1_link0] Link: reconnection attempt 2
<30>1 2024-09-02T07:36:35+00:00 hostname ppp 88658 - [meta sequenceId="8565"] [opt1_link0] CHAT: The modem is not responding to "AT" at MomCmd: labeell.


Once again, after a reboot it comes up fine:


<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="1"] Multi-link PPP daemon for FreeBSD
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="2"]
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="3"] process 6350 started, version 5.9
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="4"] web: web is not running
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="5"] [opt1] Bundle: Interface ng0 created
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="6"] [opt1_link0] Link: OPEN event
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="7"] [opt1_link0] LCP: Open event
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="8"] [opt1_link0] LCP: state change Initial --> Starting
<30>1 2024-09-02T07:38:08+00:00 hostname ppp 6350 - [meta sequenceId="9"] [opt1_link0] LCP: LayerStart
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="10"] [opt1_link0] CHAT: +CGDCONT=1,"IP","live.vodafone.com"
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="11"] [opt1_link0] CHAT: Detected Custom modem.
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="12"] [opt1_link0] CHAT: Dialing server at *99#...
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="13"] [opt1_link0] CHAT: ATDT*99#
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="14"] [opt1_link0] CHAT: Connected at 100000000.
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="15"] [opt1_link0] MODEM: chat script succeeded
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="16"] [opt1_link0] Link: UP event
<30>1 2024-09-02T07:38:09+00:00 hostname ppp 6350 - [meta sequenceId="17"] [opt1_link0] LCP: Up event
...


Wish I knew how to reinitialize the device like happens at boot so that it could be brought up again. I see plenty of similar issues being discussed with freebsd generally though so understand this is likely nothing directly related to opnsense.
#3
Quote from: doktornotor on September 02, 2024, 04:02:05 AM
Maybe the USB device just disconnects? Run usbconfig and check the system logs?

Thanks, and that was information I should have included sorry - I have tried disconnecting the device and connecting it again after it loses IP assignment. usbconfig output for the device while it is up now looks like this:


ugen0.2: <Sierra Wireless, Incorporated AirCard 320U> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)


I'll compare after it goes down again. I've never seen anything relevant in the system logs each time I've checked unfortunately. Is there anywhere better than the "general" log files view to narrow logs to a specific interface?

Quote from: doktornotor on September 02, 2024, 04:02:05 AM
Maybe just set it to "None" then.

Yes, I could set it to none, though I mentioned it more because ideally ipv6 would work too but I have no idea where to start troubleshooting that either.

Quote from: doktornotor on September 02, 2024, 04:02:05 AM
This randomly found howto for some random VF gear suggests the APN should be vfinternet.au (Step 15).

I believe I tried the various APNs including vfinternet.au and came to the conclusion the one I'm using was correct; it may have even been the only that worked. I could test again, but the fact the connection is stable for days after boot makes me think it's unlikely to have any impact.
#4
I've had this issue for as long as I can remember running opnsense (quite a few years now) and an outage this morning has meant I'm finally writing this post. I have a backup usb 4g modem (Sierra Wireless AirCard 320U) on Vodafone here in AU and connected to a PC Engines APU 2 running OPNsense 24.7.3_1-amd64.

Immediately after reboot the interface will come up and will be functional for what seems to be a random amount of time, usually a number of a days. It will then go down (i.e. the interface no longer has an address) and I haven't figured out a way to bring it back up short of rebooting, which works.

I've tried disabling the interface and enabling again, as well as saving the PPP settings again. Can anyone suggest how I can manually or automatically bring it back up, or get to the bottom of why it goes down in the first place? Not many settings involved, I believe it's only the following modified from defaults:


Interfaces: [PPP0]
Identifier: opt1
Device: ppp0
IPv4 Configuration Type: PPP
IPv6 Configuration Type: DHCPv6

PPP configuration
Modem Port: /dev/cuaU0.2
Phone Number: *99#
Access Point Name (APN): live.vodafone.com


I've also never had IPv6 get an address assigned either, though I don't think that's related. Appreciate any pointers.