Project

General

Profile

Actions

Regression #12187

closed

Outbound LAN rule no longer working

Added by Arnold Fredson over 4 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Rules / NAT
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.5.2
Affected Architecture:
All

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

Actions

Also available in: Atom PDF