Platform RUTXR1 fw version RUTX_R_00.07.03.
We have a hub and spoke topology network with the RUTXR1 acting as spokes. They are interconnected with the hub through a GRE-tunnel. From the hub we advertise a default route through the GRE-tunnel towards the spokes. The default route is received on the spokes but not installed in the routing table. We see that the BGP process installs BGP advertised routes with a metric of 20 as we advertise by means of test also the network 10.0.0.0/8 that is installed in the routing table.
The RUTXR1 is connected to a mobile datanetwork through the MOB1S1A1-interface (wwan0). Once it is connected the RUTXR1 automatically installs a default route with metric 4 that I manually raised to 254. Although this route is now configured with a metric of 254 and the BGP-received default route should be installed with an expected metric of 20 we see that the latter default route is not installed in the routing table and the router still takes the automatically installed default one.
Any idea how this can be corrected? In my opinion the RTUXR1 firmware has no sense of administrative distance, so metric is the only parameter to play with.
route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 254 0 0 wwan0
10.0.0.0 192.168.0.1 255.0.0.0 UG 20 0 0 gre4-Tunnel0
10.168.130.16 0.0.0.0 255.255.255.240 U 2 0 0 wwan0
10.168.130.18 0.0.0.0 255.255.255.255 UH 2 0 0 wwan0
10.168.132.192 0.0.0.0 255.255.255.224 U 1 0 0 eth0.15
10.168.144.16 0.0.0.0 255.255.255.240 U 1 0 0 eth0.5
10.168.146.16 0.0.0.0 255.255.255.252 U 1 0 0 eth0.3
10.168.148.32 0.0.0.0 255.255.255.248 U 1 0 0 eth0.4
10.168.158.23 0.0.0.0 255.255.255.255 UH 254 0 0 wwan0
172.16.0.0 0.0.0.0 255.255.255.240 U 1 0 0 eth0.6
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 gre4-Tunnel0
----------------------
sh ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP,
F - PBR,
> - selected route, * - FIB route
B 0.0.0.0/0 [200/0] via 192.168.0.1, gre4-Tunnel0, 00:15:38
K>* 0.0.0.0/0 [0/254] is directly connected, wwan0, 00:15:38
B>* 10.0.0.0/8 [200/0] via 192.168.0.1, gre4-Tunnel0, 00:15:38
K>* 10.168.130.16/28 [0/2] is directly connected, wwan0, 00:15:38
K>* 10.168.130.18/32 [0/2] is directly connected, wwan0, 00:15:38
K * 10.168.132.192/27 [0/1] is directly connected, eth0.15, 02:00:50
C>* 10.168.132.192/27 is directly connected, eth0.15, 02:00:50
K * 10.168.144.16/28 [0/1] is directly connected, eth0.5, 02:00:50
C>* 10.168.144.16/28 is directly connected, eth0.5, 02:00:50
K * 10.168.146.16/30 [0/1] is directly connected, eth0.3, 02:00:50
C>* 10.168.146.16/30 is directly connected, eth0.3, 02:00:50
K * 10.168.148.32/29 [0/1] is directly connected, eth0.4, 02:00:50
C>* 10.168.148.32/29 is directly connected, eth0.4, 02:00:50
K * 10.168.158.23/32 [0/254] is directly connected, wwan0, 00:15:38