1. 14 Mar, 2009 3 commits
  2. 13 Mar, 2009 2 commits
  3. 05 Mar, 2009 1 commit
  4. 27 Feb, 2009 1 commit
    • Ondřej Zajíček's avatar
      Better handling of too long attributes · 82a79586
      Ondřej Zajíček authored
      This patch extends the length for attributes from 1024 to 2048
      (because both AS_PATH and AS4_PATH attributes take 2+4 B per AS).
      If there is not enough space for attributes, Bird skips that
      route group. Old behavior (skipping remaining attributes)
      leads to skipping required attributes and session drop.
  5. 26 Feb, 2009 1 commit
  6. 25 Feb, 2009 1 commit
  7. 21 Feb, 2009 3 commits
  8. 12 Feb, 2009 4 commits
  9. 27 Jan, 2009 1 commit
  10. 16 Jan, 2009 3 commits
  11. 13 Jan, 2009 2 commits
    • Ondřej Zajíček's avatar
      Fix typo. · 0dd7ccc7
      Ondřej Zajíček authored
    • Ondřej Zajíček's avatar
      Fix OSPF protocol error recovery behavior. · 0844b65d
      Ondřej Zajíček authored
      When OSPF neighbor state drops down to EXSTART,
      clear LSA request and retransmit lists, as specified
      by RFC. I hope that this will prevent oscillations
      between EXSTART and LOADING states, which sometimes
      It also contains related fix from Yury Shevchuk that
      properly resets DB summary list iterator.
  12. 12 Jan, 2009 2 commits
  13. 11 Jan, 2009 3 commits
  14. 25 Dec, 2008 2 commits
    • Ondřej Zajíček's avatar
      Bugfix in interpret · 330aecea
      Ondřej Zajíček authored
      Missing cases in filter code interpret leads to crash
      when  bgp_next_hop attr was queried.
    • Ondřej Zajíček's avatar
      fixes some 64-bit related bugs. · 083c43e2
      Ondřej Zajíček authored
      Filter code used 'aux' integer field of 'symbol' struct to store ptr
      to next symbol and both 'aux2' and 'def' fields for value.
      Changed to just 'def' for value and 'aux2' for ptr to next symbol.
      Also another minor bugfix.
  15. 24 Dec, 2008 2 commits
    • Ondřej Zajíček's avatar
      Adds support for fallback to capabilityless BGP connect · 165a6227
      Ondřej Zajíček authored
      When capability related error is received, next connect will be
      without capabilities. Also cease error subcodes descriptions
      (according to [RFC4486]) are added.
    • Ondřej Zajíček's avatar
      Fixes bug related to reconfiguration of BGP. · 59121155
      Ondřej Zajíček authored
      BGP keeps its copy of configuration ptr and didn't update it during
      reconfiguration. But old configuration is freed during reconfiguration.
      That leads to unnecessary reset of BGP connection during reconfiguration
      (old conf is corrupted and therefore different) and possibly other strange
  16. 19 Dec, 2008 1 commit
    • Ondřej Zajíček's avatar
      Major changes to BGP · 11b32d91
      Ondřej Zajíček authored
      Fixes two race conditions causing crash of Bird, several unhandled
      cases during BGP initialization, and some other bugs. Also changes
      handling of startup delay to be more useful and implement
      reporting of last error in 'show protocols' command.
  17. 18 Dec, 2008 1 commit
    • Ondřej Zajíček's avatar
      Fixes nasty bug in event processing. · b933281e
      Ondřej Zajíček authored
      WALK_LIST_DELSAFE (in ev_run_list) is not safe with regard
      to deletion of next node. When some events are rescheduled
      during event execution, it may lead to deletion of next
      node and some events are skipped. Such skipped nodes remain
      in temporary list on stack and the last of them contains
      'next' pointer to stack area. When this event is later
      scheduled, it damages stack area trying to remove it from
      the list, which leads to random crashes with funny
      backtraces :-) .
  18. 12 Dec, 2008 1 commit
  19. 08 Dec, 2008 1 commit
    • Ondřej Zajíček's avatar
      Fixes core state machine. · d6a836f8
      Ondřej Zajíček authored
      The core state machine was broken - it didn't free resources
      in START -> DOWN transition and might freed resources after
      UP -> STOP transition before protocol turned down. It leads
      to deadlock on olock acquisition when lock was not freed
      during previous stop.
      The current behavior is that resources, allocated during
      DOWN -> * transition, are freed in * -> DOWN transition,
      and flushing (scheduled in UP -> *) just counteract
      feeding (scheduled in * -> UP). Protocol fell down
      when both flushing is done (if needed) and protocol
      reports DOWN.
      BTW, is thera a reason why neighbour cache item acquired
      by protocol is not tracked by resource mechanism?
  20. 22 Nov, 2008 1 commit
    • Ondřej Zajíček's avatar
      Fixes race condition leading to memory corruption and crash. · fbde6c39
      Ondřej Zajíček authored
      When protocol started, feeding was scheduled. If protocol
      got down before feeding was executed, then function
      responsible for connecting protocol to kernel routing
      tables was called after the function responsible for
      disconnecting, then resource pool of protocol was freed,
      but freed linked list structures remains in the list.
  21. 21 Nov, 2008 4 commits