summaryrefslogtreecommitdiff
path: root/vtysh/vtysh_config.c
diff options
context:
space:
mode:
authorpaul <paul>2005-09-12 16:58:52 +0000
committerpaul <paul>2005-09-12 16:58:52 +0000
commitca16218df74a43491e34a577db5023c89a7e79c8 (patch)
tree5aaee14da68863f7d7eb80fad46c83bebfc4fb8c /vtysh/vtysh_config.c
parent1f377b0202dfc4653f7717de964b628a369a9526 (diff)
2005-09-12 Paul Jakma <paul.jakma@sun.com>
* (general) RTM_CHANGE and implicit withdraw on RTM_NEWADDR support. * connected.c: (connected_withdraw) new function. withdraw a connected subnet address set from zebra, and pass information along to clients. (connected_announce) similar, but to announce a new connected subnet address set. (connected_check_ipv4) renamed to connected_check, as its AFI independent. (connected_add_ipv{4,6}) Remove the connected address announce stuff, use connected_announce instead. If connected_check indicates address is already present, treat it as an implicit withdraw of the existing address, ie remove the old address details and replace with the new details. (connected_delete_ipv{4,6}) Use connected_withdraw. (connected_check_ipv6) deleted in favour of connected_check. * connected.h: Rename connected_check_ipv4 to connected_check. delete connected_check_ipv6. * interface.c: Use connected_check rather than the AFI specific symbols. * kernel_socket.c: (rtm_read) RTM_CHANGE support. Create a rib delete event for the existing route, before adding route again. (kernel_read) we can handle RTM_CHANGE now.
Diffstat (limited to 'vtysh/vtysh_config.c')
0 files changed, 0 insertions, 0 deletions