Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Askar <askarali@gmail.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: mangle squid packets
Date: Tue, 5 Jul 2005 23:18:16 +0500	[thread overview]
Message-ID: <a0f69e5050705111820d01eb5@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0507051347060.28524@yvahk01.tjqt.qr>

Before marking squid packets you have to define route with "ip"
iproute2 command more info could be find on www.lartc.org , below is
an example of iproute + iptables for your firewall machine.

echo 112 squid.out >> /etc/iproute2/rt_tables
ip rule add fwmark 3 table squid.out
ip route add default via xxx.xxx.xxx.xx dev eth0 table squid.out 
ip route flush cache

# repacle xxx.xxx.xx with squid server ip
#####
here is iptables part

iptables -A PREROUTING -i eth0 -t mangle -p tcp --dport 80 -j MARK --set-mark 3


regards

Askar
hope this would helps


On 7/5/05, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
> 
> >I dont know what mangle rule I need to mark squid transparent packets, I
> >have tried all the following (One at a time):
> 
> Because Squid practically starts a new connection, you need special help
> from squid itself to mark outgoing packets based on incoming ones.
> 
> This is done by TPROXY, a netfilter module from Balabit.com.
> Unfortunately, they do not have a version for 2.6.11 and up yet.
> 
> 
> 
> Jan Engelhardt
> --
> | Alphagate Systems, http://alphagate.hopto.org/
> 
> 
> 


-- 
I love deadlines. I like the whooshing sound they make as they fly by.
Douglas Adams


  reply	other threads:[~2005-07-05 18:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01 20:31 mangle squid packets marcus
2005-07-05 11:49 ` Jan Engelhardt
2005-07-05 18:18   ` Askar [this message]
2005-07-05 20:32     ` Jan Engelhardt

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=a0f69e5050705111820d01eb5@mail.gmail.com \
    --to=askarali@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=netfilter@lists.netfilter.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