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.
- when bird runs on a big endian box (e.g. running an arm processor), then the error "MD5 tail signature is not there" occurs as before no matter if the pass is defined in one line or in a passwords block.

Another question. In Quagga you may define a key-chain containing multiple keys to be used for the MD5 authentication. Does it work the same way in bird ? I thought defining a passwords block containing multiple password entries like:

passwords {
  password "secret 1";
  password "secret 2";
};

Best regards,
Alexander Velkov



  protocol rip RIP {
    debug all;
    honor neighbor;
    authentication md5;
     password "secret";
  }

should work.

Best,
Pavel