From: senthilkumaar2021 <senthilkumaar2021@gmail.com>
To: marek@piasta.pl
Cc: netfilter@vger.kernel.org
Subject: kernel panic
Date: Mon, 17 May 2010 15:12:09 +0530 [thread overview]
Message-ID: <4BF10F71.2050409@gmail.com> (raw)
Hi
Thanks for the reply
I was using kernel 2.6.28.5 and 2.6.30.5 but i got kernel panic in both
versions
my iptable and ebtable are as follows
iptables -t mangle -N DIVERT
iptables -t mangle -A DIVERT -j MARK --set-mark 1
iptables -t mangle -A DIVERT -j ACCEPT
iptables -t mangle -A PREROUTING -p tcp -m socket -j DIVERT
iptables -t mangle -A PREROUTING -p tcp --dport 80 -j TPROXY --tproxy-mark 0x1/0x1 --on-port 3129
ebtables -t broute -A BROUTING -i $CLIENT_IFACE -p ipv4 --ip-proto tcp --ip-dport 80 -j redirect --redirect-target DROP
ebtables -t broute -A BROUTING -i $INET_IFACE -p ipv4 --ip-proto tcp --ip-sport 80 -j redirect --redirect-target DROP
Regards
senthil
> Hi,
>
> >I am using iptables version 1.43 and getting the following error in
> >machine while using squid in tproxy.we are using Linux machine as
> >bridge too
> >i was able to capture part of the error only please help me in solving
> >the issue
>
> What kernel version are you using? I don't know if it's the same
> problem but I was experiencing kernel panic with tproxy in recent
> kernels if there were any traffic to port 80 to the box itself. I was
> able to workaround the problem using RETURN target on the local traffic
> before "-m socket" match and DIVERT target.
>
> XX.XX.XX.XX in the example is the local box address.
>
> My mangle starts this way:
>
> IPTM="${IPT} -t mangle"
> echo $" * Launching mangle RULEZ..."
>
>
> # Setup a chain DIVERT to mark packets
> $IPTM -N DIVERT
> $IPTM -A DIVERT -j MARK --set-mark 1
> $IPTM -A DIVERT -j ACCEPT
>
> # Bez przekierowywania na proxy w przypadku polaczen do
> lokalnego serwera www (videocache)
> $IPTM -A PREROUTING -p tcp -d XX.XX.XX.XX --dport 80 -j ACCEPT
>
> # Use DIVERT to prevent existing connections going through
> TPROXY twice
> $IPTM -A PREROUTING -p tcp -m socket -j DIVERT --dport 80
> # regula dla ruchu klienci->swiat
> $IPTM -A PREROUTING -p tcp -m socket -j DIVERT --sport 80
>
>
> Hope this helps.
>
> Best regards,
> Marek
next reply other threads:[~2010-05-17 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 9:42 senthilkumaar2021 [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-17 8:55 kernel panic senthilkumaar2021
2006-09-25 12:32 Jacques Rodary
2006-09-07 16:42 Miha Verlic
2006-03-31 4:31 Samuel Díaz García
2006-04-01 6:21 ` Samuel Díaz García
2003-04-16 12:45 Kernel panic Allshouse, Brian M (Sabre)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BF10F71.2050409@gmail.com \
--to=senthilkumaar2021@gmail.com \
--cc=marek@piasta.pl \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).