Stealth port 113 ?
-
Can pfSense stealth a NAT.d port 113 ?. Could anyone please give a quick tut. howto do it?, Thanks ???
-
Can it be done? ???
-
You cannot "stealth" an open port.
You can either allow connections on it, or block the traffic, but you have to choose.
The best you can do is limit connections to port 113 from trusted sources (IPs of IRC servers, etc) that you know will connect, and block everyone else.
-
Just forward it to an unused ip on your network.
-
Just forward it to an unused ip on your network.
If he didn't want to use it, leaving it blocked at the firewall would be the best option.
It should be blocked by default. No need to create any extra rules, port forwards, etc.
-
-
You cannot "stealth" an open port.
You can either allow connections on it, or block the traffic, but you have to choose.
The best you can do is limit connections to port 113 from trusted sources (IPs of IRC servers, etc) that you know will connect, and block everyone else.
I guess i haveto settled with "closed" on system scan then if thare´s an hack or something else i could do. Thanks for the reply though.
-
If it is showing up as "closed" instead of "stealth" and you did not open up that port, it's probably being opened via UPNP. You can check this under Status > UPNP
By default, if you have done nothing to open the port, it should be listed as "stealth" by scanners that use that terminology.
I don't use mIRC these days but it used to only listen on port 113 (ident) when connecting to an IRC server, so it's probably safe if that is the case.
-
Iv disabled the NAT rule for identd for now. I use it sometime for irc and ftpclient ident. Some of the ftpd servers force a working ident for a connection.
-
Thare a thing call "adaptive IDENT stealthing". I dont know if that is possible to be implementing to the pfSense firewall. Thare´s article out theare about it.
