pfSense

Return GWG IP protocol (version) when no gateway IP

This is a resubmit of an older pull request I had closed. It came up again in the forum, with a user setting up a VM environment and wondering why he cannot make policy-routing rules to a gateway group. The gateway group names did not display because all his WANs were down at the time and so the existing code was too dumb to determine the IP protocol (version 4 or 6) when none of the WANs in the gateway group actually have an IP address yet.

Oops forgot the query message

Add a function to read the status of connections/SAs/SPDs from smp plugin of StrongSWAN. No need to go through the setkey dumps

Make xmlreader parse any document and properly consider listtags specified and attributes. Probably should be made the default due to its speed.

Parse even attributes when present

Merge pull request #975 from stilez/patch-1

Port dropdowns: Put port no. after descrip

Port dropdowns: Put port no. after descrip

At the moment, even if a port number is entered, it's re-displayed only as a port name when editing. Users who don't have port names -> numbers lookup memorised can't easily confirm when editing a rule, that the port is as intended. Then, when they return to firewall_rules.php the same rules have ports displayed as numbers not names (inconsistent)....

Push log changes for IPSec and fix generation of strongswan.conf and ipsec.secrets to be properly considered

• Correct logging to syslog and proper file for ipsec from strongswan
• Use proper commands to reload strongswan rather than just the daemon

Merge pull request #970 from phil-davis/master

Fix #3483 only use IPv4 DNS servers in DHCP v4 conf