@joshua.hanley Could you provide the output of the next command?
sudo accel-cmd -p 2004 show sessions
@joshua.hanley Could you provide the output of the next command?
sudo accel-cmd -p 2004 show sessions
PR with dependencies: https://github.com/vyos/vyos-build/pull/341
PR (for build): https://github.com/vyos/vyos-build/pull/340
Incorrect modify modify_section: starting search for '^vrf protocols' until '^exit-vrf'
vyos@r14# delete vrf name red vni [edit] vyos@r14# commit [ vrf name red vni 3000 ] {'name': {'protocols': {'bgp': {'address_family': {'ipv4_unicast': {'redistribute': {'connected': {}}}, 'l2vpn_evpn': {'advertise': {'ipv4': {'unicast': {}}}}}, 'system_as': '65001'}}, 'table': '3000'}} load_configuration: Configuration loaded from FRR daemon zebra load_configuration: loaded 0 ! load_configuration: loaded 1 frr version 8.5 load_configuration: loaded 2 frr defaults traditional load_configuration: loaded 3 hostname debian load_configuration: loaded 4 log syslog load_configuration: loaded 5 log facility local7 load_configuration: loaded 6 hostname r14 load_configuration: loaded 7 service integrated-vtysh-config load_configuration: loaded 8 ! load_configuration: loaded 9 vrf red load_configuration: loaded 10 vni 3000 load_configuration: loaded 11 exit-vrf load_configuration: loaded 12 ! load_configuration: loaded 13 end modify_section: starting search for '^vrf protocols' until '^exit-vrf'
Two cents from the fields. It will be nice to see vrf aware cg-nat solution, when subscribers from a number of "inside" vrfs NAT'ed into one outside vrf. Of course if that's possible.
Test case above produces:
Merged T5178 into this one; cf. the description there for background of the issue.
PR for equuleus:
https://github.com/vyos/vyos-1x/pull/1969
PR for equuleus:
https://github.com/vyos/vyos-http-api-tools/pull/5
According to nft changelog, this feature is available in 1.0.7 in a much better way:
@Harliff Could you check it? Available in the latest rolling release
vyos@r14# set protocols failover route 192.0.2.55/32 next-hop 192.168.122.1 check policy Possible completions: all-available All targets must be alive any-available Any target must be alive (default)
Hi guys,
This has a simple fix: starlette commit c568b55d set the attribute
Request._form = None
to support use of Request.form() as a context manager. Since we override the Request class for backwards-compatibility support (translation) of form-data requests, we need to check for value, not existence, of the attribute. Adding this fix allows updating FastAPI past 0.91.0.
bfd is able to monitoring static routes , using profiles and multi-hop to reached a peer :
PR https://github.com/vyos/vyos-1x/pull/1966
set protocols failover route 192.0.2.55/32 next-hop 192.168.122.1 check policy 'any-available' set protocols failover route 192.0.2.55/32 next-hop 192.168.122.1 check target '192.168.122.1' set protocols failover route 192.0.2.55/32 next-hop 192.168.122.1 check target '192.168.122.11' set protocols failover route 192.0.2.55/32 next-hop 192.168.122.1 check timeout '3' set protocols failover route 192.0.2.55/32 next-hop 192.168.122.1 interface 'eth0'
Don't have any idea how to integrate this logic to XML https://github.com/vyos/vyatta-wanloadbalance/blob/973421035568810e2583187c48d14054970b9806/templates/load-balancing/wan/node.def#L2-L5
Just in case someone wants to implement this: debugging must not be enabled by default, only on demand or via config.
Per VyOS maintainers, this operation isn't necessary.