@GRL 

good question, you actually route 192.168.100.99 out on two interfaces, I think it can be a bit random where 192.168.100.99 is routed. have you tested that setup?

  @GRL 

No, i havent tested yet.

I will wait until tomorrow morning to test it whan im a) on site in case things go weird and b) nobody is using the network

My other alternative is to put the device on a subnet naturally routed to WAN 1 but then i have to reprogram 50 end computers to access it over a different IP. which will be annoying.

Im actually surprised as i canot find any documentation that reflects my question, even the official TPlink guides make no mention of routing an individual IP differently from its range.

EDIT: i have just noticed that the policy routing rules are rearrangeable by dragging, like you can to organise the precedence of ACL rules....so....maybe ?

  @GRL 

yes, that was an interesting question. I'm excited for the answer :-) you have to update the thread when you have the facts :-)

Hi @GRL 

Thanks for posting in our business forum.

GRL wrote

 

By that i mean, if i have policy routes like so....

 

rule 1:  192.168.100.99 /32 > WAN 1

rule 2:  192.168.100.0 / 24 > WAN 2

 

will rule 1 take precedence over rule 2, so that one particular IP goes to WAN 1 and the entire rest of the subnet goes to WAN 2 ?

The system weighs priority by number. If a rule gets a smaller number, then it means higher priority, I think this setup should work as your expectation.