Search found 616 matches

by warron.french
2021/08/20 12:04:52
Forum: 8 /8-Stream / 9-Stream - General Support
Topic: [SOLVED] - iptables rule to firewalld
Replies: 4
Views: 1027

Re: [SOLVED] - iptables rule to firewalld

9997/tcp is for something to do with SPLUNK. That is about all I know presently and I am not sure if this is the correct port.

I am reading documentation that suggested the iptables command, which demonstrates how dated the instructions are.
by warron.french
2021/08/19 21:48:54
Forum: 8 /8-Stream / 9-Stream - General Support
Topic: [SOLVED] - iptables rule to firewalld
Replies: 4
Views: 1027

Re: iptables rule to firewalld

I learned from someone on ALMALinux's Chat site.

Code: Select all

firewall-cmd --permanent --add-port=9997/tcp && firewall-cmd --reload
by warron.french
2021/08/19 19:02:03
Forum: 8 /8-Stream / 9-Stream - General Support
Topic: [SOLVED] - iptables rule to firewalld
Replies: 4
Views: 1027

[SOLVED] - iptables rule to firewalld

How do I rewrite this iptables rule:

Code: Select all

iptables -I INPUT 4 -p tcp --dport 9997 -j ACCEPT
to firewall?
by warron.french
2021/08/11 19:01:11
Forum: 8 /8-Stream / 9-Stream - General Support
Topic: [RESOLVED] - reposync AppStream problems
Replies: 2
Views: 1166

Re: reposync AppStream problems

The solution to this problem is found in the following:-

Problem: conflicting requests viewtopic.php?f=54&t=77715
by warron.french
2021/08/11 18:56:31
Forum: 8 /8-Stream / 9-Stream - General Support
Topic: [RESOLVED] - Problem: conflicting requests
Replies: 16
Views: 19143

Re: Problem: conflicting requests

I did not realize I never closed this out.

The solution was to enable perl:5.26, by doing the following:

Code: Select all

dnf module enable perl:5.26
by warron.french
2021/08/11 18:52:30
Forum: 8 /8-Stream / 9-Stream - General Support
Topic: [RESOLVED] - Build Centos8 repos on RHEL-7.9
Replies: 5
Views: 1331

Re: Build Centos8 repos on RHEL-7.9

For others,
this did turn out to be a proxy problem. I got the issue resolved with the proxy administrator and then the packages started to sync down properly.

I will mark this as resolved.
by warron.french
2021/08/06 19:32:39
Forum: 8 /8-Stream / 9-Stream - General Support
Topic: [RESOLVED] - echo -e in italics
Replies: 4
Views: 1364

Re: echo -e in italics

I just found a possible reason why this is not working for me... It's more than likely the fact that I am using PuTTy after all. I found this link https://en.wikipedia.org/wiki/ANSI_escape_code#SGR_(Select_Graphic_Rendition)_parameters , which in the table provided within the section for SGR , it ac...
by warron.french
2021/08/06 19:24:17
Forum: 8 /8-Stream / 9-Stream - General Support
Topic: [RESOLVED] - echo -e in italics
Replies: 4
Views: 1364

Re: echo -e in italics

Sorry lightman47, I never got back to this.

I tried your syntax on the CLI within my PuTTy session on my Linux machine. It did not work, I wonder if PuTTY is part of the problem.


Does it work for you over a PuTTy session? Or are you using a terminal native to your CentOS OS?
by warron.french
2021/08/05 14:16:59
Forum: 8 /8-Stream / 9-Stream - General Support
Topic: [SOLVED] - Howto get precise start time in EPOCH for auditd
Replies: 3
Views: 930

Re: Howto get precise start time in EPOCH for auditd

Thanks MartinR, I was driving home and thinking about this problem and determined I could also use systemctl status auditd and suss the data out of that too. I posted my question to linux-audit@redhat.com and Steve Grubb wrote back to me with two options: 1. Your method below searching inside of the...
by warron.french
2021/08/04 19:18:12
Forum: 8 /8-Stream / 9-Stream - General Support
Topic: [SOLVED] - Howto get precise start time in EPOCH for auditd
Replies: 3
Views: 930

[SOLVED] - Howto get precise start time in EPOCH for auditd

Is there an undocumented switch argument to auditctl or any other method that can help assess the precise time and date that auditd was started? I would like to know, whether after 2 minutes or 2 years (who knows, it could happen), the epoch time stamp of when the last update occured to /etc/auditd....