On Tue, Aug 23, 2005 at 10:45:53PM +0300, Niko Tyni wrote: > On Tue, Aug 23, 2005 at 09:27:01PM +0200, Marc Haber wrote: > > Hm. The actual string doesn't look like base64 here: > > > > host = DYNAMIC/Xxx/x1xxXXXxXXxX1X1XXX > > > > (x is a lower case letter, X is a capital, 1 a digit). Please note the > > second slash which seems out of place here, right? > > No. The base64 alphabet does include '+' and '/', in addition to > letters and digits. The second slash is part of the encoded MD5 hash > of the secret.
If the parser can handle that special case, ok. I generated a new secret, and when the remote client first reported in, the .adr file was created OK. However, smokeping still _occasionally_ logs the "Invalid Target" error, and when the client changed IP addresses this morning, the .adr file was not updated. What can be going wrong here? Can I have a patch which causes the "Invalid Target" error to be logged with a timestamp, source-IP, and a trailing newline? This would greatly ease correlating error.log, access.log and tcpdump. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://lists.ee.ethz.ch/smokeping-users WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
