Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: GRC failing my firewall setup!

  1. #1
    Join Date
    Jul 2008
    Location
    United Kingdom
    Posts
    307

    Default GRC failing my firewall setup!

    Before I go any further I must admit that I'm pretty rubbish at setting these up, so please be gentle!

    Now my problem; I have a normal desktop pc (I don't want to set it up as a server) but when I check the hardness of my set up with Gibson Research Centre, it fails. It can see ports 22,23,80,443 as closed but still visible.....? I have never had this happen to me before and struggling my way through yast firewall tool, I can find no easy way of sorting this out...... Please help

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,742

    Default Re: GRC failing my firewall setup!

    Doing as root
    Code:
    netstat -tulp
    will tell you what programs are listening on what ports. Those posrts may then be blocked by the Firewall, but the programs are there and listen (in vain).
    Henk van Velden

  3. #3
    Join Date
    Jul 2008
    Location
    United Kingdom
    Posts
    307

    Default Re: GRC failing my firewall setup!

    Thank you hcvv, As you recommend I input netstat -tulp and get the following:

    penguinclaw@linux-zz0c:~> sudo netstat -tulp

    We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

    root's password:
    Active Internet connections (only servers)
    Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
    tcp 0 0 *:sunrpc *:* LISTEN 3365/rpcbind
    tcp 0 0 localhost:ipp *:* LISTEN 3408/cupsd
    tcp 0 0 localhost:smtp *:* LISTEN 3557/master
    tcp 0 0 *:sunrpc *:* LISTEN 3365/rpcbind
    tcp 0 0 localhost:ipp *:* LISTEN 3408/cupsd
    tcp 0 0 localhost:smtp *:* LISTEN 3557/master
    udp 0 0 *:988 *:* 3365/rpcbind
    udp 0 0 *:mdns *:* 3187/avahi-daemon:
    udp 0 0 *:56773 *:* 3187/avahi-daemon:
    udp 0 0 *:sunrpc *:* 3365/rpcbind
    udp 0 0 *:49778 *:* 1672/dhclient6
    udp 0 0 *:ipp *:* 3408/cupsd
    udp 0 0 *:988 *:* 3365/rpcbind
    udp 0 0 *:sunrpc *:* 3365/rpcbind
    udp 0 0 *:14649 *:* 1672/dhclient6
    udp 0 0 *:dhcpv6-client *:* 1672/dhclient6
    penguinclaw@linux-zz0c:~>





    Is this information useful in solving my problem?

  4. #4
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,670
    Blog Entries
    3

    Default Re: GRC failing my firewall setup!

    Are you directly connected to the Internet, or are you behind a router?
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  5. #5
    Join Date
    Jul 2008
    Location
    United Kingdom
    Posts
    307

    Default Re: GRC failing my firewall setup!

    I am behind a Virgin "superhub" so I guess that is through a router. It's funny in the YAST firewall2 there doesn't seem to be anywhere to disable ports, whereas in Guarddog this is a very useful feature.

  6. #6
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,670
    Blog Entries
    3

    Default Re: GRC failing my firewall setup!

    I'm not familiar with 'Virgin "superhub"'

    Does your computer have a public IP, or does it have a private IP. A private IP is usually of the form 192.168.x.y or 10.x.y.z or 172.x.y.z ?

    If you have a private IP, then you are behind some sort of router, and GRC is seeing ports on the router rather than on your system.

    If you have a public IP, then it might be seeing your ports, and perhaps your firewall is not turned on.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  7. #7
    Join Date
    Jul 2008
    Location
    United Kingdom
    Posts
    307

    Default Re: GRC failing my firewall setup!

    Thanks nrickert, yes the superhub is a router and I have a private IP. I guess that means I should actually tune the settings on the router. I hadn't actually considered that GRC may only be looking at that!

    Now to dig out the handbook!!!

    Thanks for your help..... although I may be back

  8. #8
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,742

    Default Re: GRC failing my firewall setup!

    Quote Originally Posted by Penguinclaw View Post
    Is this information useful in solving my problem?
    As see, during my sleep somone else already gave you a hint you are following now. But anwsering your question above:
    1) I did not ask you to do
    Code:
    sudo netstat -tulp
    but
    Code:
    netstat -tulp
    Running anything as root when not needed is thus to your own risk.

    2) Next time when copying/pasting a peice of computer converstation here, please do so between CODE tags to make it readable (Posting in Code Tags - A Guide.

    3) It gives you insight in the network servers you are running and the ports they are listening to. The firewall may block those ports and thus make them unusable.
    In your case, your test tells you about e.g. port 80. But the output from the netstat tells you that there is no program on your system listening on port 80 (http). Thus be asured nobody can enter your system using that port, firewall or no firewall.
    Last edited by hcvv; 22-Apr-2011 at 01:05.
    Henk van Velden

  9. #9
    Join Date
    Jul 2008
    Location
    United Kingdom
    Posts
    307

    Default Re: GRC failing my firewall setup!

    Thank you hcvv. That was very helpful. I think by looking at this and reading man pages I learnt a little bit more. So thanks for pointing me in the right directions guys

  10. #10
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,742

    Default Re: GRC failing my firewall setup!

    You are quite welcome. I always hope that people not only get answers to their peoblems, but that they also get knowledge. Seems that this worked this time
    Henk van Velden

Page 1 of 2 12 LastLast

Posting Permissions

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