There are two versions that have been developed, reasonably feature complete, pending testing. One presents an OpenAPI schema of application/x-www-form-urlencoded (multipart forms); the other, application/json. The latter uses middleware (strictly speaking, a custom request and route class, instead of the Starlette middleware capability, although that may change) to intercept multipart requests, so as to remain backwards compatible.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Mar 16 2021
Mar 16 2021
jestabro changed the status of T3412: HTTP API: move to FastAPI as web framework from Open to In progress.
jestabro changed the status of T3411: Extend the redirect_stdout context manager in vyos-configd to redirect stdout from subprocesses, a subtask of T3302: Make vyos-configd relay stdout from scripts to the user's console, from In progress to Needs testing.
jestabro changed the status of T3411: Extend the redirect_stdout context manager in vyos-configd to redirect stdout from subprocesses from In progress to Needs testing.
jestabro changed the status of T3302: Make vyos-configd relay stdout from scripts to the user's console from Unknown Status to Resolved.
jestabro changed the status of T3302: Make vyos-configd relay stdout from scripts to the user's console, a subtask of T2347: During commit, any script output directed to stdout will contain path, from Unknown Status to Resolved.
jestabro removed a project from T3302: Make vyos-configd relay stdout from scripts to the user's console: VyOS 1.3 Equuleus.
jestabro changed the status of T3411: Extend the redirect_stdout context manager in vyos-configd to redirect stdout from subprocesses from Open to In progress.
If I remember this change was accepted in to VyOS 1.3. There is confirmation of a configuration where we set IPv4 and IPv6 preferred source in the following thread:
https://phabricator.vyos.net/T1528
Mar 15 2021
Mar 15 2021
This totally breaks remote console access for me on 1.2.6, FWIW, so I consider it a fairly serious bug.
Any chance of motion on this?
@dmbaturin, don't forget to backport the other two PRs to 1.3:
https://github.com/vyos/vyatta-cfg-firewall/pull/20
https://github.com/vyos/vyos-1x/pull/730
stepler changed the status of T3395: WAN load-balancing fails with nexthop dhcp from Resolved to Unknown Status.
Waiting on backport to 1.3.
Unknown Object (User) added a comment to T3329: "system conntrack ignore" rules can no longer be created due to an iptables syntax change.
@dmbaturin please cherry-pick this to equuleus. Successfully tested on VyOS-1.3-RC1
Thanks, @erkin --- I'm sure you can cherry-pick from 1.4 to 1.3; 'backporting' is not quite the right word, as it is development branch to stable branch. I really like this solution to the mess that was remote.py.
erkin closed T3354: Convert strip-private script from Perl to Python, a subtask of T3355: Remove all remaining legacy Vyatta code, as Resolved.
zsdc changed the status of T3410: Unsafe processing of special characters in CLI autocomplete from Open to Confirmed.
In T3409#89863, @runar wrote:
GitHub <noreply@github.com> committed rVYOSONEX13d850bc8398: Merge pull request #774 from erkin/current (authored by dmbaturin).
I'll give backporting a try. It should be doable as long as Paramiko is in our reach. If not, I'll see if I can cobble together something to check for hostname resolution failure.
Mar 14 2021
Mar 14 2021
Thanks for the feedback.
I've found out conf string with "--" works the same way like string without "--". Sorry to trouble you with this question.
Hi, how is the container support now
Viacheslav changed the status of T3403: Error on interrupting list of pppoe sessions from Open to Needs testing.
c-po closed T3325: Bgp listen-range wrong commit message, a subtask of T2174: Rewrite protocol BGP to new XML/Python style, as Resolved.
sever-sever <v.gletenko@vyos.io> committed rVYOSONEX9761804ddef4: conf-mode: T2425: Add XML for policy-lists.
GitHub <noreply@github.com> committed rVYOSONEXfece992339e6: Merge pull request #733 from sever-sever/T2425 (authored by c-po).
sever-sever <v.gletenko@vyos.io> committed rVYOSONEX8fc658f521aa: pppoe: T3403: Fix show sessions interrupt for op-mode.
GitHub <noreply@github.com> committed rVYOSONEXdfa91f60f8bf: Merge pull request #773 from sever-sever/T3403 (authored by c-po).
c-po closed T1513: Move OSPF and RIP interface configuration under protocols, a subtask of T2173: Add the ability to use VRF on VTI interfaces, as Resolved.
Implemented in VyOS 1.4
Implemented in VyOS 1.4 rolling
c-po closed T2271: OSPF: add per VRF instance support, a subtask of T2175: Rewriting all FRR processes allow for reloading and to XML/Python style, as Resolved.
c-po closed T2271: OSPF: add per VRF instance support, a subtask of T3344: Per VRF dynamic routing support, as Resolved.
c-po closed T3344: Per VRF dynamic routing support, a subtask of T2579: The root task for VRF features, as Resolved.
c-po closed T3344: Per VRF dynamic routing support, a subtask of T2175: Rewriting all FRR processes allow for reloading and to XML/Python style, as Resolved.
Example configurations:
c-po closed T3345: BGP: add per VRF instance support, a subtask of T3344: Per VRF dynamic routing support, as Resolved.
GitHub <noreply@github.com> committed rVYOSONEX2785a486f798: Merge pull request #770 from c-po/vrf-dynamic-routing (authored by c-po).
I'm curious, I did a little research on Tacacs +, and I'm not sure what you want the certification service to do for you? SSH certification or?
@svd135 please retest with the latest 1.4 rolling or 1.3 beta version. The issue should be corrected.
c-po added a project to T3383: BGP IPv6 neighbor statements configuration not normalized.: VyOS 1.4 Sagitta.
Also CUMULUS has a nice looking package
A migration script is available from 1.3 onwards.