policy: modify path.GetAsSeqList() to insert 0 for non-seq-as-elems

GetAsSeqList() is used for AsPathSet matching and AsPathPrepend action.
Just eliminating non-seq-as-elems from what GetAsSeqList() returns cause
wrong results for these two match/action.

e.g path A's as-path: {100, 200} 300

currently, action 'as-path-prepend left-most repeat 2' will alter
as-path to 300 300 {100, 200} 300, which is not expected behavior.

To fix this, insert 0 for non-seq-as-elems.

Signed-off-by: ISHIDA Wataru <ishida.wataru@lab.ntt.co.jp>

0 files changed, 0 insertions, 0 deletions