summaryrefslogtreecommitdiffstats
path: root/zebra
Commit message (Collapse)AuthorAgeFilesLines
...
| * Amir - revision 197paul2003-04-091-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Log: I've fixed a small bug in connected_down_ipv4(): I changed if (ifc_pointopoint (ifc)) into if (ifc_pointopoint (ifc) && dest) like show in connected_up_ipv4() After changing this 'ip address x/y'; 'no ip address x/y' works without crash when done in sequence.
| * Add Makefile.in to the remaining .cvsignore'spaul2003-04-091-0/+1
| | | | | | | | Add ospfclient to ospfclient/.cvsignore
| * [zebra 18626] move zebra socket paths to configure.acpaul2003-04-071-2/+0
| | | | | | | | | | | | | | | | | | | | | | moved definition of the various socket paths from the per daemon header files into configure.ac. it will set the paths to be in the directory specified by --localstatedir=<prefix> or otherwise will try to guess as best it can ( a la pid file path detection - which probably should try reference ${prefix} too). the present hardcoded socket path, /tmp, isnt really correct. should be in /var somewhere really.
| * Remove auto* files from the repository.paul2003-04-071-408/+0
| | | | | | | | | | | | | | | | | | Developers working with the repository should have the appropriate tools. Out-of-sync files cause far too many problems with users as well as auto* scripts not being half as portable across systems as they ought to be. make-dist exists for a reason. Todo: make the CVS snapshot script do make-dist, and use the resulting tarball as the snapshot.
| * 2003-03-25 Paul Jakma <paul@dishone.st>paul2003-03-251-181/+190
| | | | | | | | | | | | | | | | * sync to latest zebra CVS * spec file: updated and added define for ospf-api/client NB: OSPF-API has been broken by the zebra.org changes, which has added struct ospf * as a new arg to many functions
| * Fix build for net-snmppaul2003-03-181-81/+99
| |
| * Update auto files.paul2003-03-171-310/+216
| | | | | | | | No doubt builds will now break for everyone. (works here - autoconf 2.13)
| * Sync to Zebra.org 20030301paul2003-03-011-17/+159
| |
| * Sync to latest Zebra CVSpaul2003-02-071-0/+4
| |
| * Matthew Grant <grantma@anathoth.gen.nz>patch_z17290_portfixpaul2003-01-221-3/+10
| | | | | | | | | | | | [zebra 17290] [PATCHES] - Fixes for problems in 0.93b portfix patch
| * Matthew Grant <grantma@anathoth.gen.nz>patch_z17290_ifupstaticfixpaul2003-01-222-5/+38
| | | | | | | | | | | | Subject: [zebra 17290] [PATCHES] - Fixes for problems in 0.93b Added ifupstaticfix
| * Add work around for RFC3021 patch and its problem with certain IPv6 interfacesrfc3021-ipv6-fixpaul2003-01-191-1/+6
| | | | | | | | | | | | | | | | | | addresses. It seems so far that netlink only ever returns IFA_ADDRESS for IPv6 interfaces and never IFA_LOCAL, regardless of whether it is PtP or not. Need to investigate precisely how IPv6 and netlink are supposed to behave wrt broadcast vs PtP links.
| * From havanna_moon@gmx.net Fri Jan 17 23:37:49 2003patch_z17217_show_thread_cpupaul2003-01-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Date: Sat, 11 Jan 2003 23:26:28 +0100 (CET) From: Yon Uriarte <havanna_moon@gmx.net> To: "the list(tm) Zebra" <zebra@zebra.org> Subject: [zebra 17217] [PATCH] show thread CPU Hi, a little patch from the 'stupid preprocessor tricks' collection to record thread statistics. Usage: "show thread cpu [r][w][t][e][x]" Output Fields: self explaining I hope. Type is one of RWTEX for: Read, Write (fd threads), Timer, Event, Execute. Overhead vs. vanilla zebra: almost nothing. Vanilla CVS zebra already collects thread run times. Caveats: Under linux getrusage has a granularity of 10ms, which is almost useless in this case. Run ./configure, edit config.h and comment out "#define HAVE_RUSAGE", this way it will use getimeofday which has a much better granularity. IMHO this is better, as cooperative threads are effectively running during all that wall time (dont care if CPU utilization was 3% or 99% during the time the thread was running (an effective rusage combined with getimeofday could give that info)). Maybe someone can give tips for other platforms on API granularity. TODO: change some of the calls to thread_add_$KIND to funcname_thread_add_$KIND with a meaningfull funcname, so users will get a better idea of what's going on. F.ex. (AFAIK): ospf_spf_calculate_timer -> "Routes Step 1, areas SPF" ospf_ase_calculate_timer -> "Routes Step 2, externals" Could this be added to the unofficial patch collection? Could someone with BGP keepalive problems run their bgpd with this patch and post the results? TIA, HTH, HAND, regards yon Example output: -------------------------------- ospfd# show thread cpu Runtime(ms) Invoked Avg uSecs Max uSecs Type Thread 14.829 31 478 585 T ospf_ase_calculate_timer 82.132 9838 8 291 EX ospf_nsm_event 0.029 1 29 29 E ospf_default_originate_timer 0.254 9 28 34 T ospf_db_desc_timer 0.026 7 3 11 T ospf_wait_timer 669.015 523 1279 490696 R vty_read 4.415 45 98 173 TE ospf_network_lsa_refresh_timer 15.026 31 484 588 T ospf_spf_calculate_timer 29.478 1593 18 122 E ospf_ls_upd_send_queue_event 0.173 1 173 173 T vty_timeout 4.173 242 17 58 E ospf_ls_ack_send_event 637.767 121223 5 55 T ospf_ls_ack_timer 39.373 244 161 2691 R zclient_read 12.169 98 124 726 EX ospf_ism_event 0.226 2 113 125 R vty_accept 537.776 14256 37 3813 W ospf_write 4.967 41 121 250 T ospf_router_lsa_timer 0.672 1 672 672 E zclient_connect 7.901 1658 4 26 T ospf_ls_req_timer 0.459 2 229 266 E ospf_external_lsa_originate_timer 3.203 60 53 305 T ospf_maxage_lsa_remover 108.341 9772 11 65 T ospf_ls_upd_timer 33.302 525 63 8628 W vty_flush 0.101 1 101 101 T ospf_router_lsa_update_timer 0.016 1 16 16 T ospf_router_id_update_timer 26.970 407 66 176 T ospf_lsa_maxage_walker 381.949 12244 31 69 T ospf_hello_timer 0.114 22 5 14 T ospf_inactivity_timer 34.290 1223 28 310 T ospf_lsa_refresh_walker 470.645 6592 71 665 R ospf_read 3119.791 180693 17 490696 RWTEX TOTAL ospfd# bgpd# sh t c TeX Runtime(ms) Invoked Avg uSecs Max uSecs Type Thread 21.504 476 45 71 T bgp_keepalive_timer 17.784 1157 15 131 T bgp_reuse_timer 29.080 193 150 249 T bgp_scan 23.606 995 23 420 E bgp_event 317.734 28572 11 69 T bgp_routeadv_timer 0.084 1 84 84 E zlookup_connect 0.526 1 526 526 E zclient_connect 1.348 13 103 147 T bgp_start_timer 19.443 142 136 420 T bgp_connect_timer 16.032 772 20 27 T bgp_import 447.141 32322 13 526 TEX TOTAL bgpd# bgpd# show thread cpu rw Runtime(ms) Invoked Avg uSecs Max uSecs Type Thread 155.043 7 22149 150659 R bgp_accept 129.638 180 720 53844 R vty_read 1.734 56 30 129 R zclient_read 0.255 2 127 148 R vty_accept 58.483 983 59 340 R bgp_read 171.495 29190 5 245 W bgp_write 13.884 181 76 2542 W vty_flush 530.532 30599 17 150659 RW TOTAL bgpd# --------------------------------
| * Kevin C Miller <kevinm@andrew.cmu.edu>patch_z16681_ospfd_nssapaul2002-12-131-1/+1
| | | | | | | | [zebra 16681] OSPF NSSA Patches
| * Michal Ludvig <michal@logix.cz>patch_z16525_kamepaul2002-12-131-11/+24
| | | | | | | | [zebra 16525] PATCH: Bugfixes for KAME systems
| * [zebra 14631] Generic PtP and RFC3021 interface addressing supportpatch_z14631_ptp_rfc3021paul2002-12-132-32/+44
| |
| * zebra link state detection supportpatch_z12269_linkstatepaul2002-12-133-14/+82
| |
| * patch from Frank van Maarseveen <F.vanMaarseveen@inter.NL.net>patch_z14599_multicast_inactive_ifpaul2002-12-131-11/+25
| | | | | | | | [zebra 14599] PATCH: permit [no]multicast command for (yet) inactive interfaces
| * Initial revisionpaul2002-12-1350-0/+19591
|
* Handle network interface renamesStephen Hemminger2008-07-311-35/+34
| | | | | | The interface index (rather than the name) is the primary key, so if name changes just update the record rather than doing a delete/update.
* Do link detect in quagga, rather than kernelStephen Hemminger2008-07-285-154/+3
| | | | | | Don't use kernel support for linkdetect in quagga. This reverts commit 8d95ee9f88945ee49932b1a9f7af5abe6048e6e6.
* Fix management of route changesStephen Hemminger2008-07-241-27/+45
| | | | | | | | Earlier changes to route management caused any route change to cause the whole RIB to marked as changed. This then causes route flapping. Fix by being more selective about what changes get flagged. Bugfix 3488
* Only set ifindex on set passStephen Hemminger2008-07-231-2/+2
| | | | This makes code work like comments and probable original design.
* Remove routes from FIB.Stephen Hemminger2008-07-171-17/+37
| | | | | | | | Earlier commit for Bug 3434 caused removed routes not to be marked as SELECTED. This caused them not to be removed. Fix is to always check both flags. Bugfix 3479
* Handle state transistions when there are multiple nexthopsStephen Hemminger2008-07-171-63/+53
| | | | | When multipath is being used, the state of one nexthop maybe down, but another one may be up.
* Update recursive route when nexthop changesStephen Hemminger2008-07-161-4/+7
| | | | | | | | This includes two fixes. First entries that are marked for removal should not be used (clear SELECTED flag). Also, when recursive route changes, the CHANGED flag needs to be set to force update. Bugfix 3434
* Merge extreme:vyatta/hollywood/vyatta-quagga into hollywoodStephen Hemminger2008-07-161-1/+1
|\
| * Minor typo in zebra debuggingStephen Hemminger2008-07-161-1/+1
| | | | | | | | The command to turn off zebra rib debugging was wrong.
* | Go back to hiding connected routes from down interfacesStephen Hemminger2008-07-161-1/+1
| | | | | | | | | | | | Revert "Revert "Only announce connected routes if link is detected"" This reverts commit 38701029fe978ca18645408771414a91588413d3.
* | Handle races with add/delete of routesStephen Hemminger2008-07-161-27/+20
|/ | | | | Adding a route that already exists, or deleting a route that is already gone, should not be an error.
* Revert "Only announce connected routes if link is detected"Stephen Hemminger2008-07-161-1/+1
| | | | | | Want to remember connected routes even if they aren't active at the current time. This reverts commit 84cc940a9b74d5a867a5598f4b0f6c657eb61c9c.
* Update RIB/FIB on recursive route state changesStephen Hemminger2008-07-151-37/+50
| | | | | | | | If a link state change event causes a different nexthop, then the RIB (and FIB) need to be updated. Solved by forcing the CHANGED flag. This code could be rearranged to be cleaner in future. Bugfix 3434
* Rescan for next hops after static route changeStephen Hemminger2008-07-091-0/+9
| | | | | Bugfix 3433, 3434 Need to rescan for recursive routes after any change to static route.
* active static route changes for ipv6Stephen Hemminger2008-07-071-11/+17
| | | | | This is the IPV6 analog to earlier changes to IPV4 static route management.
* Correctly identify/manage all connected static routesStephen Hemminger2008-07-051-10/+17
| | | | | | | Need to handle all the different flavors of connected routes in linkstate management Bugfix: 2904, 3416
* Make some rib data structures privateStephen Hemminger2008-07-051-2/+2
| | | | | The route_info table can be static const, and the vrf_table can be static.
* Only announce connected routes if link is detectedStephen Hemminger2008-07-051-1/+1
| | | | | Need to check both IFF_UP and IFF_RUNNING if link-detect is enabled, before announcing routes.
* Revert "Backout all changes related to using kernel for linkdetect"Stephen Hemminger2008-06-205-3/+154
| | | | | This reverts commit a182091782d22218942466b062c5ef2406853491. More changes that should NOT go into hollywood
* Revert "Use if_flags_update"Stephen Hemminger2008-06-201-1/+15
| | | | | This reverts commit 17cf20dabb137205497d81f7c55efa45a4e50748. Stuff for next release snuck into hollywood branch
* Use if_flags_updateStephen Hemminger2008-06-201-15/+1
|
* Backout all changes related to using kernel for linkdetectStephen Hemminger2008-06-205-154/+3
| | | | | | | | Having kernel cleanup FIB was not ideal for a couple reasons: 1. It still generates lots of netlink events if there are lots of static routes. 2. Kernel changes were not accepted in mainline kernel "do it in userspace"
* netlink interface minor stuffStephen Hemminger2008-05-283-23/+20
| | | | Add more prototypes and make some functions static
* get rid of duplicate includesStephen Hemminger2008-05-281-3/+0
| | | | included same file twice
* Fix compiler warningsStephen Hemminger2008-05-284-5/+14
| | | | | | | | To eliminate compiler warnings * comment out unused code * fix printf formats * remove always true expression * initialize variables
* Add ipv6 link detect hooksStephen Hemminger2008-05-284-4/+44
| | | | Enable ipv6 link detect in kernel if needed.
* Change how link-detect is configured in buildStephen Hemminger2008-05-271-2/+1
| | | | | Rather that looking for /proc/sys/net/ipv4/conf, use --enable-linkdetect flag to configure.
* Turn on kernel link-detectStephen Hemminger2008-05-225-3/+118
| | | | | If interface has link-detect enabled, try and turn on link-detect in the kernel.
* only set non-blocking on netlink socketStephen Hemminger2008-05-191-133/+50
| | | | | | There is no need to increase buffer size or set non-blocking on the netlink command socket. This reduces the number of system calls per transaction.
* remove unneeded privledge changesStephen Hemminger2008-05-191-12/+3
| | | | | | Netlink recvmsg always succeeds, there are no permission checks in the kernel on receive, only on send and bind. This reduces the number of system calls and any potential security vulnerabilty in recvmsg().
* Merge branch 'hollywood' of suva.vyatta.com:/git/vyatta-quagga into hollywoodStephen Hemminger2008-05-152-29/+34
|\
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 18:48:51 +0000