Is it possible for one to "slip through"?

[johnpoz]

@obxjeepguy said in Is it possible for one to "slip through"?:

that ip address shouldn't even be able to get that far the way it is set up.

But from what you posted I can not really tell if that is outbound connection attempt from inside your network, or a connection attempt from outside pfsense that is forwarded in?

[stephenw10]

Yes, more info needed.

I had assumed that you are forwarding traffic to the BlueIris server and have pfBlocker adding rules to filter that?
If you are using pfBlocker to automatically add rules make sure it's adding rules where you expect and in the right order.
Make sure the alias pfBlocker creates actually contains that subnet.

Steve

[OBXJeepGuy]

Okay, hopefully this explains it better. I have been running this firewall for about a year now with great success. Once I block a range, I never see another attempt. This particular one is the first time I have seen something like this happen.

[stephenw10]

But how are you applying that block? What is it blocking, traffic from a port forward to the server?

[OBXJeepGuy]

@stephenw10 I am blocking that IP range from anything on my LAN.

[johnpoz]

@obxjeepguy where is the rule?? On your lan? In floating, on your Wan?

What are the order of the rules? etc.. For all we know that was the device your showing the 205.x address in trying to make a connection and it didn't work, etc..

[stephenw10]

From connecting to anything on your LAN?

Yeah, we need to see the rule and where it's applied really. There are many ways to apply that incorrectly.

[OBXJeepGuy]

I am guessing this is what you are looking for.

[stephenw10]

Those all look like the included list names. Is your custom block list added to one of those?

Or, what 'list action' do you have set on your custom list?

[OBXJeepGuy]

@stephenw10 The custom block list is within pfB_PRI1_v4.

[stephenw10]

Ok, so that would block connections from that subnet inbound on WAN. And since it's a floating rule it would do so before and pass rules you might have on the WAN tab. You haven't explicitly confirmed it but I assume you have a port forward to the server on WAN with linked firewall rules there?

[OBXJeepGuy]

@stephenw10 said in Is it possible for one to "slip through"?:

Ok, so that would block connections from that subnet inbound on WAN. And since it's a floating rule it would do so before and pass rules you might have on the WAN tab. You haven't explicitly confirmed it but I assume you have a port forward to the server on WAN with linked firewall rules there?

Yes, I do have a port forward going to the server. I should have included that. I’ll post an image as soon as I get back to a PC.

[OBXJeepGuy]

Okay. There it is. Been quite busy at work.

[OBXJeepGuy]

@stephenw10 Now that I look at it, something seems off. I'm not quite sure.

[johnpoz]

@obxjeepguy yeah that is not a port forward, that is a allow rule outbound to some 192.168 address, why would you think you need to hide a rfc1918 address.

[stephenw10]

Yes, very unlikely that rule would ever match anything. You can see no states have been opened by it. I would just disable that.

You can see the port forward in Firewall > NAT > Port Forwards.

The associated firewall rule will be on the WAN tab.

Steve

[OBXJeepGuy]

@johnpoz said in Is it possible for one to "slip through"?:

@obxjeepguy yeah that is not a port forward, that is a allow rule outbound to some 192.168 address, why would you think you need to hide a rfc1918 address.

You are absolutely correct. And I have disabled it. That is left over from when I fist set everything up, and knew ZERO about pfSense. As for hiding an rfc1918 address, that would be for no apparent reason. Just like the folks who cover their license plates in photos of their cars.

[johnpoz]

@obxjeepguy said in Is it possible for one to "slip through"?:

Just like the folks who cover their license plates in photos of their cars.

No not the same - lic number is unique and could be looked up ;)

Rfc1918 space used by everyone.. It would be like telling you I live on the planet earth ;) could you find me with that info hehehe

My pc is 192.168.9.100, my gateway is 192.168.9.253 - does that give you any info at all that could be used to track me to where I am exactly, or even what ISP I use, etc.

edit: but knowing what address space is being used can be very helpful in troubleshooting so that easier to understand difference in vlans and why some rfc1918 IP can not talk to another one, etc. When they are obfuscated it can be more difficult understanding quickly what is going on.. While hiding your public IP space is very understandable - when you hide rfc1918 it can get confusing is all. Just something to consider in future posts is all.

[OBXJeepGuy]

@johnpoz said in Is it possible for one to "slip through"?:

@obxjeepguy said in Is it possible for one to "slip through"?:

Just like the folks who cover their license plates in photos of their cars.

No not the same - lic number is unique and could be looked up ;)

Rfc1918 space used by everyone.. It would be like telling you I live on the planet earth ;) could you find me with that info hehehe

My pc is 192.168.9.100, my gateway is 192.168.9.253 - does that give you any info at all that could be used to track me to where I am exactly, or even what ISP I use, etc.

All very true. I was always told to not even let any of those numbers out. Especially port numbers. I know the only way is if I knew your public IP address. So that being said, I will get on with port forwarding, and @stephenw10 will see there is a linked rule.

[johnpoz]

@obxjeepguy I not sure who told you to hide those or ports.. But they don't work in networking that is for sure.

Me knowing your forwarding to 80 or 443 provides me nothing if I don't know what your public wan IP is. Like saying hay your house number is 123.. What city, what street ;) if I do not know these things 123 is meaningless and provides nothing to track you. But it can be very helpful in spotting problems. Hey that should be 443, not 444 etc.

For example I forward externally port 23040 to my plex on 32400. Without even a clue to what my public IP is - how does that give away anything?