@c-po
I propose to add "set routing-options x.x.x.x"
And also migrate protocols xxx route-map

set protocols bgp 65001 route-map RMAP
set protocols bgp|ospf|isis route-map RMAP

@wsapplegate I create a PR for it https://github.com/vyos/vyos-1x/pull/847
Can you describe how to test/check it? I'm not familiar with that dns format. I tried zone with dot and without. Not sure how to check/test it.

@rizkidtn I don't understand exactly what wrong with the community?
Customers sent you routes, with blackhole community, on the router you mark match this community and set next hop "blackhole" IP address.

I don't fully understand your scheme
What interrelation between arp and tcp policy?

show conf com | match ospfv3

Copy configuration.
Delete protocols ospfv3
commit
re-add ospf config.

Time Exceeded (3)

PR for current https://github.com/vyos/vyos-1x/pull/844
PR for Equuleus https://github.com/vyos/vyatta-cfg-quagga/pull/78

I can't reproduce it VyOS 1.3-rolling-202105011026

It will be enough to add a quote here?

"\`"

https://github.com/vyos/vyatta-cfg/blob/fa2b172512aa024a9853166528c9e6601fde94d8/src/cli_new.c#L1886-L1888

A quick solution that convert JSON to config set

Can be "cherry picked" to 1.3 and 1.2

PR https://github.com/vyos/vyatta-op-vpn/pull/27

@Dmitry I can't reproduce it anymore VyOS 1.2.7

vyos@r2-lts:~$ touch tttt.txt
vyos@r2-lts:~$ ls
1.txt  foo.txt  ntp.conf  ntp.conf.2021-05-13-1945.pre-migration  ntp.conf.2021-05-13-2107.pre-migration  test.py  test.txt  tttt.txt  vyos@192.168.122.16
vyos@r2-lts:~$ 
vyos@r2-lts:~$ reset vpn remote-access user 
Possible completions:
  <text>        Terminate specified user's current remote access VPN session(s)

Default value https://github.com/vyos/vyatta-conntrack-sync/blob/7a8827e0d72cf771b0551915d738abe4838c0915/templates-cfg/service/conntrack-sync/mcast-group/node.def#L2

PR https://github.com/vyos/vyos-1x/pull/840
Can be "cherry-picked" to "equuleus" and "crux"

vyos@r6-roll# load ntp.conf
Loading configuration from 'ntp.conf'
Load complete. Use 'commit' to make changes effective.
[edit]
vyos@r6-roll#

Also bug for config "vyos" set mode clientset remote-port 12345

vyos@r6-roll# run show remote-config openvpn vtun0 remote-platform vyos 
NOTE: authentication options are deliberately left out,
since we cannot know file paths on a remote system

@zsdc Can we close it?

@krox2 The next rolling release will be with keepalived 2.1.5. Can you check?

PR https://github.com/vyos/vyos-1x/pull/837

PR https://github.com/vyos/vyos-build/pull/165

@ernstjo

set policy route-map ASxxx-CUS-IN6 rule 10 action 'permit'
set policy route-map ASxxx-CUS-IN6 rule 10 set large-community '65:23:1 additive'

PR https://github.com/vyos/vyos-1x/pull/836

Frr itself doesn't allow to set longer-prefixes without "prefix"

r4-1.3# show ip route 1.1.1.1 
  <cr>           
  json           JavaScript Object Notation
  nexthop-group  Nexthop Group Information

Can you change update source from eth0 to x.x.x.x?

I think there is no routes to neighbor
So you get it via default-route
You need to declare /32 route
Or use option
“ set protocols bgp neighbor <address|interface> disable-connected-check”

it not directly connected neighbours It can’t determine route to the next hop.
Try to set /32 route to ipv4 next hop and check again.

@francis We don't know anything about this issue.
And it difficult to say without the current configuration.

@rherold can you recheck it? Or say is it real 1.3.0-rc4?
I can't reproduce it.

PR https://github.com/vyos/vyatta-cfg-quagga/pull/77

PR crux https://github.com/vyos/vyatta-cfg-vpn/pull/44

Which proper format do we need?
For example 2 tunnels:
peer-100.64.0.2-tunnel-0
peer-100.64.0.2-tunnel-1

Maybe related task T3505 which deletes the default route for DHCP in the commit.

PR https://github.com/vyos/vyos-1x/pull/834

@carl.byington is it working in 1.3?