RedHat/CentOS 7 Firewalld is Blocking BES Traffic - BES Client
| 0 Votes |
Versioning - This is the latest version.
| 1 | CentOS 7 Firewalld is Blocking BES Traffic - BES Client | 9/25/2015 12:55:44 PM |
| 2 | CentOS 7 Firewalld is Blocking BES Traffic - BES Client | 10/2/2015 6:44:13 PM |
| 3 | RedHat/CentOS 7 Firewalld is Blocking BES Traffic - BES Client | 2/7/2018 1:27:13 PM |
| 4 | RedHat/CentOS 7 Firewalld is Blocking BES Traffic - BES Client | 2/7/2018 1:28:02 PM |
Description
|
The listed computers have firewalld enabled and are not configured to allow inbound UDP traffic on the port used by BES (BES uses port 52311 by default). The BES Server and BES Relays send UDP packets to the BES Clients to notify them that there is new information available such as new Fixlet messages, actions, and computer refreshes. BES Clients on relevant computers will not receive UDP notification packets and therefore will not see new actions or new Fixlet messages until they gather the new actionsite, which is by default, once a day. After configuring firewalld to allow inbound UDP traffic on the BES Listen Port, BES Clients will resume normal communication with the BES Server and BES Relays. Note: After this action is applied, affected BES Clients will not report until they have performed their standard once-per-day gather or until the BES Client is restarted. Note: The firewalld configuration is modified by inserting a new service into /etc/firewalld/services and enabling it on the default zone. |
Property Details
| 25072 | |
| Beta - Preliminary testing ready for more | |
| RedHat/CentOS 7 Firewalld is Blocking BES Traffic - BES Client | |
| Support | |
| 0 | |
| Internal | |
| <Unspecified> | |
| Important | |
| 2/7/2018 1:28:02 PM | |
| RedHat RHEL RedHat7 RHEL7 CentOS Cent CentOS7 Cent7 el7 firewalld firewall | |
| rexit1982 on 2/7/2018 1:28:02 PM | |
| rexit1982 on 2/19/2018 7:29:44 AM | |
| 10414 Views / 36 Downloads | |
* Average over 0 ratings.
** Log In or Register to add your rating.
|
Relevance
| Used in 223 fixlets | * Results in a true/false |
| Used in 32 fixlets | * Results in a true/false |
| Used in 6 fixlets | * Results in a true/false |
| Used in 3 fixlets | * Results in a true/false |
| Used in 3 fixlets | * Results in a true/false |
Actions
Action 1 (default)
//Modify the iptables saved ruleset
delete __appendfile
appendfile #!/bin/bash
appendfile echo -e '"1.0" encoding="utf-8"?>\n\n ' > /etc/firewalld/services/bigfix.xmlbigfix \nThe BES Server and BES Relays send UDP packets to the BES Clients to notify them that there is new information available such as new Fixlet messages, actions, and computer refreshes. This service permits that traffic on the port designated by the server. \nport="{port number of selected server as string}"/>\n
appendfile firewall-cmd --reload
appendfile firewall-cmd --permanent --zone=public --add-service=bigfix
appendfile firewall-cmd --reload
wait chmod +x "{(client folder of current site as string) & "/__appendfile"}"
wait "{(client folder of current site as string) & "/__appendfile"}"
//delete delete __appendfile
This action will be considered successful when the applicability relevance evaluates to false.
Action 2
//Disable iptables
delete __appendfile
appendfile #!/bin/bash
appendfile systemctl disable firewalld.service
appendfile systemctl stop firewalld.service
wait chmod +x "{(client folder of current site as string) & "/__appendfile"}"
wait "{(client folder of current site as string) & "/__appendfile"}"
//delete delete __appendfile
This action will be considered successful when the applicability relevance evaluates to false.
Action 3
http://support.bigfix.com/cgi-bin/kbdirect.pl?id=113
Sharing
| Social Media: |
Comments
 |
|
| related: https://forum.bigfix.com/t/firewall-fix-when-setting-up-centos-rhel-fedora-relay/13697 | |
 |
|
| After a little more searching I found this : https://bigfix.me/fixlet/details/3984 Will test it and comment there! | |
|
|
| Worked fine for CentOS 7 - are there similar fixlets for previous versions? I tried editing this one, changing "Linux CentOS (7)" to "Linux CentOS (6)" in the relevancy, but it didn't seem to work - never became relevant for my CentOS 6 instance. | |
