Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG  Not logged in

Back  |  Find  |  Login  |  Help

MOptions problem ?, posted by Alex H on Wed Feb 22 11:05:15 2006        Re: MOptions problem ?, posted by Alex H on Mon Feb 27 11:16:56 2006           Re: MOptions problem ?, posted by Holger Mundhahs on Mon Feb 27 13:26:31 2006              Re: MOptions problem ?, posted by Alex H on Tue Feb 28 09:56:55 2006                 Re: MOptions problem ?, posted by Alex H on Tue Feb 28 11:26:22 2006                    [SOLVED] Re: MOptions problem ?, posted by Alex H on Tue Feb 28 12:08:42 2006                       [SOLVED] Re: MOptions problem ?, posted by Stefan Ritt on Wed Mar 1 07:48:11 2006

Message ID: 1733     Entry time: Tue Feb 28 12:08:42 2006     In reply to: 1732     Reply to this: 1734 Icon:   Author: Alex H  Author Email: alex@synergie-inf.com  Category: Info  OS: Windows  ELOG Version: 2.6.1-1668  Subject: [SOLVED] Re: MOptions problem ?

Yop, I think I found the solution! I was in fact a conditions conflict! See the attached picture for easiest comprehension. My list box type's conditions (FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}) conflict with my Equipment's conditions. It seems that the condition ID must be unique across the whole elogd.cfg. So I have replaced my "Options Type = FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}" by : "Options Type = FWL1{101}, FWL2{102}, FWL4{103}, VPN1{104}, VPN2{105}, CLIVPN-PROC" and it works well !

Attachment 1: gotcha.gif  90 kB  | Hide | Hide all

ELOG V3.1.5-3fb85fa6