Thanks, after upgrading to iptables 1.2.5 from source, everything worked as usual. I do not know the reason why, but it works :)
Greetings Am Mon, 2002-02-25 um 19.53 schrieb Ramin Alidousti: > I believe tahat you need to specify integers instead of string > literals. > > #define KERN_EMERG "<0>" /* system is unusable */ > #define KERN_ALERT "<1>" /* action must be taken immediately */ > #define KERN_CRIT "<2>" /* critical conditions */ > #define KERN_ERR "<3>" /* error conditions */ > #define KERN_WARNING "<4>" /* warning conditions */ > #define KERN_NOTICE "<5>" /* normal but significant condition */ > #define KERN_INFO "<6>" /* informational */ > #define KERN_DEBUG "<7>" /* debug-level messages */ > > > Ramin > > On Mon, Feb 25, 2002 at 04:31:03PM +0100, Jochen Witte wrote: > > > Hi, > > > > I had the following rule with kernel 2.4.6 and iptables 1.2.1a: > > > > iptables -A INPUT ....-j LOG --log-level info > > > > Now I switched to kernel 2.4.17 and iptables 1.2.3. This produces: > > > > iptables1.2.3: log-level 'info' ambiguous. > > > > What is up here? How can I set the severity? Or did I miss something > > new? > > > > Greeting > > > > -- > > Jochen Witte > > <[EMAIL PROTECTED]> > > PGP fingerprint = 2F92 97EA BB67 E49A EE79 AD55 2FE7 DF05 EA9A 3A32 > > Keyserver = www.keyserver.net > > > -- Jochen Witte <[EMAIL PROTECTED]> PGP fingerprint = 2F92 97EA BB67 E49A EE79 AD55 2FE7 DF05 EA9A 3A32 Keyserver = www.keyserver.net
