Recent posts

#1
General Discussion / Re: Has anyone heard of / trie...
Last post by opnsensehey - Today at 04:26:20 PM
I forgot to mention: I also find it sus, and please correct me if I'm wrong, that it isn't open source. Given that it's vibe coded, I assume it wouldn't be hard to have it be open source (you can ask Claude to do the needful and then build from there, even ask Claude for instructions on HOW to do this if you, the "dev," don't know how to do that already).

There is another one of these that recently came out (I assume also vibe coded, which I'm not against): https://github.com/a-d-m-x/admixcentral

This one is open source and the developer was more up front and honest when making their intro post about it.
#2
General Discussion / Re: Has anyone heard of / trie...
Last post by opnsensehey - Today at 04:23:51 PM
I dunno, maybe it's the pessimist in me, I find it highly sus that an account was created to ask this question, doesn't post or ask about anything else, and then at the same time, the developer of the project happened to find this post and also decided to create an account at the same time (instead of already having one) so they could reply here.

Again, maybe this is isn't sus and I'm being pessimistic but I can't be the only one who finds this reeking of astrturfing (and thus kinda makes me skeptical of the whole project).

That said, I'm planning to try it and hoping for the best. I was thinking of vibe coding something like this myself (as this apparently is) and hey, if someone beat me to it and it's not doing shady things in the background (backdoors, a chance to insert botnet stuff, etc.) then I'm all for it. We'll see what happens! Definitely only going to put this on my test lab for now.
#3
Yes there were some discussions about this so we tried to accomodate the sequence as best as possible, of course without any migrations happening.

Duplicate sequence is still fine too, the tie breaker is the UUID of the rule in that case (processing order).
#4
26.7, 26.10 Series / Re: Sequence Number Cloning Fi...
Last post by mooh - Today at 03:51:34 PM
Thanks for pointing that out. The instances with identical numbers I found had been created in the past. I only noticed it now because it only shows when the UI is in advanced mode that I had not used before.

Moving rules around is how I fixed it for me.
#5
German - Deutsch / Re: Heimnetzoptimierung
Last post by sternchen45 - Today at 01:43:31 PM
danke Euch. Konkret zur Umsetzung: wie reagiert denn die OPNsense bzgl. Regelwerk, Netzwerkadapterzuordnung sowie IP-Ranges, wenn ich an den Netzen arbeite, also neue Netze hinzufüge und die Zuordnungen von Adaptern ändere?

#6
26.7, 26.10 Series / Re: [CALL FOR TESTING] Defer P...
Last post by chucksense - Today at 12:38:17 PM
I have also been testing the patch since Nov 13th, everything works fine.

My ISP WAN connection is:
- VLAN with DHCP for VoIP
- VLAN with PPPoE for Internet

Testing both patches simultaneously with no issues.

Thanks!
#7
26.7, 26.10 Series / Re: [CALL FOR TESTING] DHCP re...
Last post by chucksense - Today at 12:37:59 PM
I have also been testing the patch since Nov 13th, everything works fine.

My ISP WAN connection is:
- VLAN with DHCP for VoIP
- VLAN with PPPoE for Internet

Testing both patches simultaneously with no issues.

Thanks!
#8
General Discussion / Improved WebUI login with user...
Last post by miketubby - Today at 11:31:10 AM
I have created a patch for the web UI login that improves the user experience when using username+password and 2FA tokens (TOTP).

The improvement does away with the requirment to manually enter the TOTP code before or after your password by accepting the username and password on the form and then replacing the password input field with "One-time token:" prompt in the same way that Keycloak does.

The change also allows your browser's password manager to remember the username and password fields, but always prompt for the 2FA token.

The change is restricted to authgui.inc where some additional code implements the third input field and hids/unhides it as necessary, captures the token and prepends or concatenates it as necessary before submitting it to the authentication backend.  No changes are needed the authentication backend/authentication factory are required.

Screen shots below.

Patch is for OPNsense 26.7.9_1 only and has been tested on two instances (my lab and production firewalls).

Full details and patch are located at https://forum.opnsense.org/index.php?topic=53355.0

Mike
#9
When running IDS/IPS (Suricata) with VLANs on OPNsense, it is best to configure it on the actual hardware interface name rather than the individual VLAN names, with Promiscuous mode enabled. Applying Suricata directly to the physical parent interface allows it to capture and inspect all tagged traffic across all underlying VLANs cleanly via netmap, preventing the routing, DHCP, or connectivity disruptions that frequently occur when binding to virtual sub-interfaces.   
#10
26.7, 26.10 Series / Re: Static-port outbound NAT d...
Last post by keeka - Today at 11:01:13 AM
In my home setup (my only experience of VOIP), each phone hardware (Cisco ATA192 and Gigaset N300) were at various times registered to a local asterisk server and directly to the SIP provider. After capturing all SIP/RTP traffic on the WAN and the local VOIP network for a few weeks, I eventually found a correlation. When the Gigaset N300 received an RTP psize change (from 20ms to 30ms I think it was), it stopped playing the incoming RTP stream. RTP packets were still arriving at the device (i.e. no router/firewall issue) but the device itself played no further audio. The Cisco ATA handled the same OK. I don't know which link in the chain changed psize, but it was north of my SIP provider. So the remote user's phone or their SIP provider network.
Re SIP registration interval and keepalive SIP options. I thought a port forward favourable to either extending udp session lifetime or increasing SIP chatter.
Trust me, the participants in the phone call would not have been silent for 60 seconds ;-)
I managed to find the notes I made at the time:
    • Initial Handshake: The N300-IP sends a SIP INVITE explicitly requesting a=ptime:20 and PCMA.
    • Initial RTP Stream: For the first 15 minutes, the incoming RTP stream is stable with a frame size of 214 bytes (consistent with 20ms G.711a).
    • The Trigger: At 15 minutes, the remote side sends an RTP packet with the Marker (M) bit set.
    • Simultaneously, the incoming RTP frame size jumps from 214 bytes to 374 bytes (indicating a switch to ~40ms packetization?). There is no SIP re-INVITE or UPDATE signaling this change.
    • Hardware Response: The N300-IP immediately logs the following hardware exceptions and drops the audio path:
    Except=0x2=S_EXCEPTCLASS_ERROR Place=0x51=S_EXCEPTPLACE_SC_LAN Code=0xD4=SLE_EXC_CODE_INT_RX_RT_LNG_ERR PrcNr=23 LinkAdr=0x0 File=sc/middleware/lan/sl_.exc
    • Status: RTP packets continue to arrive at the N300 at the new 374-byte size, and the N300 repeats the log for each RTP packet received from that point on.