The neighbor can contain a string
set protocols bgp 64501 neighbor eth1 set protocols bgp 64501 neighbor eth1 remote-as 65001
The neighbor can contain a string
set protocols bgp 64501 neighbor eth1 set protocols bgp 64501 neighbor eth1 remote-as 65001
Something wrong with that check https://github.com/vyos/vyos-1x/blob/8732ebc46a2daddc6e4dfa05f3f70bf2ac9400af/src/conf_mode/protocols_bgp.py#L170-L171
Fail
set protocols bgp 64501 neighbor 203.0.113.1 remote-as 65001 set protocols bgp 64501 neighbor 203.0.113.1 peer-group FOO set protocols bgp 64501 peer-group FOO
PR https://github.com/vyos/vyos-1x/pull/748
Add checks for neighbor "is_addr_assigned"
Your rolling release so old. As I remember it was a bug with FRR, which was fixed.
Try more latest versions or vyos-1.3.0-rc1 https://community.vyos.net/get/snapshots/
@craterman can you check this feature in the latest rolling or beta?
PR for equuleus | extended smoketest
https://github.com/vyos/vyos-1x/pull/743
PR https://github.com/vyos/vyatta-cfg-quagga/pull/71
Can be "cherry-picked" to equuleus
PR for equuleus for bgp and ospf https://github.com/vyos/vyatta-cfg-quagga/pull/70
PR for equuleus for rip https://github.com/vyos/vyos-1x/pull/741
I can't reproduce it
@tuxnet Can you describe the steps to reproduce?
It seems it works now
As we use 7.5 in 1.4 now, we can implement that feature.
In T3344#87831, @runar wrote:@Viacheslav in you example, what does set protocols bgp <asn> vrf do? if i'm reading it correctly it makes no sense as you do not start a new process, and the ASN for the vrf will be the asn of the global bgp process
I prefer more option2
@ernstjo I can't reproduce it in VyOS 1.4-rolling-202102190541
Template generate wrong value
https://github.com/vyos/vyos-1x/blob/current/data/templates/frr/bgp.frr.tmpl#L112