@olofl Can you re-check it? Or can we close it?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
May 20 2021
May 19 2021
As I understand it a part of zebra, not specified to any protocol.
Maybe I'm wrong and we don't need it.
A similar problem, only for ipv4 https://phabricator.vyos.net/T1053
As we can see ipv6 address before normalization without prefix
DEBUG: 2001:db8::191 before normalize
https://github.com/vyos/vyatta-cfg-system/blob/165e56e88763c40f13e6ef77f5df1c888fdfb899/scripts/vyatta-address#L38
@c-po Nope,
vyos@r6-roll:~$ sudo ip -d link show | grep vtun -A 5
5: vtun1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 100
link/none promiscuity 0 minmtu 68 maxmtu 65535
tun type tun pi off vnet_hdr off persist off addrgenmode none numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535@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
May 18 2021
@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.
May 17 2021
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
May 15 2021
It will be enough to add a quote here?
"\`"
A quick solution that convert JSON to config set
May 14 2021
Can be "cherry picked" to 1.3 and 1.2
May 13 2021
@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 [email protected] vyos@r2-lts:~$ vyos@r2-lts:~$ reset vpn remote-access user Possible completions: <text> Terminate specified user's current remote access VPN session(s)
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?
May 12 2021
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'
May 11 2021
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
May 10 2021
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.
May 8 2021
@rherold can you recheck it? Or say is it real 1.3.0-rc4?
I can't reproduce it.