From: Lopsch <lopsch@lopsch.com>
To: Netfilter-Mailinglist <netfilter@lists.netfilter.org>
Subject: Re: semi OT: default route
Date: Wed, 20 Oct 2004 23:05:27 +0200 [thread overview]
Message-ID: <4176D317.1010004@lopsch.com> (raw)
I think this is really difficult to solve. Because you will have to bind
a connection to a certain interface and route. For example you start a
connection to a webserver over route A1. The answer will come back over
route A1 but what happens if you answer out again over the route A2 will
the server be able to answer or will it fail? Note the connection
started over A1 so the server will be awaiting packets from the IP of
the interface lying on route A1. So it will be necessary that a
process/connection keeps on one route. On our side where the router is
there is no problem conntrack will keep an eye on it but how will
servers react that get a SYN from an certain adress and then
confirmations on another IP?
next reply other threads:[~2004-10-20 21:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 21:05 Lopsch [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-20 19:56 semi OT: default route Daniel Chemko
2004-10-20 18:08 Daniel Chemko
2004-10-20 18:53 ` Lopsch
2004-10-20 13:25 Payal Rathod
2004-10-20 16:17 ` Jason Opperisano
2004-10-20 16:37 ` Nick Drage
2004-10-20 16:48 ` Jason Opperisano
2004-10-20 16:57 ` Payal Rathod
2004-10-20 18:24 ` Jason Opperisano
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=4176D317.1010004@lopsch.com \
--to=lopsch@lopsch.com \
--cc=netfilter@lists.netfilter.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.