Age | Commit message (Collapse) | Author |
|
case carp(4) interfaces anymore. LINK_STATE_IS_UP() almost always does
the right job.
OK deraadt@ henning@
This needs a -current kernel or link state may be not reported correctly.
|
|
|
|
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@
|
|
to IF_STA_LOOPBACK in if_act_start() this way they will repsect
IFF_UP on startup. Also remove a now no longer needed workaround
when reloading interfaces.
Initial diff provided by Patrick Coleman. OK dlg@
|
|
and make it possible to bind sockets (including listening sockets!)
to rtables and not just rdomains. This changes the name of the
system calls, socket option, and ioctl. After building with this
you should remove the files /usr/share/man/cat2/[gs]etrdomain.0.
Since this removes the existing [gs]etrdomain() system calls, the
libc major is bumped.
Written by claudio@, criticized^Wcritiqued by me
|
|
is forced into IF_STA_NEW so that if_init() can be called to setup timers etc.
When a loopback interface is added to the config, this means there's no way
to get to the correct state.
Fix by avoiding changing an existing IF_STA_LOOPBACK and forcing loopback
interfaces to be passive (otherwise skipping the if_init on an active
interface causes problems).
ok claudio@
|
|
the interface was removed or when the address changed leaving the multicast
groups will fail because that already happend. Fix if_leave_group() to
remove the refcount before doing the ioctl() so that the reference is
correctly removed. OK dlg@, sthen@
|
|
if route-dead-time is set to "minimal" (rather than a number of
seconds), the dead time is set to 1 second and hellos are sent at
the interval specified by fast-hello-interval in msecs. this is non
standard wrt to the ospf rfc, but it does interoperate with at least
one other router vendor.
this allows much better responsiveness to l3 topology changes than
the standard intervals allow. if i yank a cable to one of my
upstreams, the routes adjust in a second rather than the default
of 40 i was running with before. the users dont even notice something
changed.
developed while working with joshua atterbury.
ok claudio@ as part of a larger diff.
dedicated to zan rowe who thinks she is a bigger nerd than me.
|
|
|
|
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@
|
|
bytes is not enough for larger networks causing send errors because of
too big packets. OK henning
|
|
|
|
|
|
|
|
|
|
interfaces and areas. With this carp setups using ospfd are more reliable
because we can fail over if the OSPF connectivity is (partially) lost.
OK norby@
|
|
|
|
all other routers will drop the session immediatly instead of waiting for
the timeout that is normaly 40 sec. This reduces fail-over time massivly
and does not hurt anymore since we are now able to reload the configuration
on the fly. OK norby@ pyr@
|
|
Needed for reload support. OK norby@
|
|
state, if known by the driver. this is required to check the full
duplex state without depending on the ifmedia ioctl which can't be
called in the kernel without process context.
ok henning@, brad@
|
|
address of a interface could be used. Now it is possible to specify a
interface more than once if multiple networks are configured. An alternative
network can be specified via e.g. interface em0:10.0.5.1. The old interface
syntax without the IP still works and uses the main/first configured IP
address.
ospfd now needs to include the IP header on outgoing messages as it is not
possible to specifiy the source address in sendto(2). Additionally all
multicast joins and leaves have to be tracked.
OK norby@
|
|
the source address and the interface index to find the corresponding
struct interface which is less error prone. OK norby@
|
|
in state DR or BACKUP. Found while analizing PR5192 with norby@ -- seems to
help but there is still a issue left. OK norby@
|
|
global and per area defaults. With this it is now possible to define one
set of auth-md keys and use them in every defined interface. OK norby@
|
|
|
|
This makes it much easier to grep in the output.
The original format of "show interface" can be seen with
"show interface detail".
help and ok claudio@
|
|
c string with a lenght <= 8 with a buffer of size 8. Now in some cases
there can be trailing garbage after the c-string and so the bcmp() fails.
Found by Sergey Matveychuk who provided a similar patch.
OK norby@
|
|
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@
|
|
ok claudio@
|
|
Stuff that is only used in ospfd debug messages is simplified.
OK norby@
|
|
almost happy.
|
|
|
|
|
|
not be used to connect to a OSPF cloud and forced to be passive. With this
ospfd will only announce the carp interface route if the interface is master.
So you can connect a LAN in a redundant way to your ospf backbone. OK norby@
|
|
and do not remove a element twice in iface_del(). OK norby@
|
|
Prevents some of the retransmitting during bulk ls update transfers.
ok claudio@
|
|
|
|
especially it got called in the wrong place. OK norby@
|
|
OK norby@
|
|
ok norby@
|
|
- have ospfctl tell us when we are using authentication with 'show interface'
ok claudio@ norby@
|
|
- remove rtr_id from struct iface we don't need to keep a copy of this value
per interface
- replace all references to iface->rtr_id.s_addr with calls to ospfe_rtr_id()
ok claudio@ norby@
|
|
that are in loopback mode. With this it is possible to use lo1 to hold the
loopback address of the router as done often on ciscos etc.
Problem found and fix tested by jakob@ OK norby@
|
|
One of the main problems is that the RFC is very unprecise about the process
and so a bit of guessing and "violating" the RFC is needed.
The problem was that on fast restarts ospfd computed wrong DR and BDR
routers. OK norby@ deraadt@
|
|
timer in IF_STA_WAITING. We are not ready for this because the RFC is totaly
fucked up in that specific area causing many issues on fast reloads.
OK norby@
|
|
and init) are not electable not only neighbors that are in state down.
OK norby@
|
|
OK norby@
|
|
ignores the event. This removes the warning "fsm_if: interface em0, event
WAITTIMER not expected in state DROTHER" in case of a quick startup.
OK norby@
|
|
faster and follows the RFC more closely).
OK norby@
|
|
ok claudio@
|