Révision 194e05d5
Add class for outgoing PXP connections
REFERENCE.md | ||
---|---|---|
53 | 53 |
* [`nftables::rules::out::pop3`](#nftablesrulesoutpop3): allow outgoing pop3 |
54 | 54 |
* [`nftables::rules::out::postgres`](#nftablesrulesoutpostgres): manage out postgres |
55 | 55 |
* [`nftables::rules::out::puppet`](#nftablesrulesoutpuppet): manage outgoing puppet |
56 |
* [`nftables::rules::out::pxp_agent`](#nftablesrulesoutpxp_agent): manage outgoing pxp-agent |
|
56 | 57 |
* [`nftables::rules::out::smtp`](#nftablesrulesoutsmtp): allow outgoing smtp |
57 | 58 |
* [`nftables::rules::out::smtp_client`](#nftablesrulesoutsmtp_client): allow outgoing smtp client |
58 | 59 |
* [`nftables::rules::out::ssh`](#nftablesrulesoutssh): manage out ssh |
... | ... | |
829 | 830 |
|
830 | 831 |
Default value: `8140` |
831 | 832 |
|
833 |
### <a name="nftablesrulesoutpxp_agent"></a>`nftables::rules::out::pxp_agent` |
|
834 |
|
|
835 |
manage outgoing pxp-agent |
|
836 |
|
|
837 |
* **See also** |
|
838 |
* also |
|
839 |
* take a look at nftables::rules::out::puppet, because the PXP agent also connects to a Puppetserver |
|
840 |
|
|
841 |
#### Parameters |
|
842 |
|
|
843 |
The following parameters are available in the `nftables::rules::out::pxp_agent` class: |
|
844 |
|
|
845 |
* [`broker`](#broker) |
|
846 |
* [`broker_port`](#broker_port) |
|
847 |
|
|
848 |
##### <a name="broker"></a>`broker` |
|
849 |
|
|
850 |
Data type: `Variant[Stdlib::IP::Address,Array[Stdlib::IP::Address,1]]` |
|
851 |
|
|
852 |
PXP broker IP(s) |
|
853 |
|
|
854 |
##### <a name="broker_port"></a>`broker_port` |
|
855 |
|
|
856 |
Data type: `Stdlib::Port` |
|
857 |
|
|
858 |
PXP broker port |
|
859 |
|
|
860 |
Default value: `8142` |
|
861 |
|
|
832 | 862 |
### <a name="nftablesrulesoutsmtp"></a>`nftables::rules::out::smtp` |
833 | 863 |
|
834 | 864 |
allow outgoing smtp |
Formats disponibles : Unified diff