Re: sasyncd: no shared key specified

[Stuart Henderson]

On 2007/09/03 23:42, Jacob Yocom-Piatt wrote:
 tried sasyncd out on 4.1-release and noticed that when i uncomment the basic 
 settings in the default /etc/sasyncd.conf file that i see

Just deleting the lines with comments should get it working for
you.

There must be something funny with the parser, it doesn't like
a line with a comment, followed by a newline, between the first
real line of the config and the key.

 # IP addresses or hostnames of sasyncd(8) peers.
 peer 10.0.0.2
 #peer 10.0.0.3
 #peer 10.0.0.4
 # Track master/slave state on this carp(4) interface.
 interface carp1

It's a bit early in the morning for me to see what's wrong with
conf.y but here's a test case:

peer 10.0.0.2
#

interface carp1
sharedkey 0x349fec85c11f6b658d5c457d4668e035f11dfdccb849d5053a8763787b74db70

...alternatively with the #\n\n between interface and sharedkey.

sasyncd: no shared key specified

[Jacob Yocom-Piatt]

tried sasyncd out on 4.1-release and noticed that when i uncomment the 
basic settings in the default /etc/sasyncd.conf file that i see


# sasyncd -d 
config: no shared key specified, cannot continue#
# cat 
/etc/sasyncd.conf   


# $OpenBSD: sasyncd.conf,v 1.1 2007/02/22 16:55:32 henning Exp $
# sample sasyncd configuration file
# see sasyncd.conf(5)

# IP addresses or hostnames of sasyncd(8) peers.
peer 10.0.0.2
#peer 10.0.0.3
#peer 10.0.0.4

# Track master/slave state on this carp(4) interface.
interface carp1

# Shared AES key, 16/24/32 bytes.
sharedkey 0x349fec85c11f6b658d5c457d4668e035f11dfdccb849d5053a8763787b74db70

i've also tried specifying the shared key in a separate file. clues?

cheers,
jake

--