From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Fwmark problem - policy routing does not work.
Date: Sat, 27 Apr 2002 10:04:30 +0000 [thread overview]
Message-ID: <marc-lartc-101990186731417@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101958268206904@msgid-missing>
Hello,
On Sat, 27 Apr 2002, Thilo Schulz wrote:
> > It does not. The ip rule does that. Routing does not mangle packets, unless
> > the packet is locally generated and incomplete.
>
> it is generated locally in my case.
May be your problem is that LOCALOUT is after routing,
the socket already created connected route and is bound to
specific src IP. It is too late to mark packets just to select
different src IP via routing. May be you have to use SNAT to change
the src IP to the desired one. I didn't tried it and I don't know
whether it works. And I see in recent sources some funny things,
for example, ipt_local_hook(MANGLE) calls ip_route_me_harder from
LOCAL_IN but I'm not sure it will hurt your tests. May be you can
ask for new LOCAL_ROUTING hook where MANGLE can select different src
IP for different users before route connection :)))
> - Thilo Schulz
Regards
--
Julian Anastasov <ja@ssi.bg>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-04-27 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 17:23 [LARTC] Fwmark problem - policy routing does not work Thilo Schulz
2002-04-24 11:42 ` Thilo Schulz
2002-04-24 11:50 ` Stef Coene
2002-04-24 12:40 ` Thilo Schulz
2002-04-26 19:44 ` Adrian Chung
2002-04-26 20:01 ` Thilo Schulz
2002-04-26 20:08 ` Adrian Chung
2002-04-27 8:25 ` Arthur van Leeuwen
2002-04-27 8:51 ` Thilo Schulz
2002-04-27 10:04 ` Julian Anastasov [this message]
2002-04-27 11:40 ` Adrian Chung
2002-04-27 12:02 ` Arthur van Leeuwen
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-101990186731417@msgid-missing \
--to=ja@ssi.bg \
--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.