Delete obsolete /* ARGSUSED */ lint comments.

ok miod@ millert@

log the interface along with the neighbour ID in various ospfd/ospf6d
messages. ok remi@ benno@

if a neighbour is reachable over multiple network links, some problems
may be related to the link its

log the interface along with the neighbour ID in various ospfd/ospf6d
messages. ok remi@ benno@

if a neighbour is reachable over multiple network links, some problems
may be related to the link itself rather than the neighbour, so knowing
the interface can be important when trying to locate the source of a
problem.

show more ...

Add point-to-point support for broadcast interfaces.

tested by Kapetanakis Giannis
ok claudio@

Simplify logic a bit by moving a block. nbr_stop_itimer() does not use
the dr or bdr fields so clear them first.

Improve ABR support especially for self-originated stub networks.
This seems to solve the last issues people reported when using ospfd
in multiple areas. OK sthen@ prodding by deraadt@

improve snapshot handling:
- don't start a new snapshot if we are already in NBR_STA_SNAP
- ignore IMSG_DB_SNAPSHOT and IMSG_DB_END unless we are in NBR_STA_SNAP
- add new IMSG_LS_SNAP message so we

improve snapshot handling:
- don't start a new snapshot if we are already in NBR_STA_SNAP
- ignore IMSG_DB_SNAPSHOT and IMSG_DB_END unless we are in NBR_STA_SNAP
- add new IMSG_LS_SNAP message so we can distinguish it from
IMSG_LS_UPD. this way we can ignore them if we are not in NBR_STA_SNAP
ok claudio@

show more ...

ignore the nbr_adj_timer if we are not forming adjacencies; ok claudio

transmit correct state to RDE; ok claudio

First bits to support opaque LSA. Type-9, 10 and 11 are LSA that can
hold about any data you like and is used for things like greaceful
reload. Implement the basic redistribute logic and LSDB handlin

First bits to support opaque LSA. Type-9, 10 and 11 are LSA that can
hold about any data you like and is used for things like greaceful
reload. Implement the basic redistribute logic and LSDB handling but
the data sent is currently not looked at.
Tested and OK sthen@

show more ...

Fix some memory leaks. Mainly better cleanup on shutdown but the v_nexthop
leak is a runtime one.
OK bluhm@

When failing to form an adjacency, log the interface name as well
as the neighbour. ok claudio@

Clear the DR and BDR addresses in nbr_act_delete(), makes the election
process more reliable after interface flaps. Especially when the router-id
changed at the same time.
OK dlg@, sthen@

Oups, these changes should not have been commited. Revert.

Announce a stub network LSA for backup carp interfaces. This should help
when fail-over happens, since removing the better route will not result
in a blackhole until the update from the new master is

Announce a stub network LSA for backup carp interfaces. This should help
when fail-over happens, since removing the better route will not result
in a blackhole until the update from the new master is processed.
Tested, OK and input sthen@, phessler@

show more ...

Correct the output of several error and debug messages.

Do not overload nbr->options with the dd exchange bits. nbr->options is used
by the hello protocol. Instead add a dd_more flag that is used together with
(the renamed) dd_master flag.
Tested and OK n

Do not overload nbr->options with the dd exchange bits. nbr->options is used
by the hello protocol. Instead add a dd_more flag that is used together with
(the renamed) dd_master flag.
Tested and OK norby@

show more ...

NBR_ACT_HELLO_CHK was missing in the nbr_action_names list.

When deleting a neighbor or a interface make sure that no events are pending.
Needed for reload support. OK norby@

Remove a XXX in a comment.

The return value of the start/stop timer functions is almost never checked.
Switch them to void functions and check if evtimer_add/del fails -- in which
case we fatal() as there is no useful way to r

The return value of the start/stop timer functions is almost never checked.
Switch them to void functions and check if evtimer_add/del fails -- in which
case we fatal() as there is no useful way to recover in such an event.
OK norby@

show more ...

Move *_name functions to log.c and use these for both ospfd and ospfctl.
Stuff that is only used in ospfd debug messages is simplified.
OK norby@

Keep track of the duration of our relationships with neighbors.
Displayed in "ospfctl show neighbor".

ok claudio@

Do not kick the adj_timer for neighbors that are in state 2-Way.

ok claudio@

Do not traverse the entire LS retransmission list to figure out how many
are present on it.

ok claudio@

Prevent the neighbor FSM from getting stuck forever in state EXSTART.

ok claudio@