PfSense not blocking attacker (FIXED)

staroflaw · Oct 7, 2014, 5:46 PM

Hi

I am running v2.1.5
I have had some problems with an attacker. They keep running a Denial-of-service attack against my web server.
I installed pfBlocker and configured it like the documents say. Added the IP address in the List CIDR 80.82.XX.XXX but still the attack continues.

I have had a look under Rules/WAN > BLOCK ANY from WAN alias. All setup fine.

I have blocked him at the web server for the moment. but it is filling my web server logs up.
Would love some help to stop this attacker.

Thanks

Star.

jasonlitka · Oct 7, 2014, 6:30 PM

We're going to need some pictures.

KOM · Oct 7, 2014, 6:31 PM

You have no control over traffic hitting your WAN interface, and a firewall will not stop a DDoS. It's not a magic bullet. If it could stop DDoS, then DDoS wouldn't be a problem for anyone anymore. Just have your firewall drop their packets as you've already done. If your interface is overwhelmed by the traffic then there isn't much you can do about it. As for your web server logs, that's a question for an Apache/nginx forum.

staroflaw · Oct 7, 2014, 6:53 PM

Just have your firewall drop their packets as you've already done.

That's the problem, it is not dropping the packets! There traffic is still entering the WAN interface to the LAN > Webserver. despite adding the RULE.

and a firewall will not stop a DDoS

That's why I am trying to block the IP address the traffic is coming from.

Thanks

Star.

KOM · Oct 7, 2014, 7:27 PM

I thought you were trying to block them from hitting the WAN, which isn't possible. The problem with using a country list is that the list is not perfect, and if it is really a DDoS then it's very likely that you will be hit by IP addresses from all over the world. You could stick with pfblocker and also add an alias for IP addresses not being blocked, and block that alias too.

staroflaw · Oct 7, 2014, 7:58 PM

Ok, As a test I have blocked my friends IP address.

This is my settings. Under Rules > WAN I added this.

But he can still access the web/FTP/Comms server's. What am I doing wrong?

cmb · Oct 7, 2014, 8:10 PM

Probably wrong rule order, block must come above any pass rules that'd match.

staroflaw · Oct 7, 2014, 8:21 PM

Should it not work here? its Block Test

Thanks

star.

cmb · Oct 7, 2014, 8:36 PM

Assuming traffic is coming in on WAN, and you have no interface groups or floating rules, yes. There is no rule allowing web access on WAN, so guessing that must be coming in via a VPN or some other Internet connection.

staroflaw · Oct 7, 2014, 8:54 PM

Yes traffic is coming in on WAN

Floating > No floating rules are currently defined.
WAN >

Torguard / PPTP VPN / OpenVPN > are all now disabled.

Still its not blocking my mates IP. I just don't get it.

If you wanted to block a IP from entering what would you do?

Star.

kejianshi · Oct 7, 2014, 9:08 PM

If the traffic is coming in through the WAN:

1. You are allowing it, perhaps inadvertently

or

2. The connection was established before you made the rule to block it and you never rebooted pfsense.

Or perhaps you are running uPNP on something on your lan that is forwarding ports?

staroflaw · Oct 8, 2014, 10:31 AM

If the traffic is coming in through the WAN:

1. You are allowing it, perhaps inadvertently

Not sure were else to look.

2. The connection was established before you made the rule to block it and you never rebooted pfsense.

I have rebooted after every change made.

Or perhaps you are running uPNP on something on your lan that is forwarding ports?

I have removed all other devices from the network, so I only have.
Modem -> pfsense box -> Server box. Nothing else is on the network.

Still able to gain access through firewall to server.

Your avatar says it all! lol

Star.

kejianshi · Oct 8, 2014, 10:51 AM

1. Are you accessing the "WAN" from inside or outside your network to test blocking? (I have to ask)

2. Have you put a "pass" rule on the WAN as if its a LAN? floating rule? (Gotta ask)

I see you answered that before… Sigh.

Makes me wonder if the IP accessing your WAN and the IP you put on your firewall block rule are in fact the same IP.

staroflaw · Oct 8, 2014, 11:10 AM

This is what I have in my webserver logs.

80.82.78.166 - - [08/Oct/2014:12:02:52 +0100] "POST /xmlrpc.php HTTP/1.0" 403 1122 "-" "Mozilla/4.0 (compatible: MSIE 7.0; Windows NT 6.0)"
This IP is making 6 requests a second.

Here is the Rule I added on the WAN

Is this correct? Am I missing something?

Thanks

Star.

kejianshi · Oct 8, 2014, 11:21 AM

This should make no difference, however, under "destination" put WAN address, then try.

staroflaw · Oct 8, 2014, 11:40 AM

No it made no difference at all.
I even added a Rule to Block everything coming in >

Still able to access my services from outside of my network.

Star.

kejianshi · Oct 8, 2014, 11:42 AM

Do you have multiple WANs?

See, you don't have to add "Block all" rules on the WAN. Dropping inbound unsolicited packets is the default unless you allow them.

So, is there another way into your network?

staroflaw · Oct 8, 2014, 11:49 AM

No. only 1 WAN.
The Block ALL was just a test.

The only other way in was openVPN and PPTP. But I disabled them both.

Thanks for your help btw. I do appreciate it.

Star.

kejianshi · Oct 8, 2014, 12:03 PM

I don't know.

My feeling is that pfsense isn't the problem because simple allow/block rules work fine usually.

In situations like this, I normally go with a wipe and reinstall.

Also. Has anyone added firewalls directly to packet filter in the command line of pfsense?

charliem · Oct 8, 2014, 3:51 PM

Can you check that your rules are showing up in /tmp/rules.debug, especially that Torguard / OpenVPN / PPTP VPN really are disabled?

Anything look strange in that file?