Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12

Thread: Firewalld manual and examples not what I expected.

  1. #11
    Join Date
    Sep 2012
    Posts
    5,185

    Default Re: Firewalld manual and examples not what I expected.

    Quote Originally Posted by Budgie2 View Post
    I do not understand why this tells me all the ports are closed
    Because no application is listening on any port.

  2. #12
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,076
    Blog Entries
    15

    Default Re: Firewalld manual and examples not what I expected.

    Quote Originally Posted by Budgie2 View Post
    Hi Malcolm here are the findings of my very simple scan. 224 is the address of the workstation and 130 is the address of the NAS.
    With firewall running I get:

    Code:
    alastair@AJBR-W530:~> nmap 192.168.169.224
    Starting Nmap 7.80 ( https://nmap.org ) at 2019-10-13 18:18 BST
    Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
    Nmap done: 1 IP address (0 hosts up) scanned in 0.04 seconds
    And the NAS:-

    Code:
    alastair@AJBR-W530:~> nmap 192.168.169.130
    Starting Nmap 7.80 ( https://nmap.org ) at 2019-10-13 18:19 BST
    Nmap scan report for 192.168.169.130
    Host is up (0.0069s latency).
    Not shown: 987 closed ports
    PORT      STATE SERVICE
    21/tcp    open  ftp
    22/tcp    open  ssh
    80/tcp    open  http
    111/tcp   open  rpcbind
    139/tcp   open  netbios-ssn
    443/tcp   open  https
    445/tcp   open  microsoft-ds
    631/tcp   open  ipp
    873/tcp   open  rsync
    2049/tcp  open  nfs
    8080/tcp  open  http-proxy
    9000/tcp  open  cslistener
    30000/tcp open  ndmps
    
    Nmap done: 1 IP address (1 host up) scanned in 0.14 seconds
    alastair@AJBR-W530:~>
    With firewall off I get:-

    Code:
    alastair@AJBR-W530:~> nmap 192.168.169.224
    Starting Nmap 7.80 ( https://nmap.org ) at 2019-10-13 18:21 BST
    Nmap scan report for 192.168.169.224
    Host is up (0.0063s latency).
    All 1000 scanned ports on 192.168.169.224 are closed
    
    Nmap done: 1 IP address (1 host up) scanned in 0.14 seconds
    alastair@AJBR-W530:~>
    I do not understand why this tells me all the ports are closed because with the FW inactive my application can see the NAS and works.

    I shall need a bit of help with the zones and interfaces here too as I am not sure which I should be trying to set.

    Grateful for your help when you have a moment.
    Hi
    So what service are you using to connect to the NAS, samba? If so in the add the samba-client to the default firewall zone your system is set to.

    What arvidjaar said

    Try localhost instead of your external ip address.

    Code:
    nmap localhost
    
    Starting Nmap 7.80 ( https://nmap.org ) at 2019-10-13 16:51 CDT
    Nmap scan report for localhost (127.0.0.1)
    Host is up (0.00013s latency).
    Other addresses for localhost (not scanned): ::1
    Not shown: 996 closed ports
    PORT      STATE SERVICE
    22/tcp    open  ssh
    25/tcp    open  smtp
    631/tcp   open  ipp
    24800/tcp open  unknown
    I use the following to see what zone and services are in use (as root user);

    Code:
    firewall-cmd --list-all
    The gui shows the interfaces and zones, should be self explanatory?
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •