Bug #3929
closed
Port Forwarding with an association Filter
0%
Description
Hello,
using Port Forwarding with an association Filter rule isnt working.
I have a WAN (em2) and a LAN (em0). I want to forward all traffic on Port 20514 to LAN device on port 514.
Please have a look at my configuration (screenshot1), its all correct but did not work.
The Firewall block traffic, here is the output from log:
00:00:00.473798 rule 48/0(match): block in on em2: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 59)
192.168.178.253.57284 > 192.168.0.15.514: SYSLOG, length: 31
Facility user (1), Severity notice (5)
Msg: Sep 29 19:12:32 root: test\0x0a
Files
Updated by Chris Buechler almost 11 years ago
- Status changed from New to Rejected
not a bug, please use one of our available support resources for assistance. https://pfsense.org/support
Updated by Florian Asche almost 11 years ago
Hi,
how could this be not a bug?
I set all things by documentation.
Have a look at https://doc.pfsense.org/index.php/How_can_I_forward_ports_with_pfSense.
Filter rule association - this allows you to add an associated filter rule, which gets updated when the port forward is updated, or add an unassociated filter rule (the behavior of 1.2.3), or "pass" which passes all traffic that matches the entry without having a firewall rule at all.
Updated by Chris Buechler almost 11 years ago
Because you have something misconfigured. There isn't anything wrong with port forwards or associated rules.
Updated by Florian Asche almost 11 years ago
i completly reinstalled pfsense, with default configuration.
then i configured the port forwarding.
are u sure, that there is no problem?
Updated by Chris Buechler almost 11 years ago
Of course. Nothing that simple is broken. Block private networks is my guess. This isn't the place to discuss, please use one of our support resources.