- frog - lists.frrouting.org

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

10 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 09 Jun '21

09 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 09 Jun '21

09 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

Coredump file with FRR daemons
by jagadeesh N 01 Jun '21

01 Jun '21

Hi All, I'm trying to get the core dump generation in FRR daemons running with non-root user permissions, i sent signal 11 to the daemon process, although stacktrace in the log is printed, the core dump is not generated. After some research I found that, after *PR_SET_DUMPABLE* is enabled, *core dump file is generated* along with that mini dump file is also generated I've few questions related to that 1> Is there a better way to enable core dumps in FRrouting? like any configuration parameters 2> Please point me to code reference where breakpad/crashpad is integrated in FRR Regards, Jagadeesh N

1 0

frr-7.0-10.el8.x86_64 bgpd - updates
by Steve Clark 30 Apr '21

30 Apr '21

I found a version of quagga-1.2.4-2.el8.x86_64.rpm from redhat that worked fine when I replace frr with it. Hello, I am trying to get frr-7.0-10.el8.x86_64 bgp to connect to quagga-0.99.22.4-1.el6.x86_64 and it isn't working. I have no problem with the same bgpd.conf files when just using quagga. in a tcpdump on the frr side i see this error ... length 21: BGP Notification Message (3), length: 21, Finite State Machine Error (5) subcode Unknown (0) this what i see on the frr side Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.9.0.4 4 65004 0 0 0 0 0 never Active this is what i see on the quagga side Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.9.0.1 4 65001 39 41 0 0 0 00:45:53 Idle any thoughts ? -- Stephen Clark Email Confidentiality Notice: The information contained in this transmission may contain privileged and confidential and/or protected health information (PHI) and may be subject to protection under the law, including the Health Insurance Portability and Accountability Act of 1996, as amended (HIPAA). This transmission is intended for the sole use of the individual or entity to whom it is addressed. If you are not the intended recipient, you are notified that any use, dissemination, distribution, printing or copying of this transmission is strictly prohibited and may subject you to criminal or civil penalties. If you have received this transmission in error, please contact the sender immediately and delete this email and any attachments from any computer. Vaso Corporation and its subsidiary companies are not responsible for data leaks that result from email messages received that contain privileged and confidential and/or protected health information (PHI).

1 0

frr-7.0-10.el8.x86_64 bgpd
by Steve Clark 30 Apr '21

30 Apr '21

Hello, I am trying to get frr-7.0-10.el8.x86_64 bgp to connect to quagga-0.99.22.4-1.el6.x86_64 and it isn't working. I have no problem with the same bgpd.conf files when just using quagga. in a tcpdump on the frr side i see this error ... length 21: BGP Notification Message (3), length: 21, Finite State Machine Error (5) subcode Unknown (0) this what i see on the frr side Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.9.0.4 4 65004 0 0 0 0 0 never Active this is what i see on the quagga side Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.9.0.1 4 65001 39 41 0 0 0 00:45:53 Idle any thoughts ? -- Stephen Clark Email Confidentiality Notice: The information contained in this transmission may contain privileged and confidential and/or protected health information (PHI) and may be subject to protection under the law, including the Health Insurance Portability and Accountability Act of 1996, as amended (HIPAA). This transmission is intended for the sole use of the individual or entity to whom it is addressed. If you are not the intended recipient, you are notified that any use, dissemination, distribution, printing or copying of this transmission is strictly prohibited and may subject you to criminal or civil penalties. If you have received this transmission in error, please contact the sender immediately and delete this email and any attachments from any computer. Vaso Corporation and its subsidiary companies are not responsible for data leaks that result from email messages received that contain privileged and confidential and/or protected health information (PHI).

1 0

frr docker latest /etc/frr is a file
by 0xbabaf00l 28 Apr '21

28 Apr '21

Hi list, I pulled the frr docker image frrouting/frr:latest today, but I was unable to start it with a volume for /etc/frr. /etc/frr is a file (daemons file) and not a directory: # docker run -it frrouting/frr:latest ls -l /etc/frr WARNING: IPv4 forwarding is disabled. Networking will not work. -rw-r--r-- 1 root root 2619 Apr 28 05:42 /etc/frr # docker image ls REPOSITORY TAG IMAGE ID CREATED SIZE frrouting/frr latest 853e0587cf40 5 hours ago 145MB Is this intended or a bug? Thanks. Cheers, Sascha

1 0