<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: iptables -m unclean interferes with cipe
From: Dragos <dragos.delcea,AT,farmexim,DOT,ro>
Date: Tue, 8 Jan 2002 09:43:31 +0100

hello,
having in my firewall rules something like "iptables -m unclean" 
makes cipe connection not to work; it tells me something like that in the 
logs:
---
Jan  8 08:48:51 link ciped-2.4.16-686[12086]: CIPE daemon vers 1.5.2 (c) Olaf 
Titz 1996-2000
Jan  8 08:48:51 link kernel: cipcb0: alloc
Jan  8 08:48:51 link kernel: cipcb: read_lock(&tasklist_lock) at 
../cipe/device.c:216
Jan  8 08:48:51 link kernel: cipcb: read_unlock(&tasklist_lock) at 
../cipe/device.c:220
Jan  8 08:48:51 link kernel: cipcb0: setpar
Jan  8 08:48:51 link kernel: cipcb0: setpar 0.0.0.0:0 1000 60000 0200 0
Jan  8 08:48:51 link kernel: cipcb0: setkey
Jan  8 08:48:51 link kernel: cipcb0: attach
Jan  8 08:48:51 link kernel: cipcb0: opened
Jan  8 08:48:51 link ciped-2.4.16-686[12086]: sendctl: Operation not permitted
---
is this a known thing?
is there a workaround? (besides commenting the firewall rule...) why iptables 
thinks this traffic is unclean?
ah, by the way kernel 2.4.16 (debian) & iptables 1.2.4.

dragos





<< | Thread Index | >> ]    [ << | Date Index | >> ]