Age | Commit message (Collapse) | Author |
|
chain. Fix kroute_insert() and rtmsg_process() to correctly do this.
OK bluhm@
|
|
|
|
used to quickly verify if two LSDBs are in sync. Other systems do the same.
OK dlg@
|
|
(verified by both sthen@ and me).
ok sthen@; "just commit it" claudio@
|
|
problem reported with the obvious fix for bgpd by Sebastian Benoit
<benoit-lists at fb12.de>, also PR 6432
applied to all the others by yours truly. ok theo
isn't it amazing how far this parser (and more) spread?
|
|
LSA that is currently in the tree. Pruning with default metrics is bad
since the checksum of the LSA is different and therefor an additional
update cycle is needed to convince the other systems.
OK bluhm@, sthen@
|
|
Make sure that if the LSA is managed by this router that we force timed-out
LSA to stay timed out which causes them to be pruned in the secound round.
This problem can show up when not exactly the same LSA is pruned because
the checksum is used as tiebreaker resulting in indeterministic selection
of which LSA is considered newer.
OK bluhm@, sthen@
|
|
routing table and interface list, do a reload of the kernel state.
ive been running this in production for 2 or 3 weeks.
tested by sthen@
ok sthen@ claudio@ deraadt@
code written by andrew sallaway at the univeristy of queensland.
|
|
ok claudio@
|
|
af. This is possible since this filtering no longer blocks RTM_IFINFO.
OK henning@
|
|
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
|
|
ok claudio@
|
|
ok claudio@
|
|
continue. fix kr_dispatch_msg so it acts when rtmsg_process fails.
from andrew sallaway based on discussion with claudio@
ok claudio@
|
|
warnings from gcc4)
os claudio@
|
|
automagicaly mask the addresses. While there kill a #ifdef that no
longer makes sense since it is the least problem for portable versions.
|
|
the number of bytes they processed from the kernel on success, so testing
against 0 meant that the fib reload code always dropped out early.
found by andrew sallaway
ok claudio@
|
|
Minor bump for libutil.
Previous versions of this diff and man page looked at by various people.
"you should just commit" deraadt
|
|
ibuf, buf_read to ibuf_read, READ_BUF_SIZE to IBUF_READ_SIZE.
ok henning gilles claudio jacekm deraadt
|
|
more readable, and fixes a spacing bug we had in smtpd.8;
|
|
|
|
|
|
way the memory is zeroed. This is equivalent to the relayd commit by reyk.
OK reyk, jsg
|
|
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@
|
|
|
|
as the neighbour. ok claudio@
|
|
ok eric
|
|
If this happens the imsg may no longer be usable as there may be queued
messages, but this is a) already the case with the code now, and b)
would be the case if recvmsg() fails anyway, so we can document that -1
from imsg_read() invalidates the struct imsgbuf.
discussed with and ok eric
|
|
be done for rtmsgs (which have an rtm_errno) and not ifmsgs (which have
part of an if_data struct in that location). Fixes problems finding
interface addresses at startup. ok claudio@
|
|
OK dlg@
|
|
OK: henning@, claudio@
|
|
Sync description of the OSPF protocol between ospfd(8) and ospf6d(8).
Document current shortcomings -- in particular, document that ospf6d(8)
needs manual IPsec setup for security. Clean up various grammatical errors,
re-order and re-phrase things a bit to improve readability.
Update RFC references. Remove IPv4-specific stuff from ospf6d.conf(5).
OK jmc@ claudio@
|
|
in these cases, is useless anyway.
Found by and fixing the build with mandoc;
still fine with both old and new groff.
ok jmc@
|
|
in slightly different ways. this unifies these handlers and cuts
fetchtable over to using the generic handler.
help from claudio@ and sthen@
ok claudio@
|
|
dispatch_rtmsg, factor the message handling out. both fetchifs and
dispatch_rtmsg get a buffer full of messages and then run it through a
parser. now they get their buffers and pass it to rtmsg_process.
ok claudio@
|
|
refetchtable.
tested by me and sthen@
ok claudio@
|
|
From Christiano F. Haesbaert.
ok claudio@
|
|
|
|
this tells the daemon to resync the kernels list of interfaces and routes
with the daemons list. this is very useful if the routing socket overflows
and you want to sync things up again.
lots and lots of help from claudio@
ok claudio@
|
|
inform about the interface address change. If this is an active interface
it will be downed. A ospfctl reload is needed to fetch the new/changed IP
if one got set. OK dlg@, sthen@
|
|
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@
|
|
with reloads when running ospfd on multiple aliases on the same interface.
Is also needed to handle interface address changes in a much better way.
OK dlg@, sthen@
|
|
process more reliable after interface flaps. Especially when the router-id
changed at the same time.
OK dlg@, sthen@
|
|
neighbors from using the source IP on broadcast interfaces to using the
router-id all the time. The interface lookup will already check for
matching subnets so there is no conflict possible. This makes ospfd finally
grok router-id changes without freaking out. Additionally whinge when an
other router is using the same router-id instead of failing in a very
horrible way.
OK sthen@, dlg@
|
|
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.
|
|
pointed out by claudio@ before, somehow it snuck back in.
|
|
better respond to rapid topology changes.
developed while working with joshua atterbury
ok claudio@ as part of a larger diff.
|
|
state machine needed by the features that are coming along.
ok claudio@
|
|
|