Topics

1

16.1 Legacy Series / [SOLVED] pppoe + unbound

« on: April 04, 2016, 11:05:36 am »

I have recently switched internet providers, and have implemented pppoe on OPNsense.  With the internet provider supplied router in bridge mode, once every day or so a new IP address is issued to OPNsense, which creates a new route entry, which causes Unbound to stop working.

Once a day, when the DNS stops resolving, I simply login to OPNsense and restart Unbound, which restores proper operation, but I am wondering if there is some automated way to handle this situation so that no manual intervention is required?

2

16.1 Legacy Series / update issue (related to configd)

« on: March 15, 2016, 07:03:46 pm »

Greetings. My recent experience, in case it is helpful, troubleshooting an issue that developed after an update...

About 3 days ago I did an update, and noticed while watching the updates download something about pfSense3, which caught my attention, and might ultimately point to an answer... Regardless, since that update, I have experienced very erratic behavior.

Besides the configd lockup issue, which is easily identifiable and fixable on the Lobby page after the most recent update, a few other things have happened. There are frequent lock-ups of the DNS Resolver, even though the status shows active. Restarting the Resolver doesn't help, and sometimes it doesn't restart. In addition, at times the network becomes completely non-responsive, and pages time-out and won't reload, internal and external pings timeout, etc.

I disabled all non-essential services, like the IPS/IDS and Proxy Server, even though no changes have been made and they have been working fine for months. However, the issue persisted. I finally downloaded a fresh 16.1 iso and reinstalled. It worked fine, so I started manually re-configuring the services, and all was well. Then I did an update, and continued configuring services, at which point the same erratic behavior started again. Makes me wonder if the "Serious Issue" post before this one is somehow related.

So, now I have reinstalled a fresh 16.1 again, and will reconfigure services again, but will NOT update until at least after the configd lockup issue is resolved, as it is likely related. Will report back if my non-updated configuration has issues over the next few days. Hopefully this helps...

3

General Discussion / backup story

« on: June 24, 2015, 05:58:18 pm »

This afternoon there was a brief power outage. The old UPS that was powering the OPNsense machine, along with a few network devices, immediately powered down. It appears that the old UPS needs a new battery, and a new battery status indicator light...

I installed a new APC UPS and rebooted OPNsense, but the only service that was running was ntpd. All other services, dhcpd, dnsmasq, apinger, and a few others like Proxy were Stopped, and would not Start. The log files of the services showed unusual error messages like missing user accounts, or misconfigured settings, although before the power failure everything was working fine.

It quickly became clear that the power outage had corrupted some files. Rather than troubleshooting a lot of random issues, I decided to simply reinstall and start fresh. Unfortunately I didn't have a backup of the configuration, but it's easy to recreate...

So, that is the story, for what it's worth. The question is, would it be possible to add an APC UPS monitoring package to the OPNsense repository?  https://freshports.org/sysutils/apcupsd/