where do i have defined, can you give me the solution in detailed


On Thursday, October 15, 2015 at 11:59:33 AM UTC+5:30, Eero Volotinen wrote:
>
> Well. then your agent is coming from wrong address due to nat/ipsec. 
>
> You need to use any from agents coming from nat or fix ipsec/nat system.
>
> --
> Eero
>
> 2015-10-15 9:17 GMT+03:00 hari krishna <[email protected] <javascript:>>:
>
>> I have used static ip addresses for all agents, instead of wildcards, as 
>> i described earlier, agent and clients are having communications but behind 
>> the NAT through the Site to Site VPN connections
>>
>>
>>
>> On Thursday, October 15, 2015 at 11:07:51 AM UTC+5:30, Eero Volotinen 
>> wrote:
>>>
>>> to client key ip address field ..
>>>
>>> --
>>> Eero
>>>
>>> 2015-10-15 8:31 GMT+03:00 hari krishna <[email protected]>:
>>>
>>>> Can you explain in detailed about the solution, where do i have to add 
>>>> this ANY ?
>>>>
>>>>
>>>>
>>>> On Wednesday, October 14, 2015 at 6:54:45 PM UTC+5:30, Eero Volotinen 
>>>> wrote:
>>>>>
>>>>> well, you need to use correct ip address while creating client key or 
>>>>> using ip address ANY ..
>>>>>
>>>>> --
>>>>> Eero
>>>>>
>>>>> 2015-10-14 15:49 GMT+03:00 Hari Krishna <[email protected]>:
>>>>>
>>>>>> I have both my clients and servers are behind the nat and connected 
>>>>>> with VPN tunnel, Agents within the servers subnet, able to communicate 
>>>>>> to 
>>>>>> the server, but agents with different network are not able to 
>>>>>> communicate 
>>>>>> to the server, when i troubleshot the issue found following message at 
>>>>>> server.
>>>>>>
>>>>>>  ossec-remoted(1213): WARN: Message from  192.168.5.1 (gateway ip ) 
>>>>>> not allowed.
>>>>>>
>>>>>> *[image: 
>>>>>> http://c29ab44caa2d732d4dd0-b76a82c58b319f049c27bd14d94da9ed.r21.cf2.rackcdn.com/email-signature.png]
>>>>>>  
>>>>>> <http://c29ab44caa2d732d4dd0-b76a82c58b319f049c27bd14d94da9ed.r21.cf2.rackcdn.com/email-signature.png>*
>>>>>>
>>>>>> *Disclaimer: *This message and any attachments are solely intended 
>>>>>> for the addressee(s). It may also be TechAspect confidential, privileged 
>>>>>> and / or subject to copyright. Access to this email by anyone else is 
>>>>>> unauthorized. If you are not the intended recipient, any disclosure, 
>>>>>> copying, distribution or any action taken or omitted to be taken in 
>>>>>> reliance on it, is prohibited and may be unlawful. If you have received 
>>>>>> this in error, please notify the sender immediately by return e-mail and 
>>>>>> delete it from your computer. While all care has been taken, TechAspect 
>>>>>> management disclaims all liabilities for loss or damages to person(s) or 
>>>>>> properties arising from misuse of any information provided or the 
>>>>>> message 
>>>>>> being infected by computer virus or other contamination.
>>>>>>
>>>>>> -- 
>>>>>>
>>>>>> --- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "ossec-list" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to [email protected].
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>> -- 
>>>>
>>>> --- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "ossec-list" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to [email protected].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> -- 
>>
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "ossec-list" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"ossec-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to