On May 25, 9:24 am, hojo <[email protected]> wrote: > On May 25, 6:42 am, "dan (ddp)" <[email protected]> wrote: > > > Have you tried with anything more recent than 2.6? > > I thought 2.6 was the most recent. This is very confusing. > > > Try putting an ipv4 address in there and fixing it post install. It's > > hackish, but we'll look into the install scripts (if they haven't been > > fixed already).
I installed the client, configured an ipv4 address for the server then changed it to an ipv6 address. I tried both with and without brackets and both results are the same: [root@localhost bin]# ./ossec-control start Starting OSSEC HIDS v2.6 (by Trend Micro Inc.)... Started ossec-execd... 2012/05/29 11:45:12 ossec-config(1237): ERROR: Invalid ip address: '[fda1::1]'. 2012/05/29 11:45:12 ossec-config(1202): ERROR: Configuration error at '/var/ossec/etc/ossec.conf'. Exiting. 2012/05/29 11:45:12 ossec-agentd(1215): ERROR: No client configured. Exiting. Can you suggest a relatively stable revision from bitbucket that I can try rather than starting at the top and working down until I find the least changed v6 version? Thanks, -dave > > I'll give the post install fix a shot.
