From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] multipath device round robin not working?
Date: Tue, 16 Jan 2007 00:44:54 +0000 [thread overview]
Message-ID: <45AC2006.1040409@riverviewtech.net> (raw)
In-Reply-To: <45A8C870.2010806@gmail.com>
On 01/15/07 15:20, zutph3n@gmail.com wrote:
> Wow, that's a complicated solution. Nicely done:) But I think that's a
> bit too complicated for my setup.... thx for the input anyway.
Thanks.
Indeed the set up is not simple. You may consider talking with your ISP
and seeing if they can assign one of your links an IP on a different subnet.
I have found that ISPs that are worth their salt are willing to work
with you to help you resolve these types of problems.
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-01-16 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 11:54 [LARTC] multipath device round robin not working? zutph3n
2007-01-14 9:26 ` Alex Samad
2007-01-15 4:14 ` Grant Taylor
2007-01-16 0:44 ` Grant Taylor [this message]
2007-01-16 19:52 ` Alex Samad
2007-01-17 5:04 ` Grant Taylor
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=45AC2006.1040409@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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