Hello there,
I have observed a weird behaviour with policy route where rule is not matching the logged packet. I followed the multiple-uplinked examples here: https://docs.vyos.io/en/latest/configuration/policy/examples.html#multiple-uplinks
Here is a snippet of the `show policy` PS discard the `local-route` section:
```
local-route {
rule 100 {
set {
table 40
}
source {
address 10.1.40.10
}
}
}
route PBR {
default-log
interface bond01.20
rule 5 {
destination {
address 10.1.1.216
}
set {
table main
}
source {
address 10.1.10.101
}
}
rule 10 {
description "route to oci-syd using table 10"
log
set {
table 10
}
source {
address 10.1.10.101
}
}
}
```
I use an ELK stack to monitor the syslog in my homelab and it has been working well, please find the screenshot:
{F4292518}
I can't really tell the strict order of route rules the `ping` has gone through from ELK, but you can see it has hit all rules (default, 5 and 10) and eventually the result was the decision of rule 10.
Now I was under the impression that the packet would have **hit** rule 5 and the decision would be made, instead of going further down the rule chain and hit rule 10.
If anyone could enlighten me the expected policy route behaviour it would great, or there maybe configuration errors from my side too, please let me know.