From: Stanislav Nedelchev <stanislav.nedelchev@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: routing between 2 lines problem , after starting squid
Date: Fri, 07 Apr 2006 20:15:42 +0000 [thread overview]
Message-ID: <4436C86E.1040907@gmail.com> (raw)
It's Solved
Stanislav Nedelchev wrote:
> i'm using one line on eth2 only for web traffic
> eth1 is my internal line and eth0 is my main line to internet .
> i'm marking packets like this
>
> i have default route on eth0
>
> iptables -t mangle -A PREROUTING -i eth1 -p tcp --dport 80 -j MARK
> --set-mark 66
> iptables -t mangle -A PREROUTING -i eth1 -p tcp --sport 80 -j MARK
> --set-mark 66
> iptables -t mangle -A PREROUTING -i eth1 -p tcp --dport 3128 -j MARK
> --set-mark 66
> iptables -t mangle -A PREROUTING -i eth1 -p tcp --sport 3128 -j MARK
> --set-mark 66
>
> iptables -t mangle -A FORWARD -p tcp --sport 80 -j MARK --set-mark 66
> iptables -t mangle -A FORWARD -p tcp --dport 80 -j MARK --set-mark 66
> iptables -t mangle -A FORWARD -p tcp --sport 3128 -j MARK --set-mark 66
> iptables -t mangle -A FORWARD -p tcp --dport 3128 -j MARK --set-mark 66
>
>
> iptables -t nat -A POSTROUTING -o eth2 -p tcp --dport 80 -s
> 192.168.0.0/24 -d ! 192.168.0.0/16 -j MASQUERADE
> iptables -t nat -A POSTROUTING -o eth2 -p tcp --dport 3128 -s
> 192.168.0.0/24 -d ! 192.168.0.0/16 -j MASQUERADE
>
> i have also
> /sbin/ip route add 192.168.0.0/24 dev eth1 table natips
> /sbin/ip route add 127.0.0.0/8 dev lo scope link table natips
> /sbin/ip route add default via 217.10.248.1 dev eth2 table natips
> /sbin/ip route flush cache
> /sbin/ip rule add fwmark 66 table natips
>
>
> squid is running
> on 192.168.0.1:3128
>
> without squid it's working i'm using second line for web traffic
> with squid it's not working
>
> can anybody help me
>
> Thanks in advance.
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2006-04-07 20:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4436C86E.1040907@gmail.com \
--to=stanislav.nedelchev@gmail.com \
--cc=lartc@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