CentOS 7.5 not listing ports when added to firewall-cmd

DustinB3403

Ok so dealing with an annoying issue.

I have these ports enabled on a local centos 7.5 system with the below.

firewall-cmd --list-ports

80/tcp 80/udp 443/tcp 443/udp 28443/tcp 28443/udp 9090/tcp 9090/udp

sestatus

SELinux status:                 disabled


lsof -i :9090

lsof -i :443

lsof -i :80

lsof -i :28443



firewall-cmd --list-all                              public (active)

  target: default

  icmp-block-inversion: no

  interfaces: ens192

  sources:

  services: ssh dhcpv6-client telnet

  ports: 80/tcp 80/udp 443/tcp 443/udp 28443/tcp 28443/udp 9090/tcp 9090/udp

  protocols:

  masquerade: yes

  forward-ports:

  source-ports:

  icmp-blocks:

  rich rules:

See, none of the ports are listening, but they should be. What am I doing wrong here?

momurda

@dustinb3403 Is there any services running? Without a running webserver or whatever service your want, youll get nothing with
lsof -i, or
ss -atun

DustinB3403

@momurda I'm just attempting to connect via telnet to make sure the ports are available before I go and add my service to this system.

momurda

Are you on a Windows machine doing this?
I just tried from my Windows 10 machine to linux webserver telnet hostname 80 to a computer i know has a web server running. No response, connection timed out.

DustinB3403

@momurda yes I am, Windows to Linux to confirm that the ports are open.

I was getting the same response.

DustinB3403

Worth a shot I guess from a Fedora system for testing. . . but still doesn't make sense.

momurda

Works linux>linux here.
Not windows>linux. Maybe the telnet client neesd an explicit exception in Windows Firewall.

DustinB3403

@momurda will give it a try, just booting up this system.

JaredBusch

@dustinb3403 said in CentOS 7.5 not listing ports when added to firewall-cmd:

@momurda I'm just attempting to connect via telnet to make sure the ports are available before I go and add my service to this system.

But the point of his response was unless you have something answering, it should not be open just because the firewall is not blocking. The OS will not know what to do with an attempted incoming connection unless a service is running on said port.

DustinB3403

@jaredbusch Look at the OP, i have telnet listening to those ports.

JaredBusch

@dustinb3403 said in CentOS 7.5 not listing ports when added to firewall-cmd:

@jaredbusch Look at the OP, i have telnet listening to those ports.

Ahh, didn't scroll enough.