Age | Commit message (Collapse) | Author |
|
neighbor results in an out of sync condition between the vyatta config and the bgpd config
- still need vtysh to exit non-zero.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
load on boot
|
|
The CLI begin transaction restrictions make this impossible to
do in a stable manner.
Related to bug 4537
(cherry picked from commit dcebd6d713e76b3e01ba51710693d688e1570cdb)
|
|
The Quagga system needs all daemons to be running if any prefix list
is defined. And since CLI allows only one begin event, we are forced
to start all routing daemons if user defines any policy!
Bug 4643
(cherry picked from commit 8baea0622fbbc6a9e643df2a4bb8fa8a72fd02fa)
|
|
This is what CLI Primer says is supposed to work.
|
|
New CLI appears to require 'update:' rather than 'create:' on
tag nodes in order for them to get applied correctly. Workaround
this by changing all the create: to update: in Quagga config
Bug 4486
|
|
|
|
|
|
An "update" action in a non-leaf valueless node is only called when the
node is created for the first time. So the "create" action should be
used instead of "update".
|
|
Templates in */node.tag/node.def are meaningless in current CLI.
Remove all the templates that are intermediat help text.
(cherry picked from commit ebd628b2b2a93d78a60c1d0ed41d0ab793c0efdf)
|
|
node.def below node.tag is meaningless
(cherry picked from commit b606ac1a7f1120d5203a581d85e9953401d02b07)
|
|
Node was marked as 'tag:' but was a leaf node.
(cherry picked from commit 31368eec9b7dd25e248140a8732fd4c814de52b9)
|
|
Move the default import-check enabled from template to command line
option in bgpd. This resolves some of the startup issues.
(cherry picked from commit a1d23a42ef83968222b0744505986db3e02b0ae8)
|
|
BGPD needs to be started when parameters and neighbors are set.
Bug 4486
(cherry picked from commit c600f91dee1ed705648eff626f8fd090a28720b5)
|
|
need remote-as to be highest priority sibling
Bug 4486
(cherry picked from commit cf0f8def872cf356f10e14c5ac0956022eab9d0b)
|
|
Multiple value nodes are never updated, only created or deleted.
(cherry picked from commit 909452cdb631577aed7b9a7aed6613c2756f4e33)
|
|
This is what CLI Primer says is supposed to work.
(cherry picked from commit 4cb6efba141b1e54ee78077410dd027a8fcf1a39)
|
|
New CLI appears to require 'update:' rather than 'create:' on
tag nodes in order for them to get applied correctly. Workaround
this by changing all the create: to update: in Quagga config
Bug 4486
(cherry picked from commit 84536c188e359a9f046bc8f1c5a3180b3e03ee8b)
|
|
Use same syntax as other nodes
Precursor to automated edit of nodes for other bugfix.
(cherry picked from commit 435e80791de6b051ab88c7eaa7c47265bbef3be5)
|
|
The new CLI doesn't fail transaction automatically when one command fails.
(cherry picked from commit a50404c259bcbb424743d80a18bf87319666bce8)
|
|
|
|
Bug 4014
The actual device (ppp for example) may not exist when OSPF is
brought up, so allow any name
|
|
Use 'update: ...' rather than 'update:expression: ...'
|
|
Related to bug 4345
|
|
This may resolve some of the priority issues.
|
|
Bug 4391
Quagga allows IP address or interface as update source, so generalize
existing template.
|
|
Missing fi.
|
|
There were several problems with the quagga-manager update.
1) can not have multiple end: tags in same tree path
2) can not shutdown bgp without losing policy
3) watchquagga timing races
|
|
|
|
New syntax is cleaner
|
|
|
|
Wrong way to fix it.
This reverts commit b6f1a09410983507a7cfc8b08dafbd13600ed8e5.
|
|
|
|
Fixing vyatta-bgp checker found a bug in this template.
Template refered to wrong node in commit check.
It would do:
vyatta-bgp.pl --check-as --as <neighbor> --neighbor soft-reconfiguration
|
|
Change error message to not say "ethernet".
|
|
|
|
Rather than 100's of copies of the same template, use the same
process as the firewall module to generate the templates.
For this, the are meta-templates in interface-templates directory
which get processed and $IFNAME is replaced by the appropriate CLI
syntax to refer back to the directory name. Changing a quagga
template in most cases can be done by fixing the meta-template.
|
|
|
|
|
|
Rather than having mulitple copies of same template, use symlinks
|
|
This only happens if link metrics set but OSPF/RIP not running yet.
|
|
Easier to just have utility print error message
|
|
Avoid config issues with update on multi-node
|