Recent posts

#1
Tutorials and FAQs / Re: OPNsense aarch64 firmware ...
Last post by rusli - Today at 06:04:51 PM
maurice, i am stuck at opensense 25.7.3 do you have the fingerprints for that which i could updates.
the opensense-update.walker.earth are total mess up right now not like the previously one that you posted.
could you fix the problems and provide us all the fingerprints at the opnsense-update.walker.earth website.
#2
26.1, 26,4 Series / Re: Source NAT vs Outbound ?
Last post by keeka - Today at 05:55:07 PM
@franco Sorry I was slow catching on. I attributed auto-generated rules not appearing as an artifact of having not used the migration tool. Instead I have a PPPoE WAN so am likely affected by #10479 as you have pointed out earlier.
#3
26.7 Release Candidate Series / Re: Services widget
Last post by julsssark - Today at 04:46:27 PM
All good. I still like it. My slightly OCD nature prefers consistency over precision/purpose.
#4
General Discussion / Re: How to set up Single NIC O...
Last post by nero355 - Today at 04:35:45 PM
Quote from: Vectralis on Today at 08:50:42 AMThanks, another question, how long do threads on this website stay open?

Is it for example possible to like test this after a month orso and then still answer on this thread?
Or do threads get closed after a certain amount of time inactivity?
Luckily this is not a Discourse based forum so no need to worry about that! ;)
#5
26.1, 26,4 Series / Re: How reliable is Firewall:D...
Last post by pfry - Today at 03:51:14 PM
Quote from: DaElephant on Today at 03:22:51 PM[...]The .5 address is matching on the firewall rule that has .50 in it, not .5.  The .5 IP should match a rule further down the rules list for that subnet.

I cleared the state table but the exact same issue came back.

It's possible you've encountered a bug (either in rule evaluation or state display), but chances are you've got a rule logic error. We'd need to see the relevant information (rules, aliases, state display, etc.) to be sure. Putting the data together might reveal the issue (or not).

Quote[...]Another odd thing in Firewall:Dianostics:Aliases it is listing Aliases that no longer exist.  They did exist at one point but have been deleted or renamed, but still show.

I'd assume that's because pfctl will show the (now-) empty tables, but I'd have to test it to be sure.
#6
Show the rules, please. Educated guess: you have the netmasks/prefix-lengths wrong so the rule matches more than intended. To match a single IP address use /32.
#7
Hi, thanks again for publishing your plugin and sharing your work.

I forked your repository and used it as a starting point for my environment. 
I've rewritten a large part of it since then, but your project was the base that made this possible, so I want to explicitly acknowledge that.

I'm using it on OCN Fixed IP (IPoE) and it's working well here. 
Really appreciate you open-sourcing this and sharing the initial implementation.
#8
26.1, 26,4 Series / How reliable is Firewall:Diano...
Last post by DaElephant - Today at 03:22:51 PM
I ask this question because I am seeing odd behaviour there.

I have 2 IP addresses in the same subnet, .5 and .50
The .5 address is matching on the firewall rule that has .50 in it, not .5.  The .5 IP should match a rule further down the rules list for that subnet.

I cleared the state table but the exact same issue came back.


Side note
Another odd thing in Firewall:Dianostics:Aliases it is listing Aliases that no longer exist.  They did exist at one point but have been deleted or renamed, but still show.
#9
Yay, thanks and likewise!  :)
#10
Most threads are never closed. Occasionally a mod might close one because the discussion got a bit too heated. But in general or via timeout - no.