Re: [PacketFence-users] Error communicatin with Nessus

Hallo James, Thanks for your reply. Juan Valencia and I have troubleshooted this last week and below is the current status: - Can now connect. Had to had to instruct the LWG agent not to verify hostname via ssl. -> resolved - Violation id 120005 and custom violation id got triggered

Re: [PacketFence-users] Error communicatin with Nessus

Kehinde, I am looking into this. By next tuesday I should have a good solution. Thanks James On 2017-07-17 8:58 AM, Akala Kehinde via PacketFence-users wrote: Hallo Guys, Quick one.. I get this error when PF tries triggering a violation: Checked line 96 and seems it's an error with the

Re: [PacketFence-users] Error communicatin with Nessus

I expect id 100024 to be triggered when in Production vlan but it doesn't. On 11 Aug 2017 2:25 PM, "Akala Kehinde" wrote: > Ok. But in my case, I see no violation 100024 triggered even when there is > a violation. Only 100025 tiggers. > And also what ID is triggered on

Re: [PacketFence-users] Error communicatin with Nessus

100024 self closes when there is no wmi violation. When there is a violation triggered by the scan engine with action_param = mac = $mac, tid = 12, type = INTERNAL then it does not close itself. I configured the violation to allow the user to self remediate (e.g. uninstall an unwanted

Re: [PacketFence-users] Error communicatin with Nessus

Hi Cristian, The 100024 id doesn't trigger. No logs, nothin. Only the 100025 does. Just to be sure of the Reg. and Post Reg scan operations, the Reg.scan works just when authenticating and the Post Reg. after authentication. And does the violation (the wmi violation itself) self close when you

Re: [PacketFence-users] Error communicatin with Nessus

Hi Christian, Is the ssl config change you made in the nessus6.pm file necessary, because I only made the change in the REST.pm file, and I could connect. But the issue I am having is with the "scanner name doesn't exist" even after settign as "Local Scanner". Can you send me your nessu6.pm file.

Re: [PacketFence-users] Error communicatin with Nessus

Hi Cristian, Took me some time too to have the WMI scan running, but even only works for pre-reg. Failed for Reg and Post-reg scans.Had any success with that? Regards, Kehinde On Thu, Aug 10, 2017 at 2:31 PM, Cristian Mammoli via PacketFence-users < packetfence-users@lists.sourceforge.net>

Re: [PacketFence-users] Error communicatin with Nessus

WMI works for me on production network, what issues are you having? Il 10/08/2017 14:37, Akala Kehinde ha scritto: Hi Cristian, Took me some time too to have the WMI scan running, but even only works for pre-reg. Failed for Reg and Post-reg scans.Had any success with that?

Re: [PacketFence-users] Error communicatin with Nessus

Hi Akala, the result is the same for the ssl_options. It only tells LWP UserAgent to not verify the hostname. I just wanted to avoid editing something external to packetfence. I attached my nessus6.pm, but try to update /usr/share/perl5/vendor_perl/Net/Nessus/REST.pm with the latest upstream

Re: [PacketFence-users] Error communicatin with Nessus

I'm getting the same error. Nessus is running and I can connect with wget https://127.0.0.1:8834 --no-check-certificate Even a simple test program such as this fails with the same error even if the data is correct: use Net::Nessus::REST; my $nessus = Net::Nessus::REST->new(

Re: [PacketFence-users] Error communicatin with Nessus

Hi Akala, Nessus has a log that you can verify from the server perspective to try figure it out what is going on, if I'm not wrong is in /opt/nessus/var/nessus/log/ and is something realted with server in its name, try to tail that log while you try to do the connection from packetfence and you

Re: [PacketFence-users] Error communicatin with Nessus

Hello Fabrice, Still can"t get my head around this.. Seems to me like an API communication problem or any more ideas to what the problem might be. Regards, Kehinde On Sat, Jul 29, 2017 at 8:53 AM, Akala Kehinde wrote: > Hello Fabrice, > > I still get the same error,

Re: [PacketFence-users] Error communicatin with Nessus

Hello Fabrice, I still get the same error, kindly see logs below: [root@pfence logs]# netstat -nlp | grep 8834 tcp0 0 0.0.0.0:88340.0.0.0:* LISTEN 1761/nessusd tcp6 0 0 :::8834 :::*LISTEN 1761/nessusd

Re: [PacketFence-users] Error communicatin with Nessus

Hello Akala, if nessus run on the same server then try 127.0.0.1 for the server ip. Also what return : netstat -nlp | grep 8834 Regards Fabrice Le 2017-07-28 à 12:09, Akala Kehinde via PacketFence-users a écrit : > Just FYI, the Nessus server runs on the PF server. > > Regards, > Kehinde >

Re: [PacketFence-users] Error communicatin with Nessus

Just FYI, the Nessus server runs on the PF server. Regards, Kehinde On Fri, Jul 28, 2017 at 5:53 PM, Akala Kehinde wrote: > Hallo Guys, > > Quick one.. > I get this error when PF tries triggering a violation: > > Checked line 96 and seems it's an error with the creds,

[PacketFence-users] Error communicatin with Nessus

Hallo Guys, Quick one.. I get this error when PF tries triggering a violation: Checked line 96 and seems it's an error with the creds, but creds is right. Or is the creds not supposed to be that on the Nessus server? Jul 8 13:57:58 pfence pfqueue: pfqueue(10450) INFO: [mac:00:50:ff:25:ce:00]

[PacketFence-users] Error communicatin with Nessus

Hallo Guys, Quick one.. I get this error when PF tries triggering a violation: Checked line 96 and seems it's an error with the creds, but creds seems right. Or is the creds not supposed to be that on the Nessus server? Jul 8 13:57:58 pfence pfqueue: pfqueue(10450) INFO: