Franco Fichtner 2db592b1fb firewall: always display all known gateways on edit
There are a few cases where the gateway code is eligible
to drop a gateway on grounds of being disabled, inactive,
unconfigured or where the actual interface assigned is
disabled.  This is undesire because users that configure
a gateway won't be able to use it.

There are no bad side effects from the former by selecting
a whatsoever dysfunctional gateway, because the problem still
has to be fixed by the user in the gateway setup itself.

Worst of all, removing a disabled but used gateway makes
it not show up on edit, effectively wiping its setting on
save.  This breaks POLA.

While there, also enable the null routes for IPv4 and IPv6.

PR: https://forum.opnsense.org/index.php?topic=2100
2016-02-04 07:59:08 +01:00
2016-01-28 07:07:29 +01:00
2015-06-22 07:45:25 +02:00
2015-07-29 17:22:53 +02:00
2015-12-11 08:31:06 -05:00

OPNsense GUI and system management

The OPNsense project invites developers to start contributing to the code base. For your own purpose or even better to join us in creating the best open source firewall available.

The build process has been designed to make it truly straightforward and easy for anyone to build and code. Being able to get the sources and build it yourself is one of the key factors of open source software.

Although a lot of the code is still in flux, we try to publish the direction we're taking on our wiki page. The main outline of the new codebase is available at:

https://wiki.opnsense.org/index.php/Develop:Architecture

Our aim is to gradually evolve to a new codebase instead of using a big bang approach into something new.

Build tools

To create working software like OPNsense you need the sources and the tools to build it. The build tools for OPNsense are freely available. No strings attached.

Notes on how to build OPNsense can be found in the tools repository:

https://github.com/opnsense/tools

Contribute

You can contribute to the project in many ways, e.g. testing functionality, sending in bug reports or creating pull requests directly via GitHub. Any help is always very welcome!

License

OPNsense is and will always be available under the 2-Clause BSD license:

http://opensource.org/licenses/BSD-2-Clause

Every contribution made to the project must be licensed under the same conditions in order to keep OPNsense truly free and accessible for everybody.

Description
No description provided
Readme BSD-2-Clause 88 MiB
Languages
PHP 60.2%
Volt 11.3%
Python 9%
JavaScript 7%
SCSS 5.1%
Other 7.2%