From: don-lartc@isis.cs3-inc.com (Don Cohen)
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Solved: Using more than 1 Internet Line
Date: Tue, 04 Dec 2001 16:56:40 +0000 [thread overview]
Message-ID: <marc-lartc-100748486503298@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100742079800981@msgid-missing>
Arthur van Leeuwen writes:
> > This problem could be fixed by extending TCP (and of course, changing
> > the kernel) to support multiple IP addresses. I suggest a new option
> > that says "here's another IP address for me" (or perhaps, here's an
> > alternative IP/port). The kernel then has to merge these two input
> > streams. On the output side (when you send to someone who has told
> > you about alternative addresses) I can think of several ways to
> > control which address you send to. I suppose the application should
> > have some way to influence that, but as a first stab, I suggest that
> > whenever tcp has to resend a packet, it should move to the next
> > address.
...
> Oh, you're talking about implementing it at the TCP level? Right then...
> right. That should be possible... if only programs couldn't bind to specific
> addresses...
Right, I forgot about the other half, what interface programs will
have to control their own alternative addresses.
While I do think there should be such interfaces, I suggest a default
that does the "right" thing for applications that don't know about the
extension. There should be some command to tell the kernel about the
alternatives, e.g., whenever you allocate a port for address 1.2.3.*
you should also allocate alternatives for addresses 6.7.8.9 and
4.5.6.7.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-12-04 16:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 19:24 [LARTC] Solved: Using more than 1 Internet Line Christoph Simon
2001-12-02 19:41 ` Christoph Simon
2001-12-03 20:22 ` Whit Blauvelt
2001-12-03 20:45 ` Christoph Simon
2001-12-03 21:43 ` Julian Anastasov
2001-12-03 22:04 ` Arthur van Leeuwen
2001-12-03 22:19 ` Christoph Simon
2001-12-03 22:33 ` Whit Blauvelt
2001-12-03 22:44 ` Julian Anastasov
2001-12-04 8:52 ` Arthur van Leeuwen
2001-12-04 10:57 ` Julian Anastasov
2001-12-04 11:05 ` Christoph Simon
2001-12-04 16:13 ` Don Cohen
2001-12-04 16:20 ` Arthur van Leeuwen
2001-12-04 16:56 ` Don Cohen [this message]
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-100748486503298@msgid-missing \
--to=don-lartc@isis.cs3-inc.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