Recent posts

#1
Quote from: Q-Feeds on <strong>Today</strong> at 08:55:18 PMThat is indeed the intended use of the feature. It will then send you an alert whenever any product name contains "ruckus unleashed".
Thanks so much for the quick response, much appreciated.

It seems that the current search works like a phrase search. E.g. the search term "Ruckus Unleashed" does not find "Brocade Communications Systems, Inc.Ruckus Networks Unleashed APs and Zone Director". (I found that one just by searching for "unleashed".) It would be great, if in the future you could also provide "all words" match, so a term like the latter could also be found, so word order or additional words in-between don't matter.
#2
General Discussion / Re: Two WAN trouble
Last post by viragomann - Today at 09:14:56 PM
Quote from: nwabytes on October 29, 2026, 11:08:08 PMMain ip 170.10.188.14/30 the gateway is in the DC for this one 170.10.188.13. now my server network 167.224.195.232/29.
Do you want to run the /29 inside your LAN on a different network port or add it to the WAN port?
#3
26.7, 26.10 Series / Re: if_bridge looses ARP packe...
Last post by pfry - Today at 08:59:06 PM
That's a strange issue. I'd've thought the MAC would always pad short packets, as 64B has been the standard for... 50 years? Looking at it initially, I thought it might be a carrier extension issue, but apparently not.

I haven't noticed ARP issues (other than proxy issues, which do not result from lost requests). I do not currently have any Broadcom devices in use - just Intel and Realtek at the moment. I imagine the particular switch might be an issue as well.
#4
That is indeed the intended use of the feature. It will then send you an alert whenever any product name contains "ruckus unleashed".
#5
Just for the record: bnxt(4) is Broadcom, not Intel.
#6
I am a Q-Feeds plus subscriber and am currently looking at the new CVE monitoring feature for paid subscribers.

I checked for two products: OPNsense (of course!) and "Ruckus Unleashed", which is the "Unleashed" firmware for my Ruckus Wireless APs:




It seems like the product identification isn't curated and there are lots of variations for a single product name. (Understandably so BTW, I'm not complaining that it isn't curated.)

But given this state of affairs, would it be best just to select the "Watch everything matching ..." option, so I am sure to catch future variations of product names?
#7
26.7, 26.10 Series / Re: Messages in firewall log w...
Last post by pfry - Today at 08:34:19 PM
Quote from: abulafia on <strong>Today</strong> at 08:23:44 PM[...]In my case, they are UDPv4 packets incoming on WAN and have "dstport 0" (which might explain why they are blocked).

In that case the "block all targeting port 0" automatic rules should be listed (unless disabled). Most unlabeled "block" logs are from the scrub (normalization, which may also be disabled) - in other words, the packet had some other issue, and the scrub precedes other rules. I don't know about unlabeled "pass" logs as above - that's a new one to me.
#8
26.7, 26.10 Series / Re: Messages in firewall log w...
Last post by striker2150 - Today at 08:33:17 PM
Have you tried pfctl -s rules on the shell?

For debugging I usually prefer looking at the rules with pfctl as it shows the raw pf configuration without any web interface obscuring what is actually going on.
#9
26.7, 26.10 Series / Support for VLAN aware bridge ...
Last post by striker2150 - Today at 08:29:20 PM
Hi,

FreeBSD 15.1 introduced a VLAN aware bridge device.
This enables one to use one bridge device for multiple VLANs and therefore reduces the complexity of the network configuration.
With the old bridge device there was the need to have a separate bridge for each VLAN.

Question, does OPNsense already support the usage of the VLAN aware bridges?
If yes, how can I enable it in the web interface?
If no, are there any plans to support it in a future release?
#10
26.7, 26.10 Series / Re: Messages in firewall log w...
Last post by abulafia - Today at 08:23:44 PM
I also see "block" logs without label/rid.


In my case, they are UDPv4 packets incoming on WAN and have "dstport 0" (which might explain why they are blocked).

Here a screenshot filtered for "dstprt is 0":