Age | Commit message (Collapse) | Author |
|
prefixes not only the first one.
|
|
of my trees since a few weeks.
|
|
the "detailed" keyword. Currently only works for IP or prefix lookups like
"bgpctl show rib detail 199.185.137.3". Requested by many, looks good henning@
|
|
OK henning@
|
|
for it. OK henning@
|
|
format, intended for monitoring puposes. claudio ok
|
|
claudio ok
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Now bgpctl show rib 129.128.5.191 works again.
|
|
|
|
|
|
|
|
the request, but wait for the new IMSG_CTL_RESULT message, which contains
a status code to indicate wether the request was processed successfully
or wether an error occured and if so what kind of error.
no more "IMSG_CTL_NEIGHBOR_ with unknown neighbor foobaz" in the log
when you mistyped foobar - no bgpctl itself complains
claudio ok
|
|
|
|
|
|
|
|
|
|
|
|
|
|
from tamas tevesz;
|
|
make build will work now.
|
|
zero prefixlen case (32 bit shift on 32 bit val -> undefined result)
spotted by Moritz Grimm and otto
|
|
|
|
show_rib_summary_msg().
|
|
to print prefixes and nexthops and suddenly we can print IPv6 addresses that
are stored in the RIB. Makes the code even simpler. OK henning@
|
|
No need for other strange constructs. OK henning@
|
|
|
|
|
|
|
|
neighbor detail display
|
|
|
|
have no connection in that case
|
|
Needed for upcomming spamd madness. Requested and OK beck@
|
|
or metrics. Requested by beck@ OK henning@
|
|
|
|
|
|
such for those as well, pointed out by claudio
|
|
to see why a nexthop is treated invalid, claudio ok
|
|
Similar to the fix commited by henning@ a few hours ago. OK henning@
|
|
pt out by Alexander v Gernler
|
|
applicable. ok henning, jmc
|
|
too, claudio ok
|
|
and will match almost everything...
|
|
as its address
so "bgpctl neighbor upstream1 clear" now works and you don't have to
remember IPs
claudio ok
|
|
|