summaryrefslogtreecommitdiffstats
path: root/bgpd/bgp_ecommunity.h (unfollow)
Commit message (Collapse)AuthorFilesLines
2019-08-21isisd: reuse the nexthop lookup functions to avoid code duplicationRenato Westphal1-24/+19
Nothing special here. Signed-off-by: Renato Westphal <renato@opensourcerouting.org>
2019-08-21isisd: remove unnecessary null checksRenato Westphal1-4/+2
These null checks don't make sense because a) these two functions are never called with a NULL IP address and b) the same pointers are dereferenced later without any protection. Remove these NULL checks to make the code less confusing. Signed-off-by: Renato Westphal <renato@opensourcerouting.org>
2019-08-21isisd: remove unused struct fieldsRenato Westphal2-4/+0
These fields were introduced by commit e38e0df01ad, but they were never put to any use. Remove them. Signed-off-by: Renato Westphal <renato@opensourcerouting.org>
2019-08-20bgpd: Remove declarations of unused functionsDonald Sharp1-3/+0
Code inspection found some functions being declared in a .h file but FRR does not have the functions implemented. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
2019-08-19pbrd, sharpd, staticd: Add some color to sample configuration filesDonald Sharp3-1/+22
The sample configuration files for pbrd, sharpd and staticd where all the same. Add some bit of color to help new people get rolling on these three daemons. Signed-off-by: Donald Sharp <sharpd@cumulusnetwork.com>
2019-08-19*: Fix spelling errors pointed out by debian packagingDonald Sharp14-33/+33
Debian packaging when run finds a bunch of spelling errors: I: frr: spelling-error-in-binary usr/bin/vtysh occurences occurrences I: frr: spelling-error-in-binary usr/lib/frr/bfdd Amount of times Number of times I: frr: spelling-error-in-binary usr/lib/frr/bgpd occurences occurrences I: frr: spelling-error-in-binary usr/lib/frr/bgpd recieved received I: frr: spelling-error-in-binary usr/lib/frr/isisd betweeen between I: frr: spelling-error-in-binary usr/lib/frr/ospf6d Infomation Information I: frr: spelling-error-in-binary usr/lib/frr/ospfd missmatch mismatch I: frr: spelling-error-in-binary usr/lib/frr/pimd bootsrap bootstrap I: frr: spelling-error-in-binary usr/lib/frr/pimd Unknwon Unknown I: frr: spelling-error-in-binary usr/lib/frr/zebra Requsted Requested I: frr: spelling-error-in-binary usr/lib/frr/zebra uknown unknown I: frr: spelling-error-in-binary usr/lib/x86_64-linux-gnu/frr/libfrr.so.0.0.0 overriden overridden This commit fixes all of them except the bgp `recieved` issue due to it being part of json output. That one will need to go through a deprecation cycle. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
2019-08-19bgpd: Display peer info in NHT outputvivek1-2/+11
When a BGP next hop tracking (NHT) entry is created for a peer, display it in the corresponding "show" command output. Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com> Reviewed-by: Donald Sharp <sharpd@cumulusnetworks.com>
2019-08-19bgpd: Fix nexthop reg for IPv4 route exchange using GUA IPv6 peeringvivek1-12/+24
In the case of IPv4 route exchange using GUA IPv6 peering, the route install into the FIB involves mapping the immediate next hop to an IPv4 link-local address and installing neighbor entries for this next hop address. To accomplish the latter, IPv6 Router Advertisements are exchanged (the next hop or peer must also have this enabled) and the RAs are dynamically initiated based on next hop resolution. However, in the case of a passive connection where the local system has not initiated anything, no NHT entry is created for the peer, hence RAs were not getting triggered. Address this by ensuring that a NHT entry is created even in this situation. This is done at the time the connection becomes established because the code has other assumptions that a NHT entry will be present only for the "configured" peer. The API to create the entry ensures there are no duplicates. Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com> Reviewed-by: Donald Sharp <sharpd@cumulusnetworks.com>
2019-08-16isisd: fix display of the "isis bfd" commandRenato Westphal1-1/+1
We need to indent this command using one leading whitespace otherwise vtysh will have problems to display it appropriately. Signed-off-by: Renato Westphal <renato@opensourcerouting.org>
2019-08-16bgpd: fix bgp_table range lookupMarcel Röthke3-8/+10
In case the topmost node has a larger prefix length than the lookup prefix it never matches even if it was still lower than maxlen This also alters a test case to check for this bug. Signed-off-by: Marcel Röthke <marcel.roethke@haw-hamburg.de>
2019-08-16bgpd: remove initial sync timeout in rpki startup codeMarcel Röthke1-21/+1
The initial sync timeout breaks config load and is not necessary anyway. Fix #4827 Signed-off-by: Marcel Röthke <marcel.roethke@haw-hamburg.de>
2019-08-14bgpd: Display the imported route information for EVPN routesDinesh Dutt1-11/+19
For IPv4/v6 unicast routes that have been imported from EVPN Prefix routes, display the information about where the route has been imported from allowing for easy tracing of how a FIB/RIB entry got populated. Signed-off-by: Dinesh G Dutt <5016467+ddutt@users.noreply.github.com>
2019-08-14ospfd: add redist message detail to debugMark Stapp1-1/+2
Add the specific message being processed when ospfd receives a redistribution from zebra. Signed-off-by: Mark Stapp <mjs@voltanet.io>
2019-08-14zebra : zebra redistributing IPV4 link local Addresses inconsistently.vdhingra1-0/+14
Create an interface with IP4 link local address 169.254.0.131/25. In BGP enable the redistribute connected. Now Zebra will not send the route corresponding to IPV4 link local address. Now made this interface down and up. Zebra sends the route to BGP. Zebra should not send this route to BGP. This Fix would make the behaviour consistent and would not send the routes corresponding to IPV4 Link local addresses. Signed-off-by: vishaldhingra <vdhingra@vmware.com>
2019-08-14build: add check for python-3.8Michal Ruprich1-1/+5
In python-3.8, the --embed needs to be added to pythonX.Y-config Signed-off-by: Michal Ruprich <michalruprich@gmail.com>
2019-08-13zebra: Ensure master's ifname is known, even if slave comes up firstDinesh G Dutt5-15/+93
In if_netlink.c, when an interface structure, ifp, is first created, its possible for the master to come up after the slave interface does. This means, the slave interface has no way to display the master's ifname in show outputs. To fix this, we need to allow creation by ifindex instead of by ifname so that this issue is handled. Signed-off-by: Dinesh G Dutt<5016467+ddutt@users.noreply.github.com>
2019-08-13 zebra: Display master interface names, not ifindicesDinesh G Dutt1-9/+18
When displaying the master interface's information in "show interface", the display is currently the ifindex of the master interface. Make it display the name as well as that is more useful than the name. Signed-off-by: Dinesh G Dutt<5016467+ddutt@users.noreply.github.com>
2019-08-13zebra : blackhole_type was not set correctly in recursive routesvdhingra1-1/+1
If there is a recursive route resolved over blackhole route, then the resolved blackhole_type is not getting set correctly. This fix updates the bh_type correctly for resursive routes. Signed-off-by: vishaldhingra <vdhingra@vmware.com>
2019-08-12zebra: make the dplane pthread name consistentMark Stapp1-1/+1
Make the dplane pthread's name consistent (lower-case) with other pthreads. Signed-off-by: Mark Stapp <mjs@voltanet.io>
2019-08-12bgpd: Optimizing route-map's processing of dependencies.Naveen Thanikachalam1-23/+26
Say for eg., 256 prefix-list entries are pasted to VTYSH. This results in BGP processing the events for several minutes. BGPD starts a timer for 5 seconds when the first dependency configuraion is received. On timer expiry, BGP process dependent route-maps. After this processing, BGPD reads the configurations received in the next 5 seconds and then re-processes the route-maps from the beginning. This cyclic re-processing consumes time and CPU cycles. Instead of starting a timer when the first configuration is received, everytime a configuration is received, the existing timer is reset. This would mean that all the configurations are read first before the timer expires. This eliminates the cyclic re-processing. Signed-off-by: NaveenThanikachalam nthanikachal@vmware.com
2019-08-11bgpd: Assertion failed during shutdown.Naveen Thanikachalam1-0/+7
A race condition causes the failure. The function "make_info()" sets the path info's peer to bgp instance's "peer_self" which is created when BGP is first configured and deleted only when BGP is brought down completely. A race condition causes the bgp instances's "peer_self" to be removed before the routes are being pulled off from the aggregate address. If the bgp instance's "peer_self" is NULL or, if BGP is being deleted, the aggregate route must not be reinstalled. Signed-off-by: NaveenThanikachalam nthanikachal@vmware.com
2019-08-11bgpd: Standard large-communities CLI does not return error when it's ↵Naveen Thanikachalam1-2/+4
configured with reg-ex. The CLI to configure the standard format large-communities attribute accepts regular expressions as well. For ex., the below configuration is accepted. "bgp large-community-list standard TEST permit 1:1 100:*" The code to parse the large-communities does identify the configuration as invalid however, error returned isn't processed. The code has to be modified to handle the error. Signed-off-by: NaveenThanikachalam nthanikachal@vmware.com
2019-08-10Zebra: Incorrect L3VNI for FPM rtmsg for EVPN RT-5 prefixAmeya Dharkar1-1/+1
We used the vrf_id in the rtm_table field of the netlink rtmsg to fetch L3VNI. But, now we program table_id to rtm_table field instead of vrf_id. Thus, L3VNI fetched using rtm_table is incorrect. Instead, use nexthop->vrf_id to fetch the L3VNI. Signed-off-by: Ameya Dharkar <adharkar@vmware.com>
2019-08-08zebra: fix advertise svi ip as macip routeChirag Shah1-11/+24
PR #3745 added EVPN feature to advertise individual SVI-IPs as MAC-IP routes. Fix a condition in zebra to send MAC and IP pair to bgpd when the feature is enabled. Testing Done: Originator VTEP: TORC11:~# ip -br addr show VxU-1002 VxU-1002 UP 45.0.2.2/24 2001:fee1:0:2::2/64 show bgp l2vpn evpn vni 1004 VNI: 1004 (known to the kernel) Type: L2 Tenant-Vrf: default RD: 27.0.0.11:3 Advertise-svi-macip : Yes Import Route Target: 10:1004 Export Route Target: 10:1004 Remote vtep evpn route output for 45.0.4.2: BGP routing table entry for 27.0.0.11:3:[2]:[0]:[48]:[00:02:00:00:00:2f]:[32]:[45.0.4.2] Paths: (2 available, best #1) Advertised to non peer-group peers: MSP1(uplink-1) MSP2(uplink-2) Route [2]:[0]:[48]:[00:02:00:00:00:2f]:[32]:[45.0.4.2] VNI 1004 64435 65546 36.0.0.11 from MSP1(uplink-1) (27.0.0.9) Origin IGP, valid, external, bestpath-from-AS 64435, best (First path received) Extended Community: RT:10:1004 ET:8 Last update: Thu Aug 8 18:09:13 2019 Signed-off-by: Chirag Shah <chirag@cumulusnetworks.com>
2019-08-08ospfd,ripd: Enabling build with opensslMichal Ruprich4-0/+78
Enabling openssl library for md5 authentication in RIP and OSPF Signed-off-by: Michal Ruprich <michalruprich@gmail.com>
2019-08-08bgpd: Display received and advertised EVPN routes from neighborsDinesh Dutt5-116/+175
"show bgp l2vpn evpn neighbors <neighbor> [advertised-routes|routes]' did not work due to various bugs. First, the command only accepted IPv4 addresses as valid neighbor ID, thereby rejecting unnumbered BGP and IPv6 neighbor address. Second, the SAFI was hardcoded to MPLS_VPN even though we were passing the safi. Third, "all" made no sense in the command context and to make the command uniform across all address families, I removed the "all" keyword from the command. Signed-off-by: Dinesh G Dutt <ddps4u@gmail.com>
2019-08-08staticd: Fix blackhole routes being installedDonald Sharp4-3/+50
When we are ready to install a route, we were treating blackhole routes as something that should be nexthop tracked which does not work as well as one would expect. Additionally add some test code to show that this actually fixes this issue. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
2019-08-07zebra: Allow v4 or v6 addresses to be optional after `vrf X` in show ip nhtDonald Sharp1-1/+1
The `show ip nht vrf EVA ...` command was not allowing you to only specify the vrf anymore. Fix this: robot# show ip nht vrf EVA <cr> A.B.C.D IPv4 Address X:X::X:X IPv6 Address robot# show ip nht vrf EVA 4.5.6.7 robot# show ip nht vrf EVA robot# Ticket: CM-25831 Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
2019-08-06bgpd: tx addpath info for labeled unicastQuentin Young3-4/+16
Labeled unicast needs path IDs too! Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>
2019-08-06docs: Add notes about limited MPLS-TE supportMark Stapp5-20/+40
Add notes to several docs about the limits to FRR's current MPLS-TE support, which is limited to some routing protocol LSA/TLV support. It wasn't very clear that FRR does not offer a complete TE/RSVP-TE solution at this time. Also removed some stale info about configure script options. Signed-off-by: Mark Stapp <mjs@voltanet.io>
2019-08-06doc: suggest the installation of the libcap development libraryRenato Westphal8-8/+8
All FRR Linux packages are built using libcap-dev (or libcap-devel) installed in the system. Update the build instructions to suggest FRR developers to do the same. The main motivation for this is that the seteuid() system call is too expensive and overall less secure compared to using the Linux capabilities framework. Signed-off-by: Renato Westphal <renato@opensourcerouting.org>