pfSense

hello all,
We find a problem on pfsense Nanobsd 2.3.2
Hardware : Motherboard ALIX

we have 2 Wan interface with MPLS Configuration and both WAN have same Gateway.

WAN_ADSL_1(PPPoE0) 10.105.0.10 GW 10.105.0.1 ( default link)
WAN_SDSL_2(PPPoE1) : 10.105.0.11 GW 10.105.0.1

I want add static route "192.168.250.0/24" in order to route all trafic in WAN_SDSL_2(PPPoE1)

When we add static route in web interface Pfsense accept but when we check in diagnostic route menue we have

Internet:
Destination Gateway Flags Netif Expire
default 10.105.0.1 UGS pppoe0
10.105.0.1 link#8 UH pppoe0
10.105.0.10 link#9 UHS lo0
10.105.0.11 link#8 UHS lo0
94.143.87.198/32 10.105.0.1 UGS pppoe0
94.247.160.53/32 10.105.0.1 UGS pppoe0
127.0.0.1 link#7 UH lo0
185.117.37.2/32 10.105.0.1 UGS pppoe0
192.168.3.0/24 link#3 U vr2
192.168.3.5 link#3 UHS lo0
192.168.250.0/24 10.105.0.1 UGS pppoe0

The static route is not routing on good interface. Normaly with my rule 192.168.250.0/24 to pppoe1
Also there is a problem...

We go to CLI for check the configuration :

/root: netstat -nrf inet

Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 10.105.0.1 UGS pppoe0
10.105.0.1 link#8 UH pppoe0
10.105.0.10 link#9 UHS lo0
10.105.0.11 link#8 UHS lo0
94.143.87.198/32 10.105.0.1 UGS pppoe0
94.247.160.53/32 10.105.0.1 UGS pppoe0
127.0.0.1 link#7 UH lo0
185.117.37.2/32 10.105.0.1 UGS pppoe0
192.168.3.0/24 link#3 U vr2
192.168.3.5 link#3 UHS lo0
192.168.250.0/24 10.105.0.1 UGS pppoe0
192.168.251.0/24 10.105.0.1 UGS pppoe0
192.168.252.0/24 10.105.0.1 UGS pppoe0
192.168.253.0/24 10.105.0.1 UGS pppoe0
192.168.254.0/24 link#3 U vr2
192.168.254.254 link#3 UHS lo0

It is the same problem :

192.168.250.0/24 10.105.0.1 UGS pppoe0

Whereas we want this :
192.168.250.0/24 10.105.0.1 UGS pppoe1 !!!!!!

Other information :

root: route -n show 192.168.250/24
route to: 192.168.250.0
destination: 192.168.250.0
mask: 255.255.255.0
gateway: 10.105.0.1
fib: 0 * interface: pppoe0*
flags: <UP,GATEWAY,DONE,STATIC>
recvpipe sendpipe ssthresh rtt,msec mtu weight expire
0 0 0 0 1492 1 0

It's same problem whereas we add static route : 192.168.250.0/24 to pppoe1

For solve this problem I had static route in hard in CLI with :

route add $destination $passerelle -ifp $interface

/root: route add 192.168.250.0/24 10.105.0.1 -ifp pppoe1

test for checking :

/root: netstat -nrf inet
Routing tables

Internet:
Destination Gateway Flags Netif Expire
default 10.105.0.1 UGS pppoe0
10.105.0.1 link#8 UH pppoe0
10.105.0.10 link#9 UHS lo0
10.105.0.11 link#8 UHS lo0
94.143.87.198/32 10.105.0.1 UGS pppoe0
94.247.160.53/32 10.105.0.1 UGS pppoe0
127.0.0.1 link#7 UH lo0
185.117.37.2/32 10.105.0.1 UGS pppoe0
192.168.3.0/24 link#3 U vr2
192.168.3.5 link#3 UHS lo0
192.168.250.0/24 10.105.0.1 UGS pppoe1
192.168.251.0/24 10.105.0.1 UGS pppoe0
192.168.252.0/24 10.105.0.1 UGS pppoe0
192.168.253.0/24 10.105.0.1 UGS pppoe0
192.168.254.0/24 link#3 U vr2
192.168.254.254 link#3 UHS lo0

we have : 192.168.250.0/24 10.105.0.1 UGS pppoe1

I think that when you add static route in pfsense, the system match on gateway of interface and not interface
If both interface have a same gateway, pfense route trafic on défault link also it's not good direction.

when we had static route in CLi we add interface information " -ifp $interface "

---> route add $destination $passerelle -ifp $interface

its best solution but not good for web interface

Can you find a solution ?

thanks