I have been preparing to shift my network to a new bigger subnet. I have routing set up between old 192.168.2.* and new 10.10.*.* subnet. I have been evaluating pfsense for a while. Its routing of local LAN to LAN subnets is not reliable.
At times it was great, but I feel that having traffic shaping on tends to affect it, yet there were times when transfers to a samba server in the old subnet from the new subnet, via pfsense routing performed as one would hope. I have 4 intel gigbit NICs installed - all are fine. In the last weeks, inexplicably I can't make a transfer work without a drop-out - if it is routed through pfsense like this. I just updated firmware (I am a disk based system) to 1.2 release - which seems ok so far. The problem hasn't changed. Are there any rules I can do to make the traffic shaper ignore LAN to LAN subnet traffic - assuming it is the culprit. Once we rollout the new subnet and have all our servers moved there, we will still have alias IPs in the old subnet. That will help in the transition and people will still be able to get to their favourite old addresses in the LAN until we can deal with them. So having stable routing is really important. I feel I have done my best to make sure this isn't something I can figure out. I have been watching the support and trying to help people but I don't notice this topic come up much. I feel that pfsense routing is fairly useless if there is no work around, which is a shame because otherwise it beats the other firewalls I evaluated. thanks for your help Sangye
