Need help using traffic shaping to created severely degraded SSH
-
You posted a screenshot of a firewall rule with 2222.
-
You posted a screenshot of a firewall rule with 2222.
Yes. The NAT rule (also posted above and attached here) is what opens up the WAN port number 22. The Firewall rule is what opens up the redirected LAN port number 2222.
Without the limits in place, everything works.
-
The hacker connects to the standard SSH port (22)
-
The NAT forwarding rule redirects the traffic to my honeypot server at 192.168.0.202 on port 2222.
-
The firewall rule sees traffic destined for 192.168.0.202, port 2222, and passes the traffic, logging it to the firewall log.
I dont understand your reason to open SSH on your WAN. Just keep it closed.
Because that's the standard SSH port that hackers try access. I want them to connect and waste their time trying to log on. If I put the server at 2222, then they won't find it. They will come in on the SSH port (22), get rejected or blocked, and never reach the honeypot.
From a how-to on kippo, the SSH honeypot:
"Now kippo uses port 2222 to run its honeypot on, in order to send evil hackers to that port you need to use your home router (which hopefully can do port forwarding) to send all traffic for port 22 to 2222. I’m not going to explain how to do this because everyone’s router is different. So go ahead and configure that port forwarding ready for when we start kippo."
 -
-
Post a screen of your WAN rules.
-
Post a screen of your WAN rules.
I've enclosed them here. Thanks.
{Removed screenshot of rules. The person who made the request for the rules did not do so in order to answer my question.}
-
Why not install the package pfBlockerNG and limit which IPs can access the open ssh port plus block known malicious IPs.
https://forum.pfsense.org/index.php?topic=86212.0
-
Don't open the port at all.
Remove the bullshit rules. Your firewall blocks traffic not listed by default.
-
Don't open the port at all.
Remove the {expletive} rules. Your firewall blocks traffic not listed by default.
I'm not soliciting opinions on my tarpitting project. I asked for assistance getting traffic shaping limits working. If you don't know how to do that, then say so. I will thank you for trying and will wait for someone who does know how.
My purpose is not to block or reject traffic. It is to tarpit systems mounting brute force dictionary SSH attacks.
-
Why not install the package pfBlockerNG and limit which IPs can access the open ssh port plus block known malicious IPs.
I have pfBlockerNG installed and use it extensively.
But using it to block SSH won't provide me with evidence to use in reporting those making SSH brute force attacks. I won't be able to analyze the malicious payloads they deliver to determine what they do and with what systems they communicate. I won't be able to study the ACL changes they try to make.
I just got about half a dozen such attackers shut down by Amazon Web Services using evidence gathered by the SSH honeypot, but I don't wish to continue to have my log files filling up at such a high rate and so much of my bandwidth being used in the process.
-
You are probably hitting this: https://redmine.pfsense.org/issues/4326
Set the limiter on the LAN side or try a 2.2.3 snapshot where I believe a patch has now gone in: https://redmine.pfsense.org/issues/4596Steve
-
You are probably hitting this: https://redmine.pfsense.org/issues/4326
Set the limiter on the LAN side or try a 2.2.3 snapshot where I believe a patch has now gone in: https://redmine.pfsense.org/issues/4596Steve
Steve,
Thank you! A quick scan of that bug looks like it's a good bet as to the source of the problem. I've been pulling my hair out trying to figure out what's wrong. Everything's working and then I insert the two limit queues into the firewall rule and everything just stops.
Regards,
Fred
