On Mon, Nov 13, 2017 at 07:56:47AM +0300, Dmitry S. Nikolaev wrote:
> Hi.
>
> So, can we expect an answer ?
Hi
I hope that i answered:
http://trubka.network.cz/pipermail/bird-users/2017-October/011623.html
--
Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.o
Hi.
So, can we expect an answer ?
Thanks.
With best regards, Dmitry S. Nikolaev
Moscow, Russia
phone: +7 (499) 678 8007 [ext. 6003]
fax: +7 (499) 678 8007 [ext. ]
www: http://www.mega-net.ru
mail: dnikol...@mega-net.ru
SIP URI: dnikol...@sip.mega-net.ru || d...@sip.mega-net.ru
On 31.10.201
On Thu, Oct 26, 2017 at 04:40:45PM +0300, Mikhail Grishin wrote:
>
> Hi,
>
> 1) You also implemented
> enable bgp2 "enable message"
> This message currently seen only at local side and doesn't seen at
> remote peer.
>
> Scenario: You made maintenance work with the shutdown message "Session
> wil
Hi, hope you well.
I also interested in this question.
Can someone from the developers say something about it ?
Thanks.
With best regards, Dmitry S. Nikolaev
Moscow, Russia
SIP URI: d...@sip.mega-net.ru
On 26.10.2017 16:40, Mikhail Grishin wrote:
>
> Hi,
>
> 1) You also implemented
> enable bgp
Hi,
1) You also implemented
enable bgp2 "enable message"
This message currently seen only at local side and doesn't seen at
remote peer.
Scenario: You made maintenance work with the shutdown message "Session
will be down from 13:00 till 14:00".
Later session was established again. Days after at
Hi Ondrej,
Thank you for your work on this patch. When sending in my code i
realised it was a bit rough on the edges, and secretly hoped that a more
experienced BIRD developer would take pity and polish it up.
Appreciated!
On Tue, Sep 26, 2017 at 02:22:20PM +0200, Ondrej Zajicek wrote:
> On Tue,
On Tue, Sep 26, 2017 at 10:14:11AM +0200, Peter Hessler wrote:
> On 2017 Sep 19 (Tue) at 20:53:47 +0200 (+0200), Ondrej Zajicek wrote:
> :Merged with some significant changes, with support for both RX and TX of
> :shutdown communication:
> ...
> :
> :Unfortunately, that means that from Unix shell y
On 2017 Sep 19 (Tue) at 20:53:47 +0200 (+0200), Ondrej Zajicek wrote:
:Merged with some significant changes, with support for both RX and TX of
:shutdown communication:
...
:
:Unfortunately, that means that from Unix shell you have to do double qouting:
:
:birdc disable bgp1 '"hi, we will upgrade t
On Thu, Jul 27, 2017 at 05:55:40PM +0200, Job Snijders wrote:
> Hi all,
>
> Here is a patch to decode received BGP shutdown communication messages
> as specified in RFC 8203. In the following example scenario I'm sending
> a shutdown communication with openbgpd:
>
> $ bgpctl neighbor 94.142
bump? :-)
On Fri, Jul 28, 2017 at 12:26:59PM +0200, Job Snijders wrote:
> Spin #2
>
> ---
> proto/bgp/bgp.c | 12 +
> proto/bgp/bgp.h | 2 ++
> proto/bgp/packets.c | 73
> ++---
> 3 files changed, 61 insertions(+), 26 deletions(-)
Spin #2
---
proto/bgp/bgp.c | 12 +
proto/bgp/bgp.h | 2 ++
proto/bgp/packets.c | 73 ++---
3 files changed, 61 insertions(+), 26 deletions(-)
diff --git a/proto/bgp/bgp.c b/proto/bgp/bgp.c
index f706e76..2a89c00 100644
--- a/proto
Hi,
Peter van Dijk pointed me at valgrind. It appears I can improve this
patch a bit more, stay tuned.
Kind regards,
Job
On Thu, Jul 27, 2017 at 05:55:40PM +0200, Job Snijders wrote:
> Hi all,
>
> Here is a patch to decode received BGP shutdown communication messages
> as specified in RFC 8203
Hi all,
Here is a patch to decode received BGP shutdown communication messages
as specified in RFC 8203. In the following example scenario I'm sending
a shutdown communication with openbgpd:
$ bgpctl neighbor 94.142.241.204 down "TICKET-2331 we are upgrading,
back in 30 min"
requ
13 matches
Mail list logo
