Uploading file and graphing into wrong interface
-
i'm routing a public ip block across the HONDUTEL interface and i'm uploading a file from a public IP in LAN, why the NAVEGA interface is graphing that traffic?
-
Make sure your rules route the traffic accordingly. The traffic may enter HONDUTEL but do you have rules on the inside interface that tell traffic sourced from your public IP block to go out the HOUNDTEL gateway?
-
Ok, there is no communication between the two WAN interfaces because they are different iSP, the only communication is going to come from the internet through the WAN Hondutel, the IP I'm using is a public IP routed through pfSense, I'm not doing NAT I am simply routed, and the next image show the rules that apply in that case. I'm using public IP, those IP can't be routed across NAVEGA.
-
If you use floating rules for WAN traffic, return traffic will go out via the default gateway. For WANs, use interface tab rules.
Also as I said, on your internal interface(s), anything initiated from a subnet belonging to a specific ISP should have its gateway forced to be that ISP.
-
I used floating rules because i have to limit the bandwith on wan and with a wan rule i don´t know why the pfsense not limited
-
Ok, I tried what you said and you're right, but I can not limit the bandwidth on the WAN interface rule, I only work with a floating rule, I must do something specific?
-
Nope - I can't offer better advice than jimp already offered.
-
If you are using the ALTQ shaper, use the "queue" action on floating rules, not pass, to queue the traffic.
If you are using limiters, those work fine on WAN rules and LAN rules, they do not require floating rules. If your traffic isn't being limited, then it isn't hitting the rule with the limiter set.
-
Jimp, could you read this post please? http://forum.pfsense.org/index.php/topic,64568.msg350101.html#msg350101
I found that if I set HONDUTEL as default gateway the limiter it works on the WAN, what can it be?
-
What is described here is a known bug in pfsense, provide more detail here: https://redmine.pfsense.org/issues/3096
