quagga/zebra, branch isis-redist Quagga routing suite lib/command.c: rewrite command matching/parsing 2014-01-07T23:49:41+00:00 Christian Franke chris@opensourcerouting.org 2013-09-16T19:23:57+00:00 fdc8614c306e5b61224d1ab4b63c00c558dbb07e Add support for keyword commands. Signed-off-by: Christian Franke <chris@opensourcerouting.org> 
Add support for keyword commands.

Signed-off-by: Christian Franke <chris@opensourcerouting.org>
bgpd,ospfd,zebra: fix some DEFUN definitions 2014-01-07T23:49:41+00:00 Christian Franke chris@opensourcerouting.org 2013-09-16T19:20:38+00:00 54bd777005ffd9851b6fe07de78ab728f4b0f4cc Fixup some DEFUNS with incorrect command strings or mixed up helpstrings. Signed-off-by: Christian Franke <chris@opensourcerouting.org> 
Fixup some DEFUNS with incorrect command strings or mixed up helpstrings.

Signed-off-by: Christian Franke <chris@opensourcerouting.org>
zebra: make rib_dump() compatible with IPv6 RIB 2013-10-22T17:38:35+00:00 Vincent Bernat bernat@luffy.cx 2012-10-23T16:00:42+00:00 fed643f4093abc0ed5e796aab9047768f7036ed6 [DL: resolved conflicts in zebra_rib.c] [DL: fix usage with --disable-ipv6] Signed-off-by: David Lamparter <equinox@opensourcerouting.org> 
[DL: resolved conflicts in zebra_rib.c]
[DL: fix usage with --disable-ipv6]
Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
zebra: apply route-maps for interface routes 2013-09-19T16:04:40+00:00 Christian Franke chris@opensourcerouting.org 2013-07-05T15:35:41+00:00 f3a1732eb3bb41c094ec558d2aeee2766878a91d Signed-off-by: Christian Franke <chris@opensourcerouting.org> Signed-off-by: David Lamparter <equinox@opensourcerouting.org> 
Signed-off-by: Christian Franke <chris@opensourcerouting.org>
Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
zebra: fix recursive-routes via ifindex routes 2013-09-19T16:04:40+00:00 Christian Franke chris@opensourcerouting.org 2013-07-05T15:35:40+00:00 c3e6b595160cd3aa601ae7e1887e695710cde15d Signed-off-by: Christian Franke <chris@opensourcerouting.org> Signed-off-by: David Lamparter <equinox@opensourcerouting.org> 
Signed-off-by: Christian Franke <chris@opensourcerouting.org>
Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
zebra: implement NEXTHOP_FLAG_ONLINK 2013-09-19T16:04:40+00:00 Christian Franke chris@opensourcerouting.org 2013-07-05T15:35:39+00:00 e8d3d2991f72613edb76dea244a8c8e4684873dd On Linux, the kernel will only allow for a route to be installed when its gateway is directly attached according the kernel fib. There are cases when this restriction by the kernel is too strong, in those cases, we deploy the RTNH_F_ONLINK netlink flag. Signed-off-by: Christian Franke <chris@opensourcerouting.org> Signed-off-by: David Lamparter <equinox@opensourcerouting.org> 
On Linux, the kernel will only allow for a route to be installed when
its gateway is directly attached according the kernel fib.

There are cases when this restriction by the kernel is too strong, in
those cases, we deploy the RTNH_F_ONLINK netlink flag.

Signed-off-by: Christian Franke <chris@opensourcerouting.org>
Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
zebra: handle blackholes encountered in recursive resolution 2013-09-19T16:04:40+00:00 Christian Franke chris@opensourcerouting.org 2013-07-05T15:35:38+00:00 48a53dc71cb422e619859b79d5069e02fcd867d0 Signed-off-by: Christian Franke <chris@opensourcerouting.org> Signed-off-by: David Lamparter <equinox@opensourcerouting.org> 
Signed-off-by: Christian Franke <chris@opensourcerouting.org>
Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
zebra: rework recursive route resolution 2013-09-19T16:04:40+00:00 Christian Franke chris@opensourcerouting.org 2013-07-05T15:35:37+00:00 fa713d9ee5ed30dedd0a290be9aaff780a2896be Change the datastructure for recursive routes. This brings the following benefits: By using struct nexthop also to store nexthops obtained by recursive resolution, we can get rid of quite a bit of code duplication in the fib management. (rt_netlink, rt_socket, ...) With the new datastructure we can make use of all available paths when recursive routes are resolved with multipath routes. Signed-off-by: Christian Franke <chris@opensourcerouting.org> Signed-off-by: David Lamparter <equinox@opensourcerouting.org> 
Change the datastructure for recursive routes. This brings the following
benefits:

By using struct nexthop also to store nexthops obtained by recursive
resolution, we can get rid of quite a bit of code duplication in the fib
management. (rt_netlink, rt_socket, ...)

With the new datastructure we can make use of all available paths when
recursive routes are resolved with multipath routes.

Signed-off-by: Christian Franke <chris@opensourcerouting.org>
Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
zebra: improve interface shutdown behaviour 2013-09-19T15:51:16+00:00 Christian Franke chris@opensourcerouting.org 2013-01-24T14:04:50+00:00 bfac8dcd2fe7ed099a679b5c8245599c6d0312ed Linux removes IPv6 addresses when the interface is set down. Those addresses need to be readded when the interface is set up again. Also, an interface should not be reactivated from shutdown by configuring an ip address. Finally, remove the three-state logic for the shutdown setting as its sole current use may be mild confusion. Signed-off-by: Christian Franke <chris@opensourcerouting.org> Signed-off-by: David Lamparter <equinox@opensourcerouting.org> 
Linux removes IPv6 addresses when the interface is set down. Those
addresses need to be readded when the interface is set up again.

Also, an interface should not be reactivated from shutdown by configuring
an ip address.

Finally, remove the three-state logic for the shutdown setting as its
sole current use may be mild confusion.

Signed-off-by: Christian Franke <chris@opensourcerouting.org>
Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
zebra: don't change connected state from zebra/interface.c 2013-09-19T15:51:16+00:00 Christian Franke chris@opensourcerouting.org 2013-01-24T14:04:49+00:00 02b4805f3914ef6ba0242c6f4dd1b6759ef97bf2 Try to avoid changing connected state from zebra/interface.c as this means making assumptions about kernel behaviour which may be or may become wrong. This state should rather be updated by events from the kernel. Signed-off-by: Christian Franke <chris@opensourcerouting.org> Signed-off-by: David Lamparter <equinox@opensourcerouting.org> 
Try to avoid changing connected state from zebra/interface.c as this
means making assumptions about kernel behaviour which may be or may
become wrong. This state should rather be updated by events from the
kernel.

Signed-off-by: Christian Franke <chris@opensourcerouting.org>
Signed-off-by: David Lamparter <equinox@opensourcerouting.org>