# \[Feature Request\] Select specific WAN for Client **URL:** \ **Category:** Router\ **Created:** [October 1, 2026, 2:21am UTC](https://forum.gl-inet.com/t/feature-request-select-specific-wan-for-client/71707 "2026-10-01T02:21:21Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![charles2](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/c/9dc877/32.png) [@charles2](https://forum.gl-inet.com/u/charles2)\ **Post date:** [October 9, 2026, 6:23am UTC](https://forum.gl-inet.com/t/feature-request-select-specific-wan-for-client/71707/4 "2026-10-09T06:23:44Z")
Hi, Thank you for sharing your suggestion and use case. We have recorded your feature request and submitted it to the relevant team for further discussion and evaluation. However, you can try using source-based policy routing (`ip rule` ) to direct specific clients through a preferred WAN while keeping Multi-WAN in Failover mode. You may refer to: > [@Source based Multi-WAN Routing](https://forum.gl-inet.com/t/source-based-multi-wan-routing/63988/3): > > Hi Yes, right. Load balancing does not make much sense in your scenario. The session will be randomly assigned to either ISP1 or ISP2 until disconnected. This can be achieved using ip rule in failover mode. Please SSH into the router and run the following commands: # 192.168.8.201/32 is the address/subnet for devices using ETH2 # Traffic originating from this address/subnet should be matched using route table 100 with priority 10. ip rule add from 192.168.8.201 table 100 prio 10 # Add a … Please note that this is a manual workaround, and the configuration may need to be adjusted for your router and network setup. Thank you for your feedback and support. --- _[View the full topic](https://forum.gl-inet.com/t/feature-request-select-specific-wan-for-client/71707)._