| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
- Add a upgrade code to fix asn1dn string format to match strongSwan needs
- Bump config version to 11.8
|
|
|
|
|
|
| |
mandatory. Revert "myid_data and peerid_data fields are not relevant with asn1dn."
This reverts commit b8754cc85db7e92322f605bbb4b2f90bde90bb7f.
|
| |
|
|
|
| |
Improve this a little more to match only alpha after /dev/cua (/dev/cuau for example)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It originally coped with things like cuau1 cuau1.1
Then I made it cope with things like cuau1 cuau11 but it stopped working for cuau1.1
This one copes with:
cuau1
cuau1.1
cuau1.11
cuau11
cuau11.1
cuau11.11
That should allow for all sorts of reasonable device name files without matching other stuff in /dev (like cuau1.init cuau1.lock) that we need to ignore.
Please think if I have covered the bases here.
|
|
|
|
| |
is asn1dn. Ticket #4792
|
| |
|
|
|
|
| |
This reverts commit 6605035f9d2a04d1d4b724f6e993bc3f5c6d173d.
|
|\ |
|
|/
|
| |
Cherry pick of https://github.com/pfsense/pfsense/commit/90ad3a76edae543bcc63252b14660ac4baee291e
|
|\ |
|
| | |
|
| |
| |
| | |
Actually there was no real problem, but having a mis-spelling like this means that English speakers will waste time (like I did) double-checking to see if the mis-spelling would cause a real problem.
|
| |
| |
| |
| |
| | |
If you open firewall_aliases_import and enter just an invalid Alias Name (e.g. a$b) and press save or press save with all fields empty, then the screen redraws but the input error(s) is not displayed.
This fixes it.
|
| |
| |
| |
| |
| |
| | |
If you click "+" to add an alias, then press Save without entering anything, you get:
Warning: Invalid argument supplied for foreach() in /usr/local/www/firewall_aliases_edit.php on line 402
as well as the various messages related to $input_errors.
This change ensures that $input_addresses array always exists (even if it has no real entries) so that the foreach() warning does not happen.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Create a host-type alias. Put just a number in "IP or FQDN" - e.g. I made alias name "Zqw" and a single host "23". The webGUI reports:
There were error(s) loading the rules: /tmp/rules.debug:44: syntax error - The line in question reads [44]: table { 23 }
and /tmp/rules.debug has:
table <Zqw> { 23 }
Zqw = "<Zqw>"
which pf does not cope with.
It is possible to have a host name that is a number, and end up with a domain name like 23.mycompany.com - unfortunately some Wally allowed such things in standards many years ago, so it can be rather difficult to tell the difference between a number and a host name.
This change improves the check when looking through alias entries and deciding if they are meant to be a name or a "bottom-level" value (address, subnet, port, port range). Anything that ends up looking like a host name gets given to filterdns to sort out. "Names" like "23" now get given to filterdns instead of being put directly into the table in pf. This makes things happier. Even if filterdns cannot resolve "23", at least it tries and nothing barfs.
|
| |
| |
| | |
Make the required fields be correct and match thier text names, which should each have their own gettext() cal so as to build a proper array at line 81. Basically it was all broken and the errors displayed when field/s were left empty were rubbish.
|
| |
| |
| |
| |
| | |
The reqdfields had only 4 entries but reqdfieldsn has 5 entries and the field names to text descriptions did not match up.
Fixed it.
|
|/
|
|
|
| |
If you go to Interfaces, assign, PPPs, press "+" to add an entry, then press Save without entering anything then you get a warning about the foreach() here.
The is_array() check fixes it.
|
|
|
|
|
| |
Removing the "." that was in {,.[0-9]} allows it to match /dev/cuau10 and onward.
I added lots of comments on the glob expression, because the format of the glob expression is not the same as an ordinary regex.
|
|
|
|
| |
specified.
|
|
|
|
| |
3e31a7f82589d3350f111bd7d81cc83a0ab253e2
|
|
|
|
| |
b45537f75b24bc323987094e459db7b2f75aa405
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
makes QinQ un-deletable where the parent interface no longer exists
(removed, config restored from diff hardware, etc.).
|
| |
|
| |
|
| |
|
|
|
|
| |
ticket #4803
|
| |
|
| |
|
|
|
|
| |
passwd/group problem is fixed. Ticket #4523
|
|
|
|
| |
previous versions, fixing a variety of other ID issues. Latter will break some mobile IPsec circumstances, fix for that to come after more testing. Ticket #4811
|
|
|
|
| |
When enabling or disabling a route by using the enable/disable button on the Routes page, the destination network was not being put in the config change description, although the code intended it to be there.
This fixes it.
|
| |
|
| |
|
| |
|
|
|
|
| |
so people don't think they should be using it.
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|