From: "Alessandro Ren" <alessandro@opservices.com.br>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] ip rule and transparent proxy.
Date: Fri, 21 Mar 2003 14:07:36 +0000 [thread overview]
Message-ID: <marc-lartc-104825577517554@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104687131224590@msgid-missing>
I found a way to do that.
You have to mark tha packet on the OUTPUT, make a rule for that mark
to go to where you want and you must set the tcp_outgoing_address in the
squid.conf file to match the IP address of the interface you want the squid
to start the connections from.
It's working flawlessly for me.
The only think is, if link on this interface goes down, squid will
not be able do access the internet anymore. I just wrote a script that
checks this interface and if its down, changes the squid configuration file
disabling the tcp_outgoing_address.
[]s.
-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl] On
Behalf Of Esteban Ribicic
Sent: Thursday, March 06, 2003 12:11 PM
To: Alessandro Ren
Cc: 'LARTC'
Subject: RE: [LARTC] ip rule and transparent proxy.
yeah, try natting the packet on the rule so src addreess will chanche. that
might work.
or try looking on squids patches or docu if you can specify anything on it.
greets
On Thu, 2003-03-06 at 11:18, Alessandro Ren wrote:
>
> It did't work becasue the packet is trying to go out on the
secondary
> interface using the address of the primary interface, so the packet
> get dropped by the ISP.
> Well, the MARK on the OUTPUT mangle worked well actually, deviating
> the traffic, just creating the source address problem.
>
> Am I forgetting something?
>
> Thanks.
>
> -----Original Message-----
> From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]
> On Behalf Of Esteban Ribicic
> Sent: Wednesday, March 05, 2003 1:00 PM
> To: Stephane Ouellette
> Cc: Esteban Ribicic; Alessandro Ren; LARTC
> Subject: Re: [LARTC] ip rule and transparent proxy.
>
>
> after marking the packet, it is posible to route over ip (marking in
> output)...packet goes to the gw you choose..routeing after is other
> issue, as you cant know or predict what will do your isp router.
>
> the packet will go where you told him to go (through fwmarks) with src
> address as kernel algorithm says so (probably, if not bind() called,
> the ip address of the interface on wich the default gw is setted)..
>
> if the src address of the packet does not match with the interface you
> choose, is probably that the packet leaves the interface and never
> come back -my scpecial case, is that my two links are from the same
> isp and they route the packet trgout a default route in their router-
> ..so packets leaves from one interface and comes in the other... but,
> you can (i hvent tryed this, but i think it should work) nat the src
> adress and packet will go and come....maybe you shlud nat the packet
> again when it comes...
> example: ip rule add from all fwmark 0x1 nat [your ip] table pppx..for
> example..
>
> i have working hwat i said on my linux box for squid packets..the go
> from one interface and come in the other.
>
> steve
>
> On Wed, 2003-03-05 at 12:40, Stephane Ouellette wrote:
> > Esteban Ribicic wrote:
> >
> > >you should try marking squid packets (output chain for example) and
> > >then add a rule (ip rule ls).. in lartc.org
> > >http://www.lartc.org/lartc.pdf have plenty of examples.
> > >
> > >
> >
> > Unfortunately, this will not work. It is not possible to route a
> > locally-generated packet using a firewall mark because the routing
> > decision is taken before the packet is sent to the MANGLE OUTPUT chain.
> > Routing a packet using a firewall mark works only in the
> > PREROUTING
> > Netfilter hook.
> >
> > Stephane Ouellette
> >
> > >tips: when marking packets on iptables, use hexa not decimal
> > >notting.
> > >try patching the kernel if does not work (http://www.ssi.bg/~ja/)
> > >cause kernel default source may not work...
> > >
> > >and its probably that squid use as source adrres of ip header the
> > >ip
> > >on the default route, so you might have to nat that src to the other
> > >interface (so packets leave the interface you want and come back in
> > >that interface and not the other -if they come..- )
> > >
> > >greets and good speed.
> > >
> > >On Wed, 2003-03-05 at 10:27, Alessandro Ren wrote:
> > >
> > >
> >
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
--
Esteban Ribicic
Network Operation Center
UOL-Sinectis S.A.
Florida 537 Piso 6, Buenos Aires, Argentina
+54-11-4321-9110 Ext 2503
+54-11-4321-9107 Directo
eribicic@uolsinectis.com
www.uolsinectis.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-03-21 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 13:27 [LARTC] ip rule and transparent proxy Alessandro Ren
2003-03-05 13:47 ` Esteban Ribicic
2003-03-05 15:40 ` Stephane Ouellette
2003-03-05 15:59 ` Esteban Ribicic
2003-03-06 14:18 ` Alessandro Ren
2003-03-06 15:11 ` Esteban Ribicic
2003-03-21 14:07 ` Alessandro Ren [this message]
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=marc-lartc-104825577517554@msgid-missing \
--to=alessandro@opservices.com.br \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.