I went ahead and added the rule to both WAN interfaces (even though I was only targeting the DSL interface) and now its working, which makes no sense, but it does. Thanks for your help!
The only change it makes to the packets is rewriting the destination port, it's not possible for it to be mangled in a means that does anything to the protocol within (if anything it changes were broken, you would never get a connection via telnet as it would break the most basic of TCP communications). Those aren't exactly easy protocols to troubleshoot via packet capture since they aren't nicely decipherable like HTTP, SMTP, others, but that's worth a shot.
Hand meet head. The WAN default subnet was 32. Switched it to 24, life is pure again. Thanks for the help, will attempt to not overlook the basics in the future. And drink more coffee…
The floating tab is not only for shaper but a way to define more generic rules.
From teh shaper context that means you can aggregate shaper rules if you do complex stuff.
Thank you a feature request has now been submitted.. Though I was hoping that someone on this forum would have said the feature was already there and I just wasn't using it correctly. :)
Thanks all for such an amazing product. pfSense rocks!!!!
I figured out how to get QoS going on the router and things seem to have improved. I will monitor the situation and update this ticket if problems continue. Thanks to everyone for their help!
edanpedragosa, make sure you read the sticky about how to upgrade to the latest snapshot. It takes some manual intervention. If you are still on the July 4 snap, then you are running into that problem.
I just went into similar problem:
"TLS Error: local/remote TLS keys are out of sync: "
version: 2.0-RC3 (i386) built on Mon Jul 4 16:48:37 EDT 2011
using OpenVPN + Remote Access (user auth) + UDP tun
I used that before, so issue seems to be related to latest snapshot.
This sometimes causes client disconnection.