Topics

1

General Discussion / 18.7 installation and configuration in console

« on: January 12, 2019, 11:58:59 pm »

I'm trying my best to translate my experiences with another product product several other somewhat other similar products  that I used prior that accomplished pretty much the same function as OPNSense. 

I can get through the installation up until you start configuring the interfaces. 
Once you get the WAN IP address configured, the console periodically gets flooded with what looks like a firewall log that wipes out any console input, forcing either invalid input or a  ctrl-c and start over. 

At this point I can't get the DHCP server up on the LAN interface up in order to get to the remainder of the configuration.

Is this an intentional feature of the console to have the log flood it like this?

Can't say that I find it that terribly useful.  How do you turn it off?  How do I get the DHCP server up on the LAN interface so I can a desktop up and into the web interface?

2

18.1 Legacy Series / [Solved?] - Restore failures

« on: June 30, 2018, 02:59:03 pm »

Geany line wrap bit me, I think. 


I'm trying to restore a list of unbound DNS entries.   
It's a lengthy list and although the OPNSense GUI is handy, it would be FAR easier to make mass changes in the XML backup file and restore.

I wrote three entries, saved and downloaded the configuration.
Unbound section looks like this:

Code: [Select]

  <unbound>
    <enable>1</enable>
    <custom_options/>
    <dnssec>1</dnssec>
    <regdhcp>1</regdhcp>
    <regdhcpstatic>1</regdhcpstatic>
    <txtsupport>1</txtsupport>
    <active_interface>lan</active_interface>
    <outgoing_interface>wan</outgoing_interface>
   <hosts>
      <host>hostname</host>
      <domain>domainname</domain>
      <rr>A</rr>
      <ip>192.168.1.25</ip>
      <mxprio/>
      <mx/>
      <descr>description of host</descr>
    </hosts>
 </unbound>


Duplicating the <host> to </host> content with appropriate edits, then attempting to restore results in this message in the restore interface with no further detail I can find anywhere:

Code: [Select]

The following input errors were detected:

    The configuration could not be restored.

If I try to restore only the Unbound information I get this message on a new page:

Code: [Select]

Fatal error: Uncaught OPNsense\Core\ConfigException: invalid config xml in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Config.php:336 Stack trace: #0 /usr/local/opnsense/mvc/app/library/OPNsense/Core/Config.php(168): OPNsense\Core\Config->loadFromFile('/tmp/tmpxml') #1 /usr/local/etc/inc/config.inc(71): OPNsense\Core\Config->toArrayFromFile('/tmp/tmpxml', Array) #2 /usr/local/www/diag_backup.php(134): load_config_from_file('/tmp/tmpxml') #3 /usr/local/www/diag_backup.php(298): restore_config_section('unbound', '


Any pointers would be greatly appreciated!


Edit: 
I tried changing a single character in the backup file and I get the same errors.

3

18.1 Legacy Series / New installation of 18.x -- root and admin password issues

« on: June 22, 2018, 04:22:59 am »

This has happened on both a VM installation and a physical installation on a Dell Powertedge 850 with 120GB SSD - several times on the VM - I did the physical install just to make sure:

After initial installation and setup, run through setup wizard and set root and admin passwords in the wizard.
Finish tweaking settings.
Shutdown.
Bring the system back up.
Neither the root nor admin account will login using the passwords set in the wizard, nor the installer, root or admin ID login with the default passwords.

What am I missing in setup?
Don't use the wizard?

4

18.1 Legacy Series / ESXI OPNSense installations

« on: June 17, 2018, 06:44:32 pm »

I'm setting up OPNSense firewall on ESXi 6.5 and I'm looking for best practices on configuring the virtual networks in the ESXI server for management, WAN, LAN, DMZ and and interface to connect to a dedicated connection to a wireless access point. 

This really isn't an OPNSense issue, but a VMWare issue, but I'm hoping someone has already done this and has some pointers on the ESXI side of the setup.