This object controls whether the router load-shares traffic on the interface per-packet across equal-cost paths or keeps each destination pinned to one path. The choice matters because perPacket(1) sharing can reorder packets within a TCP flow, hurting throughput for latency-sensitive traffic, while perDestination(2) preserves per-flow ordering at the cost of potentially uneven link utilization. An admin running two equal-cost WAN links for a VoIP-heavy branch would set this to perDestination(2) to avoid out-of-order RTP packets, even though one link might then carry 70% of the load and the other 30%.