You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two transit peers for v6 and noticed one of the sessions was getting closed due to max prefixes, which happened to be slightly more than 200,000 (full table from provider). Other session at ~196k had not hit this limit yet.
Looking at the config documentation, "import-limit6" default is listed as 300,000, but when running pathvector generate it translates to "20000" in the generated BIRD config file when "import-limit6" not explicitly set in template or peer configuration within pacthvector's configuration file.
Environment
Output from pathvector version
Pathvector 6.3.2
Built c35220bf121f366ff05a51d93c6236e8c324d682 on 2023-06-11T07:03:14Z
No plugins
BIRD: ready.
Describe the bug
I have two transit peers for v6 and noticed one of the sessions was getting closed due to max prefixes, which happened to be slightly more than 200,000 (full table from provider). Other session at ~196k had not hit this limit yet.
Looking at the config documentation, "import-limit6" default is listed as 300,000, but when running
pathvector generate
it translates to "20000" in the generated BIRD config file when "import-limit6" not explicitly set in template or peer configuration within pacthvector's configuration file.Environment
pathvector version
yaml
language identifierTo Reproduce
Steps to reproduce the behavior:
pathvector -v generate
and it processes correctly without any errors.Expected behavior
BIRD configuration for peer should have IPv6 limit set to 300,000 rather than 200,000:
after setting "import-limit6" in pathvector.yml to 400000, the generated BIRD config file for peer updates as expected:
The text was updated successfully, but these errors were encountered: