From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Fwmark problem - policy routing does not work.
Date: Wed, 24 Apr 2002 11:50:58 +0000 [thread overview]
Message-ID: <marc-lartc-101965022826641@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101958268206904@msgid-missing>
> Yes, they do.
> I am also sure now, that marking is working:
> I have tried the same on another host that uses a gateway to access the
> internet, but has several ips on the net. If i do not enter the route (via
> option) the packets are not reaching their destination, if i am creating
> those as a given user, as all other user it does work. If i give the via
> option in the "ip route add table thilo src ....." command, the packets are
> reaching their destination again - yet even though i have given the source
> ip that should have been used, it is still using the primary one.
>
> Could this be a bug in the routing code?
I can only help you with the marking stuff :(
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
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-24 11:50 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 [this message]
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
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-101965022826641@msgid-missing \
--to=stef.coene@docum.org \
--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