>> I don't think anything is encrypted here, this is just peer
authentication
using a shared secret.
correct, my mistake :)
On Tue, Jun 28, 2016 at 5:14 PM, Baptiste Jonglez <
bapti...@bitsofnetworks.org> wrote:
> On Tue, Jun 28, 2016 at 01:59:05PM +0200, Alexander Velkov wrote:
> > Hi Ondrej,
>
On Tue, Jun 28, 2016 at 01:59:05PM +0200, Alexander Velkov wrote:
> Hi Ondrej,
>
> > The first one is RIP request, rest are RIP responses. Quagga apparently do
> > not sign RIP requests. They are optional, so it is not a big problem, but
> > AFAIK they should be signed and verified in the same way
Hi Ondrej,
> The first one is RIP request, rest are RIP responses. Quagga apparently do
> not sign RIP requests. They are optional, so it is not a big problem, but
> AFAIK they should be signed and verified in the same way as RIP requests.
OK. Yes, the whole communication process to be encrypted
On Thu, Jun 23, 2016 at 04:04:48PM +0200, Alexander Velkov wrote:
> Hello again,
>
> Error 1:
>
> You are right, it seems that quagga (ripd) really sends two packets when it
> starts - the first one is unencrypted with metric 16, the others are
> properly encrypted.
The first one is RIP request,
Hello again,
Error 1:
You are right, it seems that quagga (ripd) really sends two packets when it
starts - the first one is unencrypted with metric 16, the others are
properly encrypted.
tcpdump output on the machine running quagga:
# tcpdump -i any port 520 -vvnn
tcpdump: listening on any, lin
On Thu, Jun 23, 2016 at 11:41:18AM +0200, Alexander Velkov wrote:
> Hello,
>
> I have some issues with configuring RIP 'authentication'.
> I connect a bird v1.6.0 running on an ARM machine with a quagga v0.99.23.1
> on a 64bit Ubuntu 14.04 machine.
>
> *Plaintext* (authentication plaintext):
>
>
Hello,
I have some issues with configuring RIP 'authentication'.
I connect a bird v1.6.0 running on an ARM machine with a quagga v0.99.23.1
on a 64bit Ubuntu 14.04 machine.
*Plaintext* (authentication plaintext):
ERROR - bird writes erroneous auth error msg.
the two peers connect successfull
ok great, thank you for your answer!
On Thu, Nov 12, 2015 at 7:01 PM, Ondrej Zajicek
wrote:
> On Thu, Nov 12, 2015 at 05:25:18PM +0100, Alexander Velkov wrote:
> > Hi Ondrej,
> >
> > thank you for your reply!
> >
> > When is this branch planned to be integrated to main?
>
> I guess we will relea
On Thu, Nov 12, 2015 at 06:28:34PM +0100, Alexander Velkov wrote:
> Hi Pavel,
>
> I tried your suggestion and defined the password field as a single line. I
> tried out the behavior on different architectures.
Single line versus one password in passwords block should not make difference.
> - wh
Hi Pavel,
I tried your suggestion and defined the password field as a single line. I
tried out the behavior on different architectures.
- when bird runs on a little endian box, then there is no error and the
boxes can successfully authenticate, even when the pass is specified in a
passwords block
Hi Alex.
On 2015-11-12 16:20, Alex Lalik wrote:
protocol rip RIP {
debug all;
honor neighbor;
authentication md5;
passwords {
password "secret";
};
Configuration of the password like this
protocol rip RIP {
debug all;
honor neighbor;
authentication md5;
password "secre
On Thu, Nov 12, 2015 at 04:20:06PM +0100, Alex Lalik wrote:
> Hello,
>
> I face a problem when configuring RIP with MD5 authentication in bird.
> I find no examples in configuring bird this way, so maybe this could be
> added to the documentation.
> ...
> In case I us
Hello,
I face a problem when configuring RIP with MD5 authentication in bird.
I find no examples in configuring bird this way, so maybe this could be
added to the documentation.
This is the bird configuration I use:
protocol kernel {
scan time 20; # Scan kernel routing table every
13 matches
Mail list logo
