Age | Commit message (Collapse) | Author |
|
found by millert@, ok deraadt@
|
|
"Let msgbuf_write return -1 with errno EAGAIN. The users then must
check if this was the case and readd the event or poll again. The
current handling in the imsg code is wrong for sure."
ok gilles, benno
|
|
routing table. Need for it in "special" setups pointed out by
Loic Blot (loic.blot _AT_ unix-experience _DOT_ fr) on tech.
OK benno, henning
|
|
ok claudio benno
|
|
filter expansion so that rules are grouped by prefixes last. The RDE will
then be able to optimize the rules into table lookups but that is a later
step. As additional goodies it is now possible to use inet and inet6
on their own and or-longer can be used as a shorthand for prefixlen >= len.
OK henning@ sthen@ florian@
|
|
requested by and ok deraadt@
|
|
|
|
|
|
After a discussion with sthen@ and claudio@; wording help from sthen@.
OK claudio@, sthen@, jmc@
|
|
This is the first step to make bgpd reload non blocking in the RDE.
It also speeds up the reload time a fair bit in some cases (mainly if
you run with multiple RIBs and have larger filtersets) and it should also
fix a few edge cases on reloads.
Testing done by benno@, florian@ and sthen@ OK henning@ and benno@
|
|
From: Jan Stary
|
|
triping max-prefix. fix it this way, at least until prefix accounting
is done better.
diff from florian@
ok claudio@
|
|
a IMSG_SESSION_ADD message to the RDE when a peer comes up or when a reload
happens. The IMSG_SESSION_ADD has the full current config of the peer and
so the RDE should end up with correct values. This affects mostly maxprefix
and the RIB settings. OK henning@
|
|
|
|
OK henning@
|
|
the session engine to actually stop logging.
Found the hard way by benno@.
with & ok benno@
input & ok claudio@
|
|
ttl on outgoing packets so peer sessions can come up correctly if both sides
use ttl-security, but the kernel side is not yet implemented so incoming
packets aren't verified (note added to manual for this). ok henning@
|
|
Fixes v6 routes being added to the kernel as RTP_DEFAULT. ok florian@ benno@
|
|
|
|
who is to shy to commit these by himself.
|
|
accessed. Found by magic clang skill of blambert@
|
|
don't need to scale to 64 bits in this universe.
ok claudio@ & florian@
|
|
|
|
OK sthen@
|
|
OK sthen@
|
|
ignored silently and without aborting, much like EINTR and EWOULDBLOCK are.
ok's from various maintainers of these directories...
|
|
- on config reload also adjust the cloned neighbors so that they get the
config changes as well.
- clean up sessions that are 1h idle but in state active (instead of down)
- add bits to allow bgpctl to destroy cloned neighbors
Tested by sthen@ some time ago, OK phessler@
|
|
the description if it is set.
|
|
this is a normal condition. ok phessler@ florian@
|
|
32 chars. Allow bgpd to use these newfangled longer names.
OK sthen@
|
|
ok sthen@
|
|
particular capability is bad, log the fact and ignore it. This may give us
a chance to bring up session that have e.g. unexpected AFI,SAFI pairs in them.
Also make the error messages more user friendly.
OK henning@, sthen@
|
|
ok claudio@
|
|
ok henning
|
|
|
|
like: allow from any nexthop neighbor (to allow only prefixes that use the
routers IP address as nexthop). Lots of testing, input and OK florian@
|
|
ok claudio, benno
|
|
|
|
references into a STANDARDS section;
|
|
real. After discussion with sthen@, henning@ and deraadt@.
It can be disabled per neighbor with "announce restart no".
|
|
OK sthen@ henning@
|
|
OK sthen@, benno@, henning@
|
|
|
|
This implements only the "Restarting Client" bits of the RFC -- in other
words bgpd will keep the FIB when the client restarts but it will not do GR
when restarting itself. The capability is still off by default (you need
"announce restart yes" to enable it).
Tested by Anders Berggren. OK sthen@
|
|
- flesh out SEE ALSO in bgpd.8
- fix a formatting warning in relayd.conf.5
|
|
|
|
flags field. Some systems seem to start sending bad flags around which
cause session failures in bgpd. Make sure that bgpd ignores the must be
zero flags correctly and ensure that they are always reset to zero when
sending updates out.
Reported and patch tested by Laurent CARON, OK henning@
|
|
when there was a change in the nexthop info. Fixes massive memory consumption
crashes when used with ospfd (which sometimes updates route that have not
changed). Tested together with benno@ and a lot of input from Florian Obser.
OK henning@
|
|
set med 0 and Hennings iBGP sessions. OK henning@
|
|
running away if the setsockopt call fails, as may happen if a peer bounces
at the wrong time.
OK claudio@ after tweaks to an earlier version which was OK phessler@.
|