<![CDATA[pfsense blocking access from other routers clients]]>10.0.0.254 says The rule that triggered this action is: @57(12000) block drop in log quick on nfe0 inet from 10.0.0.0/8 to any label "Block private networks from WAN block 10/8"

I'm trying to access Emby Media Server which is behind pfsense router from a different router's LAN.
The server is hosted at 10.0.0.240:8096 on pfsense LAN, I have no problem accessing it from pfsense LAN, but when i try it from different router's LAN i get the above mentioned message in firewall log,
both Pfsense and Mikrotik are connected to same DSL router. I tried NAT port forward, Pure NAT, NAT Reflection, blindly just test and try without knowing what i was exactly doing.
I am most confused in the part, that I was able to create a Rule to forward RDP request over Internet and successfully connected with Remote Desktop Client which was on pfsense LAN. It didn't complained me then.
Now when I'm trying to connect inside from my own house and it's blocking :-) ( I know pfsense has no idea i'm in home)
I would be obligated if some one could show me the proper way and path on how to achieve it.
Attached is worse Network Diagram by a Worst network engineer.network-diagram.jpg

]]>https://forum.netgate.com/topic/142149/pfsense-blocking-access-from-other-routers-clientsRSS for NodeWed, 15 Jul 2026 06:58:58 GMTMon, 01 Apr 2019 22:59:46 GMT60<![CDATA[Reply to pfsense blocking access from other routers clients on Tue, 02 Apr 2019 12:42:13 GMT]]>@Grimson said

RTFM: https://docs.netgate.com/pfsense/en/latest/interfaces/interface-settings.html#private-networks

Thankyou Grimson, after Reading The Fine Manual.
I concluded that
since the WAN IF of pfSense router actually does not have a public IP and has a IP Address 192.168.1.253
RFC1-918, I think it is secure from outside attack over internet even after turning off the block Private IP Address and loop back address and this is the proper way to configure and it's not a work around. Please correct me if i'm wrong.
WAN-IF.JPG
RFC-1918.JPG
Thanks

]]>https://forum.netgate.com/post/834565https://forum.netgate.com/post/834565Tue, 02 Apr 2019 12:42:13 GMT<![CDATA[Reply to pfsense blocking access from other routers clients on Tue, 02 Apr 2019 11:14:45 GMT]]>@whitekalu said in pfsense blocking access from other routers clients:

Is this a workaround, Temporary Solution or this is the only way how it's done.
even though it's working I think something weird about turning off the Block Private network on WAN IF

RTFM: https://docs.netgate.com/pfsense/en/latest/interfaces/interface-settings.html#private-networks

]]>https://forum.netgate.com/post/834545https://forum.netgate.com/post/834545Tue, 02 Apr 2019 11:14:45 GMT<![CDATA[Reply to pfsense blocking access from other routers clients on Tue, 02 Apr 2019 11:04:14 GMT]]>Can anybody please throw some light.
Is this a workaround, Temporary Solution or this is the only way how it's done.
even though it's working I think something weird about turning off the Block Private network on WAN IF
Thanks

]]>https://forum.netgate.com/post/834544https://forum.netgate.com/post/834544Tue, 02 Apr 2019 11:04:14 GMT<![CDATA[Reply to pfsense blocking access from other routers clients on Tue, 02 Apr 2019 00:58:56 GMT]]>@jahonix Thankyou so much it's working now.
One curious question.
while troubleshooting windows machine I used to turn off the firewall and boom everything used to work.
will Unchecking that thing on WAN Interface some how loosen/weaken the firewall security ?
I hope it's not like turning off the windows firewall to make something work. Just Curious, It's working though.
Thanks

]]>https://forum.netgate.com/post/834473https://forum.netgate.com/post/834473Tue, 02 Apr 2019 00:58:56 GMT<![CDATA[Reply to pfsense blocking access from other routers clients on Mon, 01 Apr 2019 23:52:49 GMT]]>@whitekalu said in pfsense blocking access from other routers clients:

I know pfsense has no idea i'm in home

Actually it does. Packets do not come from your gateway but other addresses of a private IP range.
At Interfaces | Wan uncheck "Block private networks and loopback addresses" and you should be good to go.

]]>https://forum.netgate.com/post/834464https://forum.netgate.com/post/834464Mon, 01 Apr 2019 23:52:49 GMT