Kernel 2.2.16 and weird DENY's with IP-Chains

From: Jim Woodward (jim@jim.southcom.com.au)
Date: Thu Jun 08 2000 - 19:20:15 EST


Hi All,

I just upgraded to Kernel 2.2.16 on my main box last night due to the bug
that was found with earlier kernels.

Since then however, i have been noticing one of my packet filter rules
tripping up every 6 minutes *exactly* six minutes apart (it looks like a
network broadcast)

Example follows:

Jun 9 09:22:23 jim kernel: Packet log: output DENY ppp0 PROTO=17
203.31.83.230:137 255.255.255.255:137 L=78 S=0x00 I=35322 F=0x0000 T=64 (#26)
Jun 9 09:27:23 jim kernel: Packet log: output DENY ppp0 PROTO=17
203.31.83.230:137 255.255.255.255:137 L=78 S=0x00 I=36691 F=0x0000 T=64 (#26)
Jun 9 09:32:23 jim kernel: Packet log: output DENY ppp0 PROTO=17
203.31.83.230:137 255.255.255.255:137 L=78 S=0x00 I=37954 F=0x0000 T=64 (#26)
Jun 9 09:37:23 jim kernel: Packet log: output DENY ppp0 PROTO=17
203.31.83.230:137 255.255.255.255:137 L=78 S=0x00 I=40007 F=0x0000 T=64 (#26)
Jun 9 09:42:23 jim kernel: Packet log: output DENY ppp0 PROTO=17
203.31.83.230:137 255.255.255.255:137 L=78 S=0x00 I=42621 F=0x0000 T=64 (#26)
Jun 9 09:47:23 jim kernel: Packet log: output DENY ppp0 PROTO=17
203.31.83.230:137 255.255.255.255:137 L=78 S=0x00 I=44436 F=0x0000 T=64 (#26)
Jun 9 09:52:23 jim kernel: Packet log: output DENY ppp0 PROTO=17
203.31.83.230:137 255.255.255.255:137 L=78 S=0x00 I=45573 F=0x0000 T=64 (#26)
Jun 9 09:57:23 jim kernel: Packet log: output DENY ppp0 PROTO=17
203.31.83.230:137 255.255.255.255:137 L=78 S=0x00 I=46502 F=0x0000 T=64 (#26)
Jun 9 10:02:23 jim kernel: Packet log: output DENY ppp0 PROTO=17
203.31.83.230:137 255.255.255.255:137 L=78 S=0x00 I=46883 F=0x0000 T=64 (#26)
Jun 9 10:07:23 jim kernel: Packet log: output DENY ppp0 PROTO=17
203.31.83.230:137 255.255.255.255:137 L=78 S=0x00 I=47694 F=0x0000 T=64 (#26)
Jun 9 10:12:23 jim kernel: Packet log: output DENY ppp0 PROTO=17
203.31.83.230:137 255.255.255.255:137 L=78 S=0x00 I=48733 F=0x0000 T=64 (#26)

Now I do have samba running on that system, but its configured to only
broadcast and be seen by my Ethernet and not to traverse the ppp dialup
link (I block all SMB traffic on the ppp interface)

Like I said before, this only started appearing after the upgrade from
2.2.14 to 2.2.16 - is there any changes in the kernel that may cause this
to appear?

Anyone have an idea?

Regards, Jim.

-
name : Jim Woodward
www : http://www.jim.southcom.com.au
email : jim@jim.southcom.com.au

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:16 EST