You are correct, the public ip is local on our LAN port.
i did try that before, and have gone back to it
I think when I thought I switched them , I just switched one and then
switched it back. didnt look like settings took place till i reset
states. i waited for about 3 minutes, and didnt see a difference, so i
reset the states and now that ip is not transmitting any outbound
traffic but seemes to still pull inbound traffic now. wondering if some
arp poisoning is going on.
I did what i needed to do for the time being though. much appreciated.
-chris
On 9/22/2010 4:18 PM, David Burgess wrote:
On Wed, Sep 22, 2010 at 5:14 PM, Chris Flugstad<ch...@cascadelink.com> wrote:
wan rules
proto source port dest
port gw
block * 216.127.61.72 * *
* *
lan rules
block * * * 216.127.61.72
Although you weren't explicit, I got the impression that the host you
are trying to block is local to you. If so, then you need to reverse
your interfaces OR reverse the source/dest IP addresses.
If on the other hand 216.127.61.72 is an internet host that you're
trying to detach from your network, then your rules look good.
db
---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
