pfsense port forwarding/ WAN Default deny rule IPv4 (1000000103)
-
Hi guys I have a pfsense behind a modem and i try to do port forwarding for a remote machine i do all the nat port forwarding configuration but i can't access the machine and in the firewall log i see that the address is getting blocked by a default rule of ipv4 any help please!
-
@learn If this is local then you also have to enable pure-NAT NAT-reflection in that Port Forward.
-
@bob-dig yes im trying to open a port for remote machine in the lan
-
@learn Then show pictures of the rules, port forward and log.
-
-
@learn Picture of the firewall rule still missing.
-
@bob-dig sorry
-
@learn Looking good so far so problem must be somewhere else, specific to your environment.
-
@bob-dig said in pfsense port forwarding/ WAN Default deny rule IPv4 (1000000103):
specific to your environment.
suchh as ?
please help !
-
@learn so is default deny your seeing actually to the port your trying to forward? You just show a deny, you don't so that port udp or tcp even that is being blocked.
From your firewall rule showing 0/0 B tells me that rule has never been evaluated. So no traffic has hit your wan that would match your port forward and firewall rule.
-
@johnpoz im trying to do a remote access so im using tcp with a custom port instead of 3389
-
@learn again you rule not showing any hits.
Here I setup a rule for port 6060, never going to work because my 192.168.9.100 forwarding too not listening on that port
But notice when I try and go there (from can you see me . org), that after my rule shows it was evaluated, its no longer 0/0 B, but shows that it was used in the states table.
Your deny actually shows to your wan IP on the 6060 port your trying to access.. via TCP? You didn't show the full log, you just show "something" was denied..
-
@johnpoz i tried differnt ports even the deafult port and did a diagnostic test port
it shows the port is good but still not able to access -
@learn that is just a local test not remote..
Again - your rules is not showing any traffic actually hit it, that 0/0 B in the states column shows that pfsense saw no traffic to that port.
What was actually logged as blocked.. You just show a deny.. Here would be an actual block
Here is a log showing a block, see it is too my wan IP, I blocked out last 2 octets of my public IP.. But see there is the port is was going to, and that its TCP, and a SYN.
From your wan rule showing that 0/0 B shows that nothing has hit your public IP on that port to be forwarded. Or the numbers would change from 0/0 even if the port forward didn't actually work.
-
@johnpoz
here what t shows in my log -
@learn 3389 ain't 6060.
-
@bob-dig i changed to do port testing but none worked
-
@learn But it is important to test so test again towards 6060 and show the log and don't hide the beginning of those IPs!
-
@bob-dig did what you said it it the same result!
-
@learn does pfblockerng and openvpn can block portforwarding? im lost here
this what it shows in the logs
