Re: iptables classifies ESTABLISHED packets as INVALID randomly [message #33575 is a reply to message #33562] |
Thu, 23 October 2008 07:01 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to previous message](/theme/ovz3/images/down.png) |
Tony2
Messages: 4 Registered: October 2008
|
Junior Member |
|
|
I forgot to show the log from iptables when the problem happens: it looks like this:
Oct 22 14:16:09 eu3 kernel: Detected-from-wiki: IN=venet0 OUT=eth0 SRC=192.168.100.130 DST=129.70.186.31 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=80 DPT=41348 WINDOW=5792 RES=0x00 ACK SYN URGP=0
Oct 22 14:16:09 eu3 kernel: Blocked-Invalid: IN=venet0 OUT=eth0 SRC=192.168.100.130 DST=129.70.186.31 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=80 DPT=41348 WINDOW=5792 RES=0x00 ACK SYN URGP=0
It looks like there is some problem with the connection tracking system. A workaround could be avoiding use of statefulness of iptables, but it doesn't sound like a good step.
|
|
|