Messages

Hi,
I can report that for me the problem has been resolved in the 19.7.2 update and the DHCP Relay is now starting and working as expected without any configuration change.
Regards,
Neal

Yes that is true for us - the IP of the DHCP server for the relay is on a routed subnet, not a subnet that is directly connected to the OPNsense device. So it seems something changed in 19.7 because it definitely was working for us for a long time.

Hi,
After upgrade to 19.7 the DHCPv4 Relay service won't start. The same configuration was working in previous versions for the last 18months at least.
The messages in the log...
"dhcrelay: Can't attach interface lan to bpf device /dev/bpf0: Device not configured"
and...
"opnsense: /status_services.php: The command '/usr/local/sbin/dhcrelay -i em2 -i lan XX.XX.XXX.X' returned exit code '1', the output was 'Requesting: em2 as upstream: Y downstream: Y Requesting: lan as upstream: Y downstream: Y "
with IP address masked.
Regards,
Neal

Hi Franco,
It turns out you are right - I cleared the History in the browser and it now works as expected.
Thanks for the reply.
Regards,
Neal

Hi,
I have an LDAP server set up for user authentication which works. It has been there through several upgrades. When I went to click the import button to add a new user it does not work in 18.7.8. The page just refreshes and goes back to the existing user list.
Neal

Hi,
See below the responses from the old system and then the new...

sysDescr.0 = STRING: OPNsense hostname 18.1.13-a2cd7c69f OPNsense FreeBSD 11.1-RELEASE-p11 amd64

sysDescr.0 = STRING: FreeBSD hostname 11.1-RELEASE-p11 FreeBSD 11.1-RELEASE-p11  21b4c8ea1d5(stable/18.7) amd64

The OID is .1.3.6.1.2.1.1.1.0 I believe.
Regards,
Neal

Hi,
This is not super urgent, but a nice to have fixed. We upgraded the snmp plugin to the net-snmp version as the bsnmp plugin is deprecated. We did also switch to using snmp V3 from snmp V2.
I notice the system is now being described as FreeBSD as opposed to OPNsense which means our monitoring systems (Observium and LIbreNMS) now identify them as servers (FreeBSD) by default as opposed to firewalls.
Is this expected behavior or something wrong with our systems?
Regards,
Neal

Just in case it helps;
I saw this too. We don't use IPv6 so I disabled IPv6 in the firewall settings and the problem went away, and allows us to still block IPv4 Bogons.

Wow, I come back from the weekend and it is sorted! One of the benefits of living in a timezone ahead of most of the world :-)

I have just tested it is working for me so thanks for the very quick fix.

Regards,
Neal

Hi,
I can create an internal certificate in 17.7.8 but after upgrade to 17.7.9 when I go to create an internal certificate by pressing save it just presents a blank page and the cert isn't created.
Regards,
Neal