search for: repropagated

...no idea why it complains about the route and fib 0 as I use the same up script as on my two x86 FreeBSD boxes and they do not complain. Before someone says "replace your keys" I went down that road already. I verified I had the right keys on all systems. In addition I have replaced and repropagated the beaglebone keys 3 times. I want to stress that all the x86 boxes can speak with each other. The x86 boxes are FreeBSD 10.1, FreeBSD 8.1 and Mac OS X 10.6.8. The beaglebone keys were generated on the beaglebone. Ideas or clues appreciated. - -Brett - -- wynkoop at wynn.com...

...te that already exists. Maybe that is indeed the case? > Bogus data received from net01e (199.89.147.1 port 655) > > Before someone says "replace your keys" I went down that road already. > I verified I had the right keys on all systems. In addition I have > replaced and repropagated the beaglebone keys 3 times. Some problem with the keys is the most likely explaination for "bogus message", however if that is ruled out the next likely problem is the use of "PrivateKey" or "PublicKey" statements in config files, when you actually meant "Privat...