Age | Commit message (Collapse) | Author |
|
dropped when parsed but instead be added to the RIB marked as not eligible.
So the decision process does not pick them up as a valid route.
Tested and some ideas by Tony Sarendal (tony (at) polarcap (dot) org)
|
|
seen on startup.
|
|
|
|
|
|
it with a simple filter in the yylex() loop.
The compression in lgetc() didn't happen for quoted strings,
thus creating a regression when tabs were used in variables.
Some testing by todd@ and pyr@
OK deraadt@
|
|
when it's not really documented in what way it influences the decision
process, people like myself will screw it up and assume that it gets
added to the prefix path lenth, and thus that smaller weight wins.
.. which is not the case. Document the actual behaviour.
ok claudio, the general change agreed by henning.
proofraed by jmc.
|
|
ok henning@
|
|
Requested and OK deraadt@
|
|
expand to space or tab, and a \ followed by newline should be ignored
(as a line continuation). compatible with the needs of hoststated
(which has the most strict quoted string requirements), and ifstated
(where one commonly does line continuations in strings).
pointed out by mpf, discussed with pyr
|
|
yylex implementation and the code which interacts with yylex. this also
brings the future potential for include support to all of the parsers.
in the future please do not silly modifications to one of these files
without checking if you are de-unifying the code.
checked by developers in all these areas.
|
|
as found in hoststated, and make all the code diff as clean as possible. a
few issues remain mostly surrounding include support, which will likely be
added to more of the grammers soon.
ok norby pyr, others
|
|
127.0.0.1 / ::1 unconditioally, since RTF_BLACKHOLE/REJECT are not
actually checked in the forwarding path and the gw doesn't matter otherwise.
makes them work.. found teh hard way by me. claudio ok
|
|
string that it returned later. rde_update_log() did not do that.
Memory leak found and diff provided by Mike Belopuhov.
|
|
all the relative metrics need some special handling. OK henning@ deraadt@
|
|
|
|
reloading.
``yeah that is good'' henning@
|
|
function with the same arguments.
|
|
|
|
set is used inside neighbor or group statements and the result was that
these rules no longer machted everything. Problem found by Jon Morby.
Please commit henning@
|
|
bgpd uses internaly so we can just dump that one out.
Found by Stuart Henderson, OK henning@
|
|
not allow anybody to use 65535. That one is reserved for well known
communities. Add in that check again.
|
|
ok claudio@
|
|
short updateds included a dummy ::/0 route and the withdraws were totaly
wrong because the AFI/SAFI header was missing.
put it in henning@
|
|
4. OK henning@
|
|
that unfortunately means we cannot use 0 for "unset".
ok claudio
|
|
AS path and the 2-byte version. If both pathes have the same length don't
try to merge them instead use the new path.
Issue reported by Jon Morby and further analysed by Stuart Henderson.
Tested by Stuart Henderson.
|
|
version 13.
|
|
Additionally our as4byte support is based on draft-ietf-idr-as4bytes-13.
|
|
From: Stuart Henderson <stu@spacehopper.org>
|
|
|
|
|
|
|
|
|
|
|
|
"people will complain if it's unclear" jmc@
|
|
|
|
|
|
are now 4-byte instead of the old 2-byte numbers. The only exception are
communities because they can not be switched. The RDE will inflate and deflate
the ASPATH and AGGREGATOR attributes on demand and create the NEW_ASPATH and
NEW_AGGREGATOR field whenever needed. Both old and new stile sessions are
supported and can be mixed. Currently new stile sessions with the 4-byte AS
number capability turned on are only enabled if one of the AS numbers involved
is a 4-byte one.
This is based on an initial diff by Geoff Huston gih (at) apnic (dot) net
Cleanup, testing and bug-fixes by myself (via AS 3.10).
Currently mrt table dumps are producing incompatible output this will be fixed
afterwards -- this diff is already big enough.
"get it in if you think it is ready" henning@
|
|
using a static message structure. This is more flexible and needed if
multipath comes into play. looks good henning@
|
|
some time ago. OK henning@
|
|
Discussed with henning@
|
|
|
|
|
|
This makes prefixlen filtering for AF_INET6 unnecessary complex. From now
on if prefixlen is used alone the address family needs to be specified
beforehands via the new inet or inet6 keywords.
Remove an old check so that it is finally possible to filter IPv6 prefixes.
OK henning@
|
|
mostly from rivo nurges <rix@estpak.ee>, ok claudio
|
|
IPV6_UNICAST_HOPS which does the same thing and does not fail.
OK henning@ found by Jon Morby
|
|
signal "connection closed" upstream.
spotted by Valentin Kozamernik <tin@komna.com>
|
|
|
|
|
|
a few things we actually never realy cared about.
OK henning@
|