SSH Login Attempts

[NogBadTheBad]

@ahking19 said in SSH Login Attempts:

n System | Advanced I did have "Enable Secure Shell" checked and also "Disable

"Does checking "Enable Secure Shell" allow outside ssh access?" No.

Do you have a firewall rule on your WAN enabling SSH, SSH inbound to the WAN interface would be blocked by default ?

Looks like brute force SSH to me.

https://www.abuseipdb.com/check/94.23.195.112

https://www.abuseipdb.com/check/185.113.240.93

[ahking19]

I don't currently have an active WAN firewall rule to allow inbound port 22.

I did have a rule that was port forwarding 22 to an SFTP server but that rule is disabled, although it exists. Haven't used the SFTP server in 10-12 months so I could delete the rule.

-Andrew

[johnpoz]

post up your wan rules.. NO turning on enable ssh does not auto create wan rule to allow traffic.

Do you have any floating rules?

[NogBadTheBad]

I used this on my Pi running FreeBSD if ever you need to block SSH brute force attacks:-

https://www.cyberciti.biz/faq/freebsd-openbsd-pf-stop-ftp-bruteforce-attacks/

[johnpoz]

pfsense has built in lockout of failed attempts

https://www.netgate.com/docs/pfsense/firewall/sshlockout.html

Sure there is a way to adjust the number of fails - but I do not think its in the gui anywhere.

[ahking19]

@johnpoz Here are the rules

[NogBadTheBad]

@ahking19

How about the floating rules ?

[johnpoz]

Dude your rule right there on top allows ANY Ip in that pfb_europe_v4 to anything... Why in the world would you have such a rule???

[ahking19]

@nogbadthebad

No floating rules

[johnpoz]

That first rule allows access to anything.. Coming from anything in that alias.. So no shit getting brute force on ssh, and your gui to as well.

Why do you think you need such a rule?

[NogBadTheBad]

@johnpoz said in SSH Login Attempts:

Dude your rule right there on top allows ANY Ip in that pfb_europe_v4 to anything... Why in the world would you have such a rule???

What John said, if you look in the firewall logs, you'll see it as its logging it.

[ahking19]

@johnpoz

Damn, was temp rule for team working in France. Updated rule to only allow OpenVPN.

[johnpoz]

That rule is pointless since you have a rule just below it that allows vpn any source. Unless you just want to log those from that alias?

[ahking19]

There is a block rule in between if NOT North America.

[NogBadTheBad]

@ahking19 said in SSH Login Attempts:

North America.

Wouldn't it be better to change the block rule in between if NOT North America to a pass North America, then the rule beneath block any OpenVPN and log?

[johnpoz]

True.. on the ! NA rule.

But you could for sure write those rules a bit more clear.. But without knowing EXACTLY what your wanting to do its just guessing, etc.

[ahking19]

@nogbadthebad

That would be fine for OpenVPN. But also don't need HTTP & HTTPS sites available outside North America. Not sure how/if I can combine pfBlocker rule with NAT rule. if that makes sense...

-Andrew

[johnpoz]

Sure you can if you just use its aliases - they can be used anywhere you want.. Rule, Nat, etc.

[ahking19]

Thanks. I'll take a look at using the pfBlocker aliases.