since the indexes themselves aren't used, it should be safe to change the current list interpretation into a named one, this would ease operations like https://github.com/opnsense/core/pull/5184
* Remove the unset-after-write-before-redirect logic of dhcpd on
WAN that practically does nothing.
* At least since b6b3a5ad1d6c41 interface_bring_down() does not
tamper with down flag of the interface avoiding the need to
set the up flag to fix "VLAN" (multiple times).
* Remove debug output that I have never seen before. The function
call below will throw an error too if that is even possible.
commit 46e0383625acfa59e723c390d0b5b2feed8a53aa
Author: Ad Schellevis <ad@opnsense.org>
Date: Mon Aug 23 11:05:53 2021 +0200
Firewall / Log - Live log : support rfc5424 format for https://github.com/opnsense/core/pull/5175
commit 0cf3030724d02181991436b324fe5fc70118d4d5
Author: Ad Schellevis <ad@opnsense.org>
Date: Sat Aug 21 09:36:56 2021 +0200
System logging - switch local logging to rfc5424 format.
Allow custom destinations to choose for rfc5424. closes https://github.com/opnsense/core/issues/4911
commit a46e39bcecca6dab1d5a68a0e7f481ea42c16034
Author: Ad Schellevis <ad@opnsense.org>
Date: Fri Aug 20 18:23:22 2021 +0200
System logging - switch local logging to rfc5424 format.
add severity filter to api and log pages
commit b0f38003d7745a01202ffca5e7b5b697ff211f1e
Author: Ad Schellevis <ad@opnsense.org>
Date: Fri Aug 20 15:42:58 2021 +0200
System logging - switch local logging to rfc5424 format.
Split BaseLogFormat into a generic LogFormat and a child NewBaseLogFormat to be able to support both property and method based parsers to keep (external) plugins compatible.
commit 264513f148185faf4a4509bc19aa35739c9844f9
Author: Ad Schellevis <ad@opnsense.org>
Date: Thu Aug 19 19:56:19 2021 +0200
System logging - switch local logging to rfc5424 format.
Refactor log parser (BaseLogFormat), since the plugins use this as well we might have to undo a bit or refactor those as well.
This will need a new version of py-dnspython (py-dnspython2 in ports) for dns.asyncresolver support. Some additional log messages have been added to gain more insights into the resolving process via the general log.
Intermediate results aren't saved to disk anymore, which also simplifies the resolve() function in the Alias class. An address parser can queue hostname lookups for later retrieval (see _parse_address()) so we can batch process the list of hostnames to be collected.
o add "Automatic user creation" option in System/Access/Servers (for ldap + derivatives)
o simple detached flow, updatePolicies() calculates differences between local and remote group membership, when there is something to sync (remote groups exists) and a local user doesn't exist a configd signal is send to create a new empty user without rights and a random password.
The user_dn field isn't populated, although this will cost additional queries to the remote host, it might be worth the flexibility of allowing to move users to different auth scopes.
This way we can keep track of the underlying ABI in case a business
version needs to find its way back to community ABI.
In general ALTABI is just the derived ABI version, i.e. the one that
shares the same build settings/packages/OS version.
* Allow DNS resolver to skip entry on EmptyLabel
A name like '.example.com' is not a valid name, but should be handled like a non existant name instead of throwing an exception
It seems that comments are limited in ipfw to 80 chars which is not
documented (at least not in the manpage `ipfw(8)`). If users
accidentally use long traffic shaper rule descriptions this limit could
be reached causing updates via the GUI apply button to be silently
ignored which will cause confusion.
`ipfw /usr/local/etc/ipfw.rules` shows the following error:
Line 77: comment too long (max 80 chars)
and exists with edit code 65.
Interestingly, a slice of up to `0:83` still works. As this is
undocumented and the error says max 80 chars I go with something
slightly below this max to account for the whitespace.
o add Use flowid and Use strict options
o extend interfaces overview with various lagg properties
o show unassigned interfaces in overview so lagg parents are always visible
o fix collapse event in overview to reference by internal name in stead of description.
