diff options
| author | smos <seth.mos@dds.nl> | 2012-06-01 07:41:15 +0200 |
|---|---|---|
| committer | smos <seth.mos@dds.nl> | 2012-06-01 07:46:55 +0200 |
| commit | e02caf4ab97b993a62e81c5002bd0581165e4a64 (patch) | |
| tree | 0c445c049eff3e2600fc136ba881c3ebabf712f6 /usr/local/www/system_gateways_edit.php | |
| parent | 4473e33cf345da613da44f0d7a1df2beb1686731 (diff) | |
| download | pfsense-e02caf4ab97b993a62e81c5002bd0581165e4a64.zip pfsense-e02caf4ab97b993a62e81c5002bd0581165e4a64.tar.gz | |
Actually save the IPprotocol variable into the config, otherwise it stil won't work.
People will likely need to edit and save their gateways now if they have double entries.
e.g. both manual and automatically added entries, these will dissapear as soon as you save.
If we know if the gateway or monitor is ipv4 or ipv6 we can autodetect which prevents this.
Because we don't know what address family the gateway on a dual stack interface belongs to we better not guess, and let the user figure it out. Often, a edit and save is the fastest.
For upgrading from 2.0 we could mark all gateways as being ipv4 which prevents half of the issues.
Redmine ticket #2463
Diffstat (limited to 'usr/local/www/system_gateways_edit.php')
| -rwxr-xr-x | usr/local/www/system_gateways_edit.php | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/usr/local/www/system_gateways_edit.php b/usr/local/www/system_gateways_edit.php index 6a8936e..84a0b32 100755 --- a/usr/local/www/system_gateways_edit.php +++ b/usr/local/www/system_gateways_edit.php @@ -243,6 +243,7 @@ if ($_POST) { $gateway['gateway'] = "dynamic"; $gateway['name'] = $_POST['name']; $gateway['weight'] = $_POST['weight']; + $gateway['ipprotocol'] = $_POST['ipprotocol']; $gateway['interval'] = $_POST['interval']; $gateway['descr'] = $_POST['descr']; if ($_POST['monitor_disable'] == "yes") |
