This oddly didn't help, as soon as I changed it to be the internal IP, it complained the external IP wasn't allowed to connect.
I did manage to get it working by using the instructions here: http://dcid.me/2011/01/automatically-creating-and-setting-up-the-agent-keys/ Apparently using the remote agent doesn't lock it down to a specific IP. Thanks for the help, Ben On Wednesday, March 7, 2012 4:35:42 PM UTC-5, woodspeed wrote: > > Hi! > > Maybe this helps you: > http://www.ossec.net/doc/manual/agent/agent-dhcp-nat.html > > Best regards > woodspeed > > 2012. március 7. 16:46 Ben írta, <bhw2249>: > >> Hi all, >> >> Trying to troubleshoot connectivity between an ec2 ossec-agentd and a >> non-ec2 ossec-remoted. >> >> My question is the following: >> >> - does the NAT that an elastic IP provide cause issues? >> >> 1) I can't seem to get it to connect and my server shows no signs of it >> trying to connect. >> 2) No other agents have issues, and no firewall rules are in the way. >> >> Any suggestions? >> >> OSSEC HIDS v2.6 on both systems. >> agent: Linux west.hub 3.0.0-13-virtual #22-Ubuntu SMP Wed Nov 2 17:10:19 >> UTC 2011 i686 i686 i386 GNU/Linux >> server: Linux rackm3.ben 2.6.32-39-generic #86-Ubuntu SMP Mon Feb 13 >> 21:47:32 UTC 2012 i686 GNU/Linux >> >> >> Thanks, >> Ben >> > >
