From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Iptables, SNAT/MASQ, Multiple gateways
Date: Mon, 30 Sep 2002 19:23:01 +0000 [thread overview]
Message-ID: <marc-lartc-103341378009058@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103332395202631@msgid-missing>
Hello,
On Mon, 30 Sep 2002, Michael T. Babcock wrote:
> Don Cohen wrote:
>
> >I actually sent a proposal to this list that I think provides a good
> >solution to the general problem: an extension to TCP (possibly even
> >IP) that supports multiple addresses/ports. This would even allow you
> >to switch addresses in the middle of a connection. I think what I
Yes, we can implement it as separate IP protocol :)
Of course, at the beginning the idea may sound too stupid, we
have to change that. May be there is already solution for that?
A "simple" tunnel without encryption that will support failover
and balancing of the negotiated traffic, ability to negotiate
multiple IPs for each endpoint. Of course, there should be some
problems with the proper tunneling of this traffic in each end,
see how difficult is routed the IPSec traffic. Each endpoint will do
failover detection of all negotiated links and will do balancing (if
desired) over these links, based on relative ratio. This tunnel
should be transparent to the upper layers (TCP/UDP/ICMP/SCTP).
> SCTP actually supports this already; look it up -- its quite a bit
> different from TCP but allows you to do all the same types of things,
> with more options.
But this feature is only for SCTP. We want the traffic
from one multihomed router to use multiple links when talking
to another router, both understanding this "our new" IP tunneling
protocol.
I see it in this way: when such packet is received, we
decapsulate it and place it on the expected interface. As
result, the upper layers will see the packet on the right
input interface even if it is received on another input
interface (for example, if it is the only alive).
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-09-30 19:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 18:24 [LARTC] Iptables, SNAT/MASQ, Multiple gateways Simon Matthews
2002-09-29 22:45 ` José Luis Domingo López
2002-09-30 5:18 ` Don Cohen
2002-09-30 7:06 ` Simon Matthews
2002-09-30 15:55 ` Don Cohen
2002-09-30 17:05 ` Michael T. Babcock
2002-09-30 18:11 ` Jose Luis Domingo Lopez
2002-09-30 19:23 ` Julian Anastasov [this message]
2002-09-30 19:24 ` Simon Matthews
2002-09-30 19:26 ` Simon Matthews
2002-09-30 19:41 ` Greg Scott
2002-10-01 4:12 ` William L. Thomson Jr.
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-103341378009058@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.