From: Zealot <zealot0630@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] How to use different path for INCOME and OUTGOING package ?
Date: Wed, 27 Sep 2006 20:52:47 +0000 [thread overview]
Message-ID: <451AE49F.4090602@gmail.com> (raw)
there are 3 computers.
A-------------B--------------C
I want the outgoing packages of B go to C.
And receive responding package from A.
As soon as insert the routing entry:
ip route add 10.0.0.0/8 via C src B dev BC
B seems stop receiving packages from A.
Use tcpdump on B, I can get the package.
But, it seems that kernel check the routing table, and found that the
source address of the package coming form A is not in routing table of B
to A, actually, it is in the table of B to C,
then the package is dropped.
How to configure the kernel not to drop the package ?
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2006-09-27 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 20:52 Zealot [this message]
2006-09-27 21:14 ` [LARTC] How to use different path for INCOME and OUTGOING package Zealot
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=451AE49F.4090602@gmail.com \
--to=zealot0630@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