From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 2-3 uplinks, nat and failover...is it possible?
Date: Sun, 05 Jun 2005 18:05:04 +0000 [thread overview]
Message-ID: <42A33ED0.7DF30186@iswest.com> (raw)
In-Reply-To: <bb04248805060416566fb00fcf@mail.gmail.com>
aristo7514 aristo7514 wrote:
> I have a public IP block
> 81.8.124.1-81.8.124.63
and 172.17.whatever
as well as 172.18.whatever
and 81.8.120
:( ... Why do you confuse us with just the one?
> Here is the list for my ip addresses.
>
> eth0 has ip 172.16.55.1/255.255.255.0
> eth0:1 has ip 172.17.56.1/255.255.255.0
> eth0:2 has ip 172.17.57.1/255.255.255.0
> eth0:3 has ip 172.17.58.1/255.255.255.0
> eth0:4 has ip 81.8.124.1/255.255.255.192
I doubt that eth0:# is ever going to work because others have reported
failure to this ML under similar circumstances.
> eth1 has ip 81.8.120.18/255.255.255.252
> eth3 has ip 172.18.10.30/255.255.255.0
>
> One of my internet connection is 81.8.120.18/255.255.255.252 with
> gateway of 81.8.120.17 (Public)
>
> The other one is 172.18.10.30/255.255.255.0 with gateway of
> 172.18.10.2 (Behind an ADSL router)
Have you read Martin Brown's stuff at http://linux-ip.net/ ? If not,
you've missed (what I consider to be) the most understandable
documentation on the internet.
With Julian's patch, nano.txt and a reading of Martin you should be able
to use all the internet connections. Dead Gateway Detection may not
work depending on the number of hops to the dead gateway.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-06-05 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 23:56 [LARTC] 2-3 uplinks, nat and failover...is it possible? aristo7514 aristo7514
2005-06-05 18:05 ` gypsy [this message]
2005-06-05 21:03 ` Carl-Daniel Hailfinger
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=42A33ED0.7DF30186@iswest.com \
--to=gypsy@iswest.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 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.