All of lore.kernel.org
 help / color / mirror / Atom feed
From: Esteban Ribicic <eribicic@UolSinectis.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ip rule and transparent proxy.
Date: Wed, 05 Mar 2003 15:59:44 +0000	[thread overview]
Message-ID: <marc-lartc-104688005203546@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104687131224590@msgid-missing>

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/

  parent reply	other threads:[~2003-03-05 15:59 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 [this message]
2003-03-06 14:18 ` Alessandro Ren
2003-03-06 15:11 ` Esteban Ribicic
2003-03-21 14:07 ` Alessandro Ren

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-104688005203546@msgid-missing \
    --to=eribicic@uolsinectis.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 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.