Recent posts

#1
26.7 Series / Re: How to correctly display n...
Last post by Boxer - Today at 04:44:23 PM
Resize the widget, it should appear if you widen the widget
#2
26.7 Series / How to correctly display netwo...
Last post by lss4 - Today at 04:17:47 PM
After updating to OPNsense 26.7.2 I noticed the Interface section in the Dashboard no longer shows the interface's speed and duplex (e.g. 1000base-T <full-duplex>).

In fact, when I loaded the Dashboard page, the interface speed (and duplex) can be seen for a very brief moment then disappears.

Previously on 26.7.1_1 and before the interface speed is correctly displayed on the Dashboard. This is making diagnosing network speed issues harder, such as a cable being connected unreliably that it's only operating at 100base-T capping transmit speed at 10MB/s.

I wonder if this is a bug or an intended change. The Interface -> Overview section doesn't have a column for showing network speed and duplex, either.

EDIT: I just looked at the changelog of 26.7.2 and could not find anything explicitly related to the display of interface speed and duplex on the dashboard.
#3
26.7 Series / Re: SSH to opnsense fails afte...
Last post by revr3nd - Today at 04:15:26 PM
I do have a destination NAT rule that redirects SSH on the WAN interface to a git server (WAN TCP/22 to an internal server on port TCP/222). The looks here sounds like the SSH directly to the firewall (NOT on the WAN interface) is also getting wrapped up in this destination NAT rule.

I can confirm after disabling that NAT rule I am able to successfully SSH to the firewall.

So the issue here is that the NAT rules are matching and processing the SSH traffic meant for the firewall. It looks like the NAT rule is ignoring the interface the traffic is coming in on.

Breakdown of the rule:
-- Interface: ZN_WAN (group with WAN1 and WAN2 interfaces)
-- Version: IPv4+IPv6
-- Protocol: TCP
-- Destination Address: This firewall
-- Destination Port: TCP/22
-- Redirect Target IP: Git server
-- Redirect Target Port: 222

I'll continue to mess with the rule to make it more specific to only the WAN IPs, but this is a change is how the NAT rules are processed from 26.7.1
#4
26.7 Series / Re: Unbound stopps suddenly
Last post by MiRei - Today at 02:01:34 PM
a few minutes after reboot
#5
General Discussion / Re: PBR from self?
Last post by userfw - Today at 01:51:41 PM
I lost a good few hours chasing a weird issue with CARP advertisement packets that weren't going to the peer from the interfaces they were supposed to go, all thanks to an overly broad PBR firewall rule towards one of the WAN gateways, so I'd say yes, you can PBR self traffic.
#6
26.1, 26,4 Series / Re: Upgrade questions
Last post by Patrick M. Hausen - Today at 01:35:59 PM
Quote from: zuzuvela on Today at 01:13:12 PM1/ While back I upgrade from 25 -> 26. Now I see extra tab Firewall Rules [New]. Does this change my current configuration? Or I have to move the ' old ' ones to this? Or how does this work?

You are supposed to migrate your rules from the old to the new interface before upgrading to 26.7. So while on 26.1 use the migration assistant to do that. Instructions are on the migration assistant page in the UI.
#7
26.1, 26,4 Series / Upgrade questions
Last post by zuzuvela - Today at 01:13:12 PM
Hi,

Nice to be here. Few questions please.

1/ While back I upgrade from 25 -> 26. Now I see extra tab Firewall Rules [New]. Does this change my current configuration? Or I have to move the ' old ' ones to this? Or how does this work?

2/ Somehow my DNS blocklists etc. have been reset, is this expected?

3/ In Syslog output I see Suricata 9, deprecated. What does this mean for IDS/IPS?
#8
26.1, 26,4 Series / IPTV stopped working after upg...
Last post by ou1 - Today at 01:12:25 PM
As the title says, I upgraded OPNSense Business to 26.4.2 and my IPTV stopped working. I'm not sure if it's an issue with igmp-proxy or something completely unrelated.

The only message relating to igmpproxy in the logs is:
Warning igmpproxy select() failure; Errno(4): Interrupted system call

This message only started appearing after the upgrade.

Any help would be appreciated.
#9
26.7 Series / Re: Unbound stopps suddenly
Last post by DEC740airp414user - Today at 01:06:23 PM
so upon reboot.  no traffic is passing. or after a few minutes after the reboot?


I've been running 26.7 for 3-4 days now with no issues,  I figured id test for. you
I have a snapshot of business edition I went back to.  ran for a bit.  then restored back to a 26.7 snap shot.   I am not getting that error message.
I am using dns over tls to nextdns.  and the blocklists above with no tweaks to unbound.  more or less out of box
#10
26.7 Series / Re: Unbound stopps suddenly
Last post by MiRei - Today at 11:53:55 AM
EasyList
EasyPrivacy
Steven Black List
YoYo List

Unbound crashes only after reboot in 50%.
No more issues after restarting unbound.