I don't think anyone saw this issue lately, but if it resurfaces, feel free to reopen the task.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 11 2024
Jan 8 2024
Dec 17 2023
Aug 25 2023
Jul 12 2023
Jun 13 2023
I opened an issue on github:
Aug 29 2022
Apr 1 2022
Mar 31 2022
I can confirm that the issue is fixed on today's rolling release!
Mar 30 2022
Bugfix just got merged into FRR codebase - next VyOS rolling ISO image will have the fix.
Mar 28 2022
FRR bugreport filed https://github.com/FRRouting/frr/issues/10911
Mar 27 2022
I'm not comfortable posting my config here for ever but I've uploaded it to ubuntu pastebin and set it to expire in a week: https://paste.ubuntu.com/p/BW5KxyjPQr/
Can not get it crashed here. Please share your full config.
Still seems to be broken on 1.4-rolling-202203270930
Re-run with the latest FRR code-base and it also seems to be fixed - please try the latest VyOS version ;)
Feels like the bug was introduced in https://github.com/FRRouting/frr/commit/36295a387c241d3dba7aaa305a1860a6a07ab0cf
Feb 22 2022
@Viacheslav, hmmm, yeah that's a good point. I'll see what I can do to add the OP configs. I know I added the conf configs.
@Cheeze_It There is a task for op-mode T4265
Task for controller T4266
Nov 6 2021
Oct 17 2021
Sep 29 2021
Sep 11 2021
Sep 10 2021
Sep 3 2021
Aug 9 2021
@xrobau As I mentioned before, peer-group can't exist without peer-as/remote-as in your case remote-as should be internal. It can exist without remote-as but with "route-reflector-client" it shouldn't
You can check it with vtysh FRR:
Aug 6 2021
You COULD have a peer-group without remote-as, as you could apply that peer group to multiple remotes, and override the remote-as. But that is an edge case. The BETTER way to handle it is to enforce having a remote-as -- especially if you enable route-reflector-client
Aug 3 2021
@xrobau You have to set remote-as for peer-group or for neighbor
[email protected]# set protocols bgp 65001 peer-group FOO [edit] [email protected]# set protocols bgp 65001 neighbor 203.0.113.2 peer-group FOO [edit] [email protected]# set protocols bgp 65001 neighbor 203.0.113.2 remote-as 65002 [edit] [email protected]# commit [edit] [email protected]#
Aug 1 2021
Jun 23 2021
@Harliff Try 1.2.7/1.3 it was fixed with commit https://github.com/vyos/vyos-build/pull/138/files#diff-c7d29a506307d9cf8d86c3cd3f65ca4e4058ea442cacdf9a89d2485b56c7417aR67
T2061
I've not checked later versions. Maybe it was already fixed on 1.2.7 or 1.3/1.4 ?
Apr 30 2021
Will be adding the BGP op commands for it as well eventually...
Apr 29 2021
Already in 1.4
set protocols bgp address-family ipv4-flowspec
Oct 23 2020
Sep 9 2020
Aug 3 2020
Jul 27 2020
Fixed, VyOS 1.3-rolling-202007270117
Jul 26 2020
May 30 2020
May 13 2020
Mar 1 2020
Feb 9 2020
Feb 4 2020
Jan 13 2020
In FRR 7.0.1 (VyOS 1.2.3) was some bug, due to which static routes were not updated (maybe, not in all cases or environments) after the next-hop state change. In VyOS 1.2.4 we use stable FRR 7.2, which processes this situation without problems. An example (key point from FRR debug log):
FRR 7.0.1:
Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.0/30: Adding route rn 0x5612ea69d1f0, re 0x5612ea69d370 (type 2) Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.0/30: Redist update re 0x5612ea69d370 (type 2), old (nil) (type -1) Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.0/30: Adding route rn 0x5612ea69d490, re 0x5612ea69e110 (type 2) Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.0/30: Redist update re 0x5612ea69e110 (type 2), old (nil) (type -1) Jan 13 15:29:51 vyos zebra[1041]: NHT processing check for zvrf default Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.1/32: Evaluate RNH, type 0 Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.1/32: NH resolved over route 10.230.230.0/30 Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.1/32: Notifying client static about NH Jan 13 15:29:51 vyos zebra[1041]: 0:192.168.20.1/32: Evaluate RNH, type 0
FRR 7.2:
Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30: Adding route rn 0x5574620a18b0, re 0x5574620a1930 (connected) Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30: Adding route rn 0x5574620a29b0, re 0x5574620a1850 (connected) Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30 update_from_ctx(): no fib nhg Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30 update_from_ctx(): rib nhg matched, changed 'true' Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30: Redist update re 0x5574620a1930 (connected), old 0x0 (None) Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.1/32: Evaluate RNH, type Nexthop Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.1/32: NH resolved over route 10.230.230.0/30 Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.1/32: Notifying client static about NH Jan 13 15:33:23 vyos zebra[1042]: rib_add_multipath: 0:10.0.0.0/8: Inserting route rn 0x5574620a1b10, re 0x5574620a1a30 (static) existing (nil) Jan 13 15:33:23 vyos zebra[1042]: 0:10.0.0.0/8: Adding route rn 0x5574620a1b10, re 0x5574620a1a30 (static) Jan 13 15:33:23 vyos zebra[1042]: netlink_route_multipath(): RTM_NEWROUTE 10.0.0.0/8 vrf 0(254) Jan 13 15:33:23 vyos zebra[1042]: netlink_route_multipath() (single-path): nexthop via 10.230.230.1 if 3(0) Jan 13 15:33:23 vyos zebra[1042]: netlink_talk: netlink-dp (NS 0) type RTM_NEWROUTE(24), len=60 seq=10 flags 0x501 Jan 13 15:33:23 vyos zebra[1042]: 0:10.0.0.0/8 update_from_ctx(): no fib nhg Jan 13 15:33:23 vyos zebra[1042]: 0:10.0.0.0/8 update_from_ctx(): rib nhg matched, changed 'true' Jan 13 15:33:23 vyos zebra[1042]: 0:10.0.0.0/8: Redist update re 0x5574620a1a30 (static), old 0x0 (None)
So, configured static routes updating properly.
Jan 6 2020
Jan 1 2020
Dec 27 2019
Dec 17 2019
PR https://github.com/vyos/vyatta-op/pull/32
Fix "show monitoring" command.
Dec 16 2019
PR https://github.com/vyos/vyatta-op-quagga/pull/4/commits/7659873869d92c9ec6b363db7e06d2ba5b41e5f6
New syntax for commands "monitor protocol bgp enable", "monitor protocol bgp disable"
Dec 14 2019
It looks like the VyOS has the old command syntax.
Feb 19 2019
Feb 8 2019
Feb 5 2019
Jan 31 2019
Jan 18 2019
Jan 3 2019
Jan 1 2019
Dec 21 2018
Dec 15 2018
Dec 5 2018
Nov 27 2018
Nov 25 2018
Since most of the work is done and every release candidate of 1.2.0 has been using FRR already, I suppose we should close it. Remaining issues that are causes by FRR incompatibilities should, and are getting their own tasks anyway.
Nov 20 2018
Nov 13 2018
Nov 6 2018
Oct 29 2018
Oct 24 2018
Oct 13 2018
not vyos related