Can't Get It Working

[divsys]

Yes, the source address change is one of those "oh yeah, don't forget to change that too…" I remember when I'm  looking at the rule sheet - not while I'm typing  :(

Thanks for the catch  :)

-jfp

[bluegrass]

Ok, I'm able to access the internet through both LAN ports on my firewall HOWEVER, I can also access the web GUI on either port using either IP address. No matter which LAN port I'm on I can sign in to the GUI with 192.168.2.1 and 192.168.3.1

That shouldn't be happening, right?

[stephenw10]

That is the expected behaviour if you have 'allow any' rules on each LAN interface.

Steve

[bluegrass]

I tried changing the "allow any" rule to "allow WAN subnet to LAN1 subnet" but then I can't access anything over that port. I put back the allow any rule and it works but I can also access both ports from either again.

[divsys]

@bluegrass:

I tried changing the "allow any" rule to "allow WAN subnet to LAN1 subnet" but then I can't access anything over that port. I put back the allow any rule and it works but I can also access both ports from either again.

If you're just trying to stop LAN from seeing OPT1 (and vice versa), you can add a LAN1 rule:

"Allow LAN to NOT OPT1 subnet"

And similarly on OPT1

"Allow OPT1 to NOT LAN"

Depends on what you're trying to acheive

[stephenw10]

Yep. Or you can explicitly block access to the OPT1 interface address from the LAN subnet with a block rule placed above the 'allow any' rule. Then you can still access devices on OPT1 from LAN.

[bluegrass]

I'm not sure if I'm doing this right so here's a screen cap of what I did. There was no change.

[johnpoz]

So you want to BLOCK going anywhere but that lan segment?  That is what that rule would do.

Post your lan rules so we can see exactly what other rules you have in place, etc.  That rule by itself would block everything but the lan segment.  So you would not be able to go to the internet..  Is that what your after?

[Guest]

Enter firewall block rules on the "LAN" or "OPT1" for port 80 and 443 from "LAN" or "OPT1" to "IP of ROUTER", then nobody can reach the interface from this LAN / OPT1

[stephenw10]

Hmm, that rule is definitely wrong. It will never (or should never) match any traffic as you will never see any packets going into the LAN interface that have source 'SERVER subnet'.

What exactly are you trying to achieve?

Steve

[johnpoz]

I didn't even catch the server source ;)  Yeah that would never even trigger.

[bluegrass]

What I'm trying to do is keep the SERVER and LAN ports from being able to communicate with each other.

I don't want anyone on my home network to accidently get access to my little web server and screw something up. And I don't want any traffic for the server getting onto my home network.

[bluegrass]

Ok I think I got it fixed. I looked in the 'Definitive Guide to PFSense' and it said: "Rules in PFSense are applied on a per-interface basis, always in the inbound direction on that interface. This means traffic initiated from the LAN is filtered using the LAN interface rules.Traffic initiated from the Internet is filtered with the WAN interface rules."

So I changed the source on Server TO server and source on LAN to LAN and now the two ports don't appear to be able to access each other.

[stephenw10]

Sounds good.
If you're in any doubt post up some screen shots of your rules.  :)

Steve

[bluegrass]

Ok, here's the rules for my LAN and SERVER ports.


[stephenw10]

Looks good, that should block all IPv4 traffic between the LAN and SERVER subnets.  :)
It won't block IPv6 traffic if you are using IPv6 at all. Change the TCP/IP version to 'any' if you want to block v6 too.

Steve

[bluegrass]

Thanks for all the help.