yuusuke wrote:是mangle-routing-mark + policy routing rule的組合:


匹配用的是布林運算的AND閘:
如果規則中mangle-routing-mark的src-address=192.168.88.100,
policy routing rule的interface=lan(192.168.88.0/24),
最後policy routing的src-address觸發的只會有192.168.88.100
同樣若policy routing rule的src-address=192.168.88.200/32,
mangle-routing-mark的in-interface=lan(192.168.88.0/24),
最後policy routing的src-address觸發的只會有192.168.88.200
若mangle-routing-mark的src-address=192.168.88.100,
policy routing rule的src-address=192.168.88.0/24,
最後policy routing的src-address觸發的只會有192.168.88.100
同樣若policy routing rule的src-address=192.168.88.200/32,
mangle-routing-mark的src-address=192.168.88.0/24,
最後policy routing的src-address觸發的只會有192.168.88.200
若mangle-routing-mark的src-address=192.168.88.100,
policy routing rule的interface=lan2(192.168.89.0/24),
這樣policy routing便會無法匹配,不作用!
同樣若policy routing rule的src-address=192.168.88.200/32,
mangle-routing-mark的in-interface=lan(192.168.89.0/24),
同樣policy routing無法匹配,不作用!
若mangle-routing-mark的src-address=192.168.88.100,
policy routing rule的src-address=192.168.89.0/24,
這樣policy routing便會無法匹配,不作用!
同樣若policy routing rule的src-address=192.168.88.200/32,
mangle-routing-mark的src-address=192.168.89.0/24,
同樣policy routing無法匹配,不作用!

這嘛設置fasttrack沒毛病,完全合法。