"
I have done this before by renaming the config file and rebooting.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
#16
18.7 Legacy Series / Re: Locked out of GUI - Reseet to factory from console (shell)
November 14, 2018, 08:42:34 PM #17
18.7 Legacy Series / Firewall aliases missing
November 14, 2018, 06:52:16 PM
Hi,
I have two firewalls running OPNsense. One of them seems to have lost it's aliases :'(. They are disappeared from the Firewall->Aliases view but when I try to add/edit a FW rule they are selectable.
If I add try adding a new alias then the new alias appears in the list but then all the other aliases completely disappear!
Is there an easy way to get them back?
I have two firewalls running OPNsense. One of them seems to have lost it's aliases :'(. They are disappeared from the Firewall->Aliases view but when I try to add/edit a FW rule they are selectable.
If I add try adding a new alias then the new alias appears in the list but then all the other aliases completely disappear!
Is there an easy way to get them back?
#18
17.1 Legacy Series / Upgrade 16.7 to 17.1 success.
February 02, 2017, 10:35:58 PM
Hi,
just to let you know I successfully upgraded two systems from 16.7 to 17.1. Everything went smoothly and everything was working as it should. I have one system mainly used as a VPN gateway (OpenVPN) and another for firewall (and using DNS resolver).
I was so pleased I sent you a little donation to say thanks for your hard work on making such a useful product.
Long may it continue.
Regards,
Kevin
just to let you know I successfully upgraded two systems from 16.7 to 17.1. Everything went smoothly and everything was working as it should. I have one system mainly used as a VPN gateway (OpenVPN) and another for firewall (and using DNS resolver).
I was so pleased I sent you a little donation to say thanks for your hard work on making such a useful product.
Long may it continue.
Regards,
Kevin
#19
16.1 Legacy Series / Re: DNS Resolver failing to start after upgrade
February 28, 2016, 11:47:17 AM
Hi,
that command (unbound-control-setup) worked. Thanks!
that command (unbound-control-setup) worked. Thanks!
#20
16.1 Legacy Series / [SOLVED] DNS Resolver failing to start after upgrade
February 27, 2016, 05:32:49 PM
I upgrade from (I think) 16.1.3 to 16.1.4 and since then the DNS Resolver service fails to start. All I get in the logs is:
opnsense: /status_services.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1456589818] unbound[17195:0] debug: creating udp4 socket 0.0.0.0 53 [1456589818] unbound[17195:0] debug: creating tcp4 socket 0.0.0.0 53 [1456589818] unbound[17195:0] debug: creating udp6 socket :: 53 [1456589818] unbound[17195:0] debug: creating tcp6 socket :: 53 [1456589818] unbound[17195:0] debug: creating tcp4 socket 127.0.0.1 953 [1456589818] unbound[17195:0] debug: switching log to syslog'
I switched to DNS Forwarder which works ok but would like to go back to Resolver due to running my own domain.
opnsense: /status_services.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1456589818] unbound[17195:0] debug: creating udp4 socket 0.0.0.0 53 [1456589818] unbound[17195:0] debug: creating tcp4 socket 0.0.0.0 53 [1456589818] unbound[17195:0] debug: creating udp6 socket :: 53 [1456589818] unbound[17195:0] debug: creating tcp6 socket :: 53 [1456589818] unbound[17195:0] debug: creating tcp4 socket 127.0.0.1 953 [1456589818] unbound[17195:0] debug: switching log to syslog'
I switched to DNS Forwarder which works ok but would like to go back to Resolver due to running my own domain.
