<p>thanks for your prompt response <br>i only have those picture taken from my fishy cell phone. what i understand is some issue with ebtables. it is posible to only use iptables rules for tproxy. many people use only iptables rules. i posted same issue to squid developer amos he said </p>
<div>" There are some patches for SYN related issues with TPROXY just appeared in the iptables/ebtables developer mailing lists. It may be related.<br>If in doubt try to get hold of Balabit who are the official authors and support group for tproxy kernel changes.<br>
Amos "</div>
<div><br><br> </div>
<div class="gmail_quote">On Tue, Sep 1, 2009 at 7:08 PM, KOVACS Krisztian <span dir="ltr"><<a href="mailto:hidden@sch.bme.hu">hidden@sch.bme.hu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br>
<div class="im"><br>On k, szept 01, 2009 at 03:27:55 +0600, Asif Bakali wrote:<br>> Hello one of my server FC11 x64 bit running Tproxy with combination of<br>> iptables + ebtables rules during peek hours machine was rash with given such<br>
> as error "kernel panic " . when i replace tproxy with netfilter and remove<br>> ebtables rules just use simple iptables with NAT rules everything was fine.<br>> anyone faced this issue before ? find below my configuration<br>
<br></div>I tried to have a look at your panic screen, but the picture you've<br>attached is very small, barely readable and seems to not contain the<br>message as a whole...<br><br>Do you have a picture of the full message with somewhat better resolution?<br>
<br>--<br><font color="#888888">KOVACS Krisztian<br></font></blockquote></div><br>