VyOS supports Policy Routing, allowing traffic to be assigned to a different routing table. Traffic can be matched using standard 5-tuple matching (source address, destination address, protocol, source port, destination port).
And was wondering how exactly I am configuring 5-tuple based PBR?
Theoretical this is possible, but uncommon. When i think about random source ports.
I think this sentense mean, that this 5 matches are possible.
What do you want to do?
The wiki and the readthedocs has the same content regarding 5-tuple.
Nothing technical about ECMP or any routing related concepts such as weight.
What would happen if I am adding two next-hops?
Can VyOS be used as a load balancer for an AnyCast array of hosts?
… if it will route based on 5-tuple(srcip,dstip,proto,srcport,dstport) I can assume that it would be possible to advertise from an AnyCast array of hosts into VyOS with BGP and expect traffic routing to be static per 5-tuple.
(this is how it’s done on other Routing platforms)
i have understand, that your vyos router will the gateway from your clients to the anycast host. Or the reversed way?
you define you matching criteria and set a routing table, in this table you have the next hop ip. Each rule can have oder matching criteria and an other routing table set.
@rob The other way, this can be a border GW for a network of hosts.
clients <cloud> VyOS ---> <array of AnyCast hosts(such as DNS)>
These AnyCast hosts advertise to VyOS the same address using BGP.
The result should be a routing tables with let say multiple 8.8.8.8 addresses to couple next-hops with the same weight.