- frog - lists.frrouting.org

Announcing FRR 8.0.0
by Quentin Young 30 Jul '21

30 Jul '21

Hi all, We are pleased to announce the 8.0 release of FRRouting! Github Release - https://github.com/FRRouting/frr/releases/tag/frr-8.0 Debian Packaging - https://deb.frrouting.org/ RPM Packaging - https://rpm.frrouting.org/ Some major highlights: - A new daemon, pathd, has been added. This daemon implements support for segment routing. - EVPN Multihoming is now fully supported - OSPFv3 now supports VRFs - TI-LFA has been implemented in IS-IS and OSPF - Zebra now has the ability to dump netlink messages in a human-friendly format - LDP gained SNMP support And of course, innumerable bug fixes and other improvements. Please see the release notes for the detailed changelog: https://frrouting.org/release/8.0/ We expect to have a bugfix release out in the near future to include some fixes that didn't make it into this release, so please stay tuned for that. As always, thank you to all contributors! Cheers, - Quentin

1 0

OSPF, FreeBSD and aliases
by Eugene Grosbein 20 Jul '21

20 Jul '21

Hi! I hope this is right list to ask. Please correct me if not. I'm trying to move from quagga to frr 7.5.1. I have existing working setup with OSPF and FreeBSD servers that have some aliases on its OSPF-enabled interfaces. In FreeBSD, if one needs several IP addresses in same IP subnet on one interfaces (for CARP etc.) then one assigns one of IPs with "real" subnet mask and others with /32 mask: igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 inet 192.168.49.3 netmask 0xffffff00 broadcast 192.168.49.255 inet 192.168.49.13 netmask 0xffffffff broadcast 192.168.49.13 inet 192.168.49.17 netmask 0xffffffff broadcast 192.168.49.17 And another OSPF neighbour: igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 inet 192.168.49.1 netmask 0xffffff00 broadcast 192.168.49.255 inet 192.168.49.10 netmask 0xffffffff broadcast 192.168.49.13 inet 192.168.49.11 netmask 0xffffffff broadcast 192.168.49.17 This worked for me for years with quagga but frr's ospfd does not form neighbourship with following errors: interface igb0:192.168.49.17: ospf_read network address is not same [192.168.49.1] interface igb0:192.168.49.17: ospf_read network address is not same [192.168.49.10] interface igb0:192.168.49.17: ospf_read network address is not same [192.168.49.11] It seems ospfd's checks cannot cope with FreeBSD-like IP aliases. Please help.

3 8

Where is ./bootstrap.sh coming from?
by Saqib Ilyas 18 Jul '21

18 Jul '21

Hi I am tyring to build a Docker image for FRR using https://github.com/FRRouting/frr/blob/master/docker/ubuntu20-ci/Dockerfile. When it gets to line 55, it fails on ./bootstrap/.sh. I have manually inspected the Dockerfile and it seems that the only thing that would write anything to /home/frr/frr is the libyang build. But that isn't producing any file by that name. I tried manually building libyang, too. Where is bootstrap.sh supposed to come from? Thanks and best regards -- Saqib Ilyas

2 1

Error with Ansible - socket_path must be a value
by Saqib Ilyas 14 Jul '21

14 Jul '21

Hi I have started a few FRR containers using containerlab. From the host running the container, I can ping the router just fine. Then, I try to interact with the router using Ansible. When I use the facter module, things work just fine. However, when I use the Ansible frr.frr module, I get the following error: An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AssertionError: socket_path must be a value fatal: [172.20.20.4]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n File \"/root/.ansible/tmp/ansible-tmp-1626187837.4416695-33984649570835/AnsiballZ_frr_facts.py\", line 102, in <module>\n _ansiballz_main()\n File \"/root/.ansible/tmp/ansible-tmp-1626187837.4416695-33984649570835/AnsiballZ_frr_facts.py\", line 94, in _ansiballz_main\n invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n File \"/root/.ansible/tmp/ansible-tmp-1626187837.4416695-33984649570835/AnsiballZ_frr_facts.py\", line 40, in invoke_module\n runpy.run_module(mod_name='ansible_collections.frr.frr.plugins.modules.frr_facts', init_globals=None, run_name='__main__', alter_sys=True)\n File \"/usr/lib/python3.8/runpy.py\", line 207, in run_module\n return _run_module_code(code, init_globals, run_name, mod_spec)\n File \"/usr/lib/python3.8/runpy.py\", line 97, in _run_module_code\n _run_code(code, mod_globals, init_globals,\n File \"/usr/lib/python3.8/runpy.py\", line 87, in _run_code\n exec(code, run_globals)\n File \"/tmp/ansible_frr.frr.frr_facts_payload_0vramok4/ansible_frr.frr.frr_facts_payload.zip/ansible_collections/frr/frr/plugins/modules/frr_facts.py\", line 425, in <module>\n File \"/tmp/ansible_frr.frr.frr_facts_payload_0vramok4/ansible_frr.frr.frr_facts_payload.zip/ansible_collections/frr/frr/plugins/modules/frr_facts.py\", line 410, in main\n File \"/tmp/ansible_frr.frr.frr_facts_payload_0vramok4/ansible_frr.frr.frr_facts_payload.zip/ansible_collections/frr/frr/plugins/modules/frr_facts.py\", line 134, in __init__\n File \"/tmp/ansible_frr.frr.frr_facts_payload_0vramok4/ansible_frr.frr.frr_facts_payload.zip/ansible_collections/frr/frr/plugins/module_utils/network/frr/frr.py\", line 18, in get_capabilities\n File \"/tmp/ansible_frr.frr.frr_facts_payload_0vramok4/ansible_frr.frr.frr_facts_payload.zip/ansible/module_utils/connection.py\", line 121, in __init__\nAssertionError: socket_path must be a value\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1} An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AssertionError: socket_path must be a value fatal: [172.20.20.6]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n File \"/root/.ansible/tmp/ansible-tmp-1626187837.3930752-95082556581940/AnsiballZ_frr_facts.py\", line 102, in <module>\n _ansiballz_main()\n File \"/root/.ansible/tmp/ansible-tmp-1626187837.3930752-95082556581940/AnsiballZ_frr_facts.py\", line 94, in _ansiballz_main\n invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n File \"/root/.ansible/tmp/ansible-tmp-1626187837.3930752-95082556581940/AnsiballZ_frr_facts.py\", line 40, in invoke_module\n runpy.run_module(mod_name='ansible_collections.frr.frr.plugins.modules.frr_facts', init_globals=None, run_name='__main__', alter_sys=True)\n File \"/usr/lib/python3.8/runpy.py\", line 207, in run_module\n return _run_module_code(code, init_globals, run_name, mod_spec)\n File \"/usr/lib/python3.8/runpy.py\", line 97, in _run_module_code\n _run_code(code, mod_globals, init_globals,\n File \"/usr/lib/python3.8/runpy.py\", line 87, in _run_code\n exec(code, run_globals)\n File \"/tmp/ansible_frr.frr.frr_facts_payload_y1xygkr8/ansible_frr.frr.frr_facts_payload.zip/ansible_collections/frr/frr/plugins/modules/frr_facts.py\", line 425, in <module>\n File \"/tmp/ansible_frr.frr.frr_facts_payload_y1xygkr8/ansible_frr.frr.frr_facts_payload.zip/ansible_collections/frr/frr/plugins/modules/frr_facts.py\", line 410, in main\n File \"/tmp/ansible_frr.frr.frr_facts_payload_y1xygkr8/ansible_frr.frr.frr_facts_payload.zip/ansible_collections/frr/frr/plugins/modules/frr_facts.py\", line 134, in __init__\n File \"/tmp/ansible_frr.frr.frr_facts_payload_y1xygkr8/ansible_frr.frr.frr_facts_payload.zip/ansible_collections/frr/frr/plugins/module_utils/network/frr/frr.py\", line 18, in get_capabilities\n File \"/tmp/ansible_frr.frr.frr_facts_payload_y1xygkr8/ansible_frr.frr.frr_facts_payload.zip/ansible/module_utils/connection.py\", line 121, in __init__\nAssertionError: socket_path must be a value\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1} My Ansible playbook is: - name: testing facts hosts: routers tasks: - name: testing ansible.builtin.setup: gather_subset: - '!all' - '!any' - facter - name: Do not collect hardware facts frr.frr.frr_facts: gather_subset: - '!hardware' I read that Ansible FRR module uses SSH to communicate with the devices. However, I can't seem to ssh into the FRR router. Could that be the reason? How do I fix it? Thanks and best regards -- Saqib

2 1

How Impelemnt QOS For ip Prefix IN Frr-Routing
by Ramin Malekgahsemi 11 Jun '21

11 Jun '21

HI I Used For testing Frr For My Edge Router Now my Questions IS How limit My prefix-list OR ip-accesslist BW or apply Traffic shapping on it ? and How can apply Specify Inteface For example Centos 7 ( Frr-Routing Guest OS ) Another Question IS Can used Frr-routing (DNS recusive ) ??? Thanks

1 0

isis_tlvs.c : bugs in unpack_item_ext_subtlvs()
by himanshu sardana 10 Jun '21

10 Jun '21

Hi FRR team, File: https://github.com/FRRouting/frr/blob/master/isisd/isis_tlvs.c In unpack_item_ext_subtlvs() there are few sub-tlvs whose unpacking need to be fixed. Basically 2 fixes are required: 1. Default length of sub-tlvs are not correct 2. If length is not as per standard, then pointer has to be advanced to the length value. In below example, these 2 fixes are tagged as FIXME#1 and FIXME#2 For example: unpack_item_ext_subtlvs() { . . . . . . case ISIS_SUBTLV_MM_DELAY: if (subtlv_len != ISIS_SUBTLV_DEF_SIZE) { // FIXME#1: As per standard this is 8 byte sbuf_push(log, indent, "TLV size does not match expected size for Min/Max Link Delay!\n"); // FIXME#2: Advance the pointer to subtlv_len i.e. uncomment below line and add it in the code // stream_forward_getp(s, subtlv_len); } . . . . . . } Note: In unpack_item_ext_subtlvs(), there are other "case" as well that needs the same 2 fix Thanks, Himanshu Rai

1 0

bgp6 routes out of sync with kernel (7.2.1)
by Rudy Rucker 10 Jun '21

10 Jun '21

I was seeing an odd issue where some IPv6 routes (mostly google) were not working in our network. We have two Arista edge routers and one FRR edge. Logging into bgpd, I shutdown all the bgp IPv6 sessions and then started them back up and our routing issue went away. We were running 7.2.1 and have since upgraded to 7.5.1 on FreeBSD 12.2. Uptime had been a while on the box and we were not even thinking about it (one of the reasons I like FRR). I didn't see anything odd in the logs. What would cause the FIB and bgpd demon to get out of sync? Other than shutting and restarting sessions is there a process that can validate kernel routes? Thanks, Rudy

1 0

Re: [FROG] QOS Policy
by jimc 10 Jun '21

10 Jun '21

On 2021-06-08 22:24, Ramin Malekgahsemi via frog wrote: > Hi Dear Firends I want Used Frr-routing For Policy and QOS and > shaping for edge of my network For example 1G bit For voip or ...... > frr Can impelement QOS and detect Traffic VOIP and other traffic ???? I think you're saying you want to allocate bandwidth to various services like VOIP. I'm just a newbie but I didn't see parameters for that in frr. You might be interested in my insights about handling that issue. Very quick summary: make sure VOIP gets priority to go out, but don't allocate; send out packets from the hog flows whenever there's nothing waiting in the quick response categories. Which are recognized not by their port, but because their bandwidth is low. https://www.jfcarter.net/~jimc/documents/voip-qos-1609.html -- James F. Carter Email: jimc(a)jfcarter.net Web: http://www.math.ucla.edu/~jimc (q.v. for PGP key)

1 0

QOS Policy
by Ramin Malekgahsemi 09 Jun '21

09 Jun '21

Hi Dear Firends I want Used Frr-routing For Policy and QOS and shaping for edge of my network For example 1G bit For voip or ...... frr Can impelement QOS and detect Traffic VOIP and other traffic ???? please Help me ? anothe question is Frr support neflow and slflow or ipfix ??

1 0

Using Northbound gPRC to configure BGP
by xingyeping＠163.com 03 Jun '21

03 Jun '21

Hi All. I'm trying to configure BGP with Northbound gPRC. I'm using a Golang client to send Json format configuration to BGPD and now I can send some configuration to BGPD，the question is I can't configure the "afi-safis"。The configuration is underneath： { "frr-routing:routing": { "control-plane-protocols": { "control-plane-protocol": [{ "type": "frr-bgp:bgp", "name": "bgp", "vrf": "default", "frr-bgp:bgp": { "global": { "local-as": 100, "router-id": "2.2.2.2", "afi-safis": { "afi-safi": [{ "afi-safi-name": "frr-routing:ipv4-unicast", "frr-routing:ipv4-unicast": { "network-config": [{ "prefix": "192.168.155.0/24" }, { "prefix": "192.168.166.0/16" }] } }] } }, "neighbors": { "neighbor": [{ "remote-address": "4.4.4.4", "neighbor-remote-as": { "remote-as-type": "as-specified", "remote-as": 100 } }] } } }] } } } The red part can't deliver to BGPD，and the log is： 2021/06/02 08:11:24 BGP: [SWK28-M149C] northbound callback: event [prepare] op [modify] xpath [/frr-routing:routing/control-plane-protocols/control-plane-protocol[type='frr-bgp:bgp'][name='bgp'][vrf='default']/frr-bgp:bgp/global/router-id] value [2.2.2.2] 2021/06/02 08:11:24 BGP: [SWK28-M149C] northbound callback: event [prepare] op [create] xpath [/frr-routing:routing/control-plane-protocols/control-plane-protocol[type='frr-bgp:bgp'][name='bgp'][vrf='default']/frr-bgp:bgp/global/afi-safis/afi-safi[afi-safi-name='frr-routing:ipv4-unicast']] value [(none)] 2021/06/02 08:11:24 BGP: [SWK28-M149C] northbound callback: event [prepare] op [create] xpath [/frr-routing:routing/control-plane-protocols/control-plane-protocol[type='frr-bgp:bgp'][name='bgp'][vrf='default']/frr-bgp:bgp/neighbors/neighbor[remote-address='4.4.4.4']] value [(none)] 2021/06/02 08:11:24 BGP: [SWK28-M149C] northbound callback: event [prepare] op [modify] xpath [/frr-routing:routing/control-plane-protocols/control-plane-protocol[type='frr-bgp:bgp'][name='bgp'][vrf='default']/frr-bgp:bgp/neighbors/neighbor[remote-address='4.4.4.4']/neighbor-remote-as/remote-as-type] value [as-specified] 2021/06/02 08:11:24 BGP: [SWK28-M149C] northbound callback: event [prepare] op [modify] xpath [/frr-routing:routing/control-plane-protocols/control-plane-protocol[type='frr-bgp:bgp'][name='bgp'][vrf='default']/frr-bgp:bgp/neighbors/neighbor[remote-address='4.4.4.4']/neighbor-remote-as/remote-as] value [100] I'm also tried to replace the "network-config" to "frr-bgp:network-config",but it's also does't work. Can anyone tell me the correct json format of "afi-safis"? Regards, Yeping Xing xingyeping(a)163.com

1 0