We have this problem in more then one case. The solution so gar is to use " as quote which we later on render in Jinja2
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 12 2021
Sounds like a missing validator. Wo should prevent users from doing such things ;)
@Viacheslav, when we use a migrator we should enable the ipv4 afi for each and every ipv4 neighbor if its not configured explicitly. What do you think? If a peer group is configured for that neighbour, too - that will be no issue.
Aug 11 2021
Thanks for you comment ! it's good consider that options
Similar task T2315, also there is bug related T1976, etc.
It should be a migration script that determines ip/ipv6 neighbor and set neighbor to properly afi.
So there is one question, how to determine which afi we should to use if we see "peer-group" in configuration?
I don't think that we can implement it in 1.3 as it uses an old codebase.
This will be merged, pending discussion on pros/cons of preprocessing vs. relaxing schema restriction.
Gotcha. Thanks. Will wait.
Hi @paunadeu yeah that is an open issue (https://github.com/vyos/vyos-1x/commit/d77709252de54757d3f3e76ce6c52492ba967488) it got disabled recently.
Thank you for the quick fix!
OK. Seeing VyOS output now:
I think wasn't a problem. Not defined VNI in VRF, in L3 respects config in L2 don't, asked for the behavior in FRR Slack.
@raphielscape Are there still problems after updating PR? Please provide the configuration and I'll take the time to check it
I added a new neighbor belonging to the sub-AS 65031 to the existing bgp configuration:
Hello, @nyamada!
Really appreciated for such a detailed problem analysis! The regex is fixed in the 1.4 version now.
Could you test it, so we can backport changes safely to 1.2 and 1.3?
To reproduce in 1.4:
As Workaround in T3350 set raw option "config /path/to/config/file"
@fernando Thanks.
Aug 10 2021
i've been testing this new feature in our last release and it works well :
A bit of background: the error here is is a result of the Relax-NG schema requiring a leaf node to have a 'properties' entry; that is considered a sanity check by the schema author, but emerges as an issue when we moved to a modular structure for the *.xml.i include files. Leaving that restriction as-is, the solution of merging leaf nodes in the lxml script should be straightforward (the general case more intricate), so I will look at amending the override-default script.
Sure ! i'll test this feature and let you know !
@fernando Can you check this feature in the next rolling release?
set service snmp community public client 127.0.0.1 set service snmp oid-enable route-table
Aug 9 2021
PR for Equuleus https://github.com/vyos/vyos-1x/pull/959
- Backport configquerry.py [Done]
https://github.com/vyos/vyos-1x/commit/2aa75521a829712256c3c34685e60a9d36b33791
Need to implement in customer, if I can help in something, please don't hesitate to ask.
Maybe with FRR 8.1
In any case, we'll do more tests.
It's upgrade on FRR planned?
https://github.com/vyos/vyatta-cfg-vpn/commit/2cec760601a6e85ca8e0b6a30c173196a97a777a
Back-ported the dhcp ip check loop to 1.3