1. 07 Dec, 2017 23 commits
  2. 17 Oct, 2017 1 commit
  3. 10 Oct, 2017 4 commits
  4. 09 Aug, 2017 4 commits
  5. 04 Aug, 2017 1 commit
  6. 04 Jul, 2017 1 commit
    • Ondřej Zajíček's avatar
      Implement onlink flag for nexthops · a1f5e514
      Ondřej Zajíček authored
      Add proper support for per-nexthop onlink flag in routes to handle next
      hop addresses that are not covered by interface IP ranges. Supported by
      kernel and static protocols.
      
      Thanks to Vincent Bernat for the idea.
      a1f5e514
  7. 14 Jun, 2017 1 commit
  8. 09 Jun, 2017 2 commits
    • Ondřej Zajíček's avatar
      Babel: Parse sub-TLVs and skip TLVs with mandatory sub-TLV · 145ebfa1
      Ondřej Zajíček authored
      RFC6126bis formally introduces sub-TLVs to the Babel protocol, including
      mandatory sub-TLVs. This adds support for parsing sub-TLVs to the Babel
      protocol and skips TLVs that contain mandatory sub-TLVs, as per the spec.
      
      For details, see section 4.4 of
      https://tools.ietf.org/html/draft-ietf-babel-rfc6126bis-02
      
      Thanks to Toke Høiland-Jørgensen <toke@toke.dk> for the patch.
      145ebfa1
    • Ondřej Zajíček's avatar
      Babel: Implement IPv6 prefix compression on outgoing updates · b3c6273e
      Ondřej Zajíček authored
      Previously, the Babel protocol would never use prefix compression on outgoing
      updates (but would parse it on incoming ones). This adds compression of IPv6
      addresses of outgoing updates.
      
      The compression only works to the extent that the FIB is walked in lexicographic
      order; i.e. a prefix is only compressed if it shares bytes with the previous
      prefix in the same packet.
      
      Thanks to Toke Høiland-Jørgensen <toke@toke.dk> for the patch.
      b3c6273e
  9. 08 Jun, 2017 1 commit
    • Ondřej Zajíček's avatar
      Babel: Add support for dual-stack IPv4/IPv6 operation · 4324025f
      Ondřej Zajíček authored
      This adds support for dual-stack v4/v6 operation to the Babel protocol.
      Routing messages will be exchanged over IPv6, but IPv4 routes can be
      carried in the messages being exchanged. This matches how the reference
      Babel implementation (babeld) works.
      
      The nexthop address for v4 can be configured per interface, and will
      default to the first available IPv4 address on the given interface. For
      symmetry, a configuration option to configure the IPv6 nexthop address
      is also added.
      
      Thanks to Toke Høiland-Jørgensen <toke@toke.dk> for the patch.
      4324025f
  10. 23 May, 2017 2 commits