Netgate SG-1000 microFirewall

Author Topic: Ports not stealth  (Read 203 times)

0 Members and 1 Guest are viewing this topic.

Offline Remf

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Ports not stealth
« on: November 10, 2017, 10:24:02 am »
Hi
I have just run Shields Up from Gibson GRC against my new pfSense firewall and its reporting majority of the ports stealthed except 135, 137, 138, 139, 445. These are closed?

I don't have any port forwarding set up or UPnP. pfSense is patched to latest version with a very basic rule set.
Any ideas?

Any yes I am a pfSense newbie :-)

Offline KOM

  • Hero Member
  • *****
  • Posts: 5370
  • Karma: +667/-19
    • View Profile
Re: Ports not stealth
« Reply #1 on: November 10, 2017, 10:30:47 am »
Those are all MS networking ports.  By default, pfSense allows no access in from WAN.  All ports should show stealth.

Offline johnpoz

  • Hero Member
  • *****
  • Posts: 14295
  • Karma: +1330/-193
  • Not a pfSense employee, they cannot fire me...
    • View Profile
Re: Ports not stealth
« Reply #2 on: November 10, 2017, 10:42:50 am »
You have something in front of pfsense listening on those ports.. Or your isp is rejecting them vs just dropping them..  Or you forwarded them inbound.. Pfsense would not be listening on any of those ports, and as stated out of the box all inbound ports into pfsense unsolicated would be dropped.. Or as grc likes to use the nonsense term "stealth".. Its not a valid networking term btw..
- An intelligent man is sometimes forced to be drunk to spend time with his fools.
- Please don't PM me for personal help
- if you want to say thanks applaud or https://www.freebsdfoundation.org/donate/
1x SG-2440 2.3.4_p1 (work)
1x 2.4.2-RELEASE on VM esxi 6.5 (home)

Offline NogBadTheBad

  • Sr. Member
  • ****
  • Posts: 357
  • Karma: +26/-0
    • View Profile
Re: Ports not stealth
« Reply #3 on: November 10, 2017, 11:27:06 am »
I see this when I use shields up.

It will be down to your ISP  blocking the ports at their ingress point as john said.

I bet if you do a packet capture on the WAN interface, you won’t even see those ports hit your firewall.

Offline johnpoz

  • Hero Member
  • *****
  • Posts: 14295
  • Karma: +1330/-193
  • Not a pfSense employee, they cannot fire me...
    • View Profile
Re: Ports not stealth
« Reply #4 on: November 10, 2017, 12:18:54 pm »
Many an ISP block those ports.. But they you would think they would just drop, not sure why they would send reject.. But guess it is the nice thing to do ;)  Just you almost never see that on firewall.. Because if your sending me packet I don't want, why should I spend bandwidth and cycles telling you.. Unless you were on my network... From the public internet sure not going to spend effort letting answering the noise.. I reject inbound, so if client tries to go outbound on a port I prevent they get a reject.

Do you scream go away when the jehovah witness comes a knocking at your door or do you just ignore them until they go away ;)  You sure don't want to get up and answer the door just to tell them go away do you.. Better to just sit back on the couch and finish your beer..

Only thing I reject from internet is traceroute udp ports, so my my traceroute to on ipv4 or through via ipv6 see the hop ;)

But yes as stated - great test is to sniff for it on pfsense wan.. If pfsense doesn't see it even - sure couldn't be sending reject..
- An intelligent man is sometimes forced to be drunk to spend time with his fools.
- Please don't PM me for personal help
- if you want to say thanks applaud or https://www.freebsdfoundation.org/donate/
1x SG-2440 2.3.4_p1 (work)
1x 2.4.2-RELEASE on VM esxi 6.5 (home)