Messages

Since doing a fresh install of 22.1 on the weekend, I've experienced a few freezes, in that I can't access any external sites over http/https. The OPNSense dashboard is still working and I can see the firewall log refreshing as per normal but no routing appears to be happening.  Rebooting solves the issue.

I just wanted to know what to look for and where in the various logs that would indicate why and if is there is a way of fixing the issue without needing to reboot.
Thanks

Is there a downloadable ISO for 22.1 b1?

Indeed. I'm happy to wait.

I know. Just wanting to set up my new Intel NUC with the dual I225's

Is the first beta here - https://pkg.opnsense.org/FreeBSD:13:amd64/22.1/sets/     base-22.1.b1-amd64.txz ?

Upgrade path is not available yet, only fresh install and restore

Which file is the installable beta?
Thanks

Thanks. When will be the first beta for 22.1 available to try?

Alan

Will the first beta of 22.1 have support for the Intel I225-LM controllers?  I have an 11th Gen Intel NUC with dual 2.5Gbe and waiting to use it with opnsense.

The last log entry was last night, my time, about 8 hours ago. But the reosolv.conf messages were still created all through this time in the system log.

I'm not sure how to check if unbound is restarting every 5 minutes.
Thanks

Yes, but no change. Messages are still appearing every 5 minutes to the second. I called my service provider and they're not forcing any lease renewals either.

Thanks for this info. I disabled "Allow DNS server list to be overridden by DHCP/PPP on WAN", which I assume is what you refer to, but I still see the same messages every 5 minutes

Hi,
I'm seeing entries like this "dhclient: Creating resolv.conf" written to general system log exactly every 5 minutes and wanted to know what could cause this. The content of the /etc/resolv.conf includes the 2 ip addresses of my ISP's dns's along with:
domain localdomain
nameserver 127.0.0.1

I've searched for this elsewhere but couldn't find any definitive answers.
Is there some setting I can tweak to increase the time? Could it be my ISP expiring the lease every 5 minutes ?
Any help would be appreciated. I'm running 20.1.4
Thanks
Alan

This is resolved now. It appears that the port IDs of the NICs on the Fitlet2 were swapping for some reason after initial assignment. So what I thought was the LAN interface was in fact a port with no cable attached. I used auto configure for WAN and LAN and they took. All working nicely now.

Hi,
(I had this incorrectly posted in the 20.1 Production forum so I apologize for the duplication.)

I've installed OPNSense 20.1 onto a new Fitlet2 but can't get past an issue with the LAN interface.  I was able to get an IP address on the WAN port from my ISP without any problems and I set the static address 192.168.1.1/24 on the LAN port. I'm able to ping 192.68.1.1 in the OPNSense shell as well as curl from the shell to http://192.168.1.1 to see the login page content of the web ui.  But I can't ping 192.168.1.1 from my pc attached to the LAN port directly nor via a switch, or see the web UI login page via http.  I tried setting a static address on my pc and also tried to get an address via dhcp but it won't connect. Note the exact same thing happens with pfSense as well.

I'm out of ideas and would appreciate any help. I can see others on the forum running ok with a Fitlet2. Are there any firewall settings I need to change first, that can be done from the command line?  Perhaps I've overlooked something simple.
Thanks
Alan