D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: sfitt on November 30, 2011, 08:29:58 AM

Title: External port scan indicates udp port 111 is open, how do I block it on DIR-655
Post by: sfitt on November 30, 2011, 08:29:58 AM

External port scan indicates udp port 111 is open, how do I block it on DIR-655

Title: Re: External port scan indicates udp port 111 is open, how do I block it on DIR-655
Post by: FurryNutz on November 30, 2011, 08:54:57 AM

This maybe open for a reason:
http://www.grc.com/port_111.htm (http://www.grc.com/port_111.htm)

What are your SPI setting set for currently?

Title: Re: External port scan indicates udp port 111 is open, how do I block it on DIR-655
Post by: sfitt on November 30, 2011, 09:24:59 AM

I am aware of the Sun Remote Procedure Call, however there are no Unix or Linux based systems on the network. SPI is Enabled, UDP Endpoint Filtering is Address Restricted , TCP Endpoint Filtering is Port And Address Restricted.

Title: Re: External port scan indicates udp port 111 is open, how do I block it on DIR-655
Post by: FurryNutz on November 30, 2011, 09:40:36 AM

What Hardware version is your router? Look at sticker under router.
What Firmware version is currently loaded? Found on routers web page under status.

Title: Re: External port scan indicates udp port 111 is open, how do I block it on DIR-655
Post by: sfitt on November 30, 2011, 10:04:02 AM

Hardware Version: B1   Firmware Version: 2.00NA

Title: Re: External port scan indicates udp port 111 is open, how do I block it on DIR-655
Post by: FurryNutz on November 30, 2011, 10:21:37 AM

Hmm. I have the same Version at home. I will have to check on this when I get home.
Most research on line results in a lot of information regarding blocking on OSs and not pertaining to routers. I might presume that it's open for a reason since Unix and Linux bases OSs might need it open and Dlink might push this to the operators and users of those OSs to block it in the OS and not the router. So not sure if there is a way to block it on the router...you might be able to set up a Port Forward rule and select Deny All. Use 111 for BOTH TCP and UDP and Deny ALL.

http://www.sans.org/security-resources/idfaq/blocking.php (http://www.sans.org/security-resources/idfaq/blocking.php)

http://www.wilderssecurity.com/showthread.php?t=303979 (http://www.wilderssecurity.com/showthread.php?t=303979)