Regression #12187
closedOutbound LAN rule no longer working
0%
Description
I just realized that after a 2.5.2 upgrade a rule I had in place no longer works.
- I have Dual ISPS
- I have high bandwidth HD video cameras that continually record and upload to a cloud service. I want a single ISP to transfer all this data leaving other clear for regular office use.
- I have given all these devices a static IP and have listed them in Firewall/Alias
- The in Firewall/Rules, then LAN I have created a rule that applies to the aforementioned Alias group.
- Scrolling down, I have set the desired Gateway to be used.
This rule worked for a long time, but just stopped working after 2.52 upgrade.
Troubleshooting Notes.
- I've removed the rule and the aliases and readded them
- I added my laptop IP to the alias
- When running a trace from the laptop, I can see that it uses the desired gateway, however when I start doing bandwidth-intensive things, and I run another traceroute, I notice that the traffic then goes out the wrong gateway.
- The rule starts to work after I clear the states or reboot the firewall but fails again once some traffic starts to move through it.
I discovered it when I checked the traffic totals for the month and the desired gateway had about 1/10th of the total traffic than is normal for it.
Thank you
Updated by Jim Pingle almost 4 years ago
- Project changed from pfSense Packages to pfSense
- Category changed from FRR to Rules / NAT
- Status changed from New to Rejected
- Release Notes set to Default
Not enough information here to classify it as a bug. Post on the forum and include specific details such as the entire configuration of that rule, other outbound NAT rules and settings, firewall rules that traffic hits, etc.