[43340] in North American Network Operators' Group
Re: sub-basement multihoming (Re: Verio Peering Question)
daemon@ATHENA.MIT.EDU (Rafi Sadowsky)
Fri Oct 5 19:16:42 2001
Date: Sat, 6 Oct 2001 01:15:41 +0200 (IST)
From: Rafi Sadowsky <rafi-nanog@meron.openu.ac.il>
Reply-To: <nanog@merit.edu>
To: Vadim Antonov <avg@exigengroup.com>
Cc: <nanog@merit.edu>
In-Reply-To: <Pine.LNX.4.10.10110031648190.19274-100000@arch.exigengroup.com>
Message-ID: <Pine.GSO.4.31.0110060102150.2214-100000@meron.openu.ac.il>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
Anyone ever try using the RADWARE LinkProof ?
(or similar - are there any others ? )
<http://www.radware.com/content/products/link.htm>
It looks like a combination between link monitoring & NAT'ing internal
address the the "best" ISP's NetBlock
Thanks
- Rafi
--
Rafi Sadowsky rafi@noc.ilan.net.il
Network Operations Center | VoiceMail: +972-3-646-0592 FAX: +972-3-646-0454
ILAN - IUCC -I2(Israel) | FIRST-REP ILAN-CERT(CERT@CERT.AC.IL)
(Israeli Academic Network) | (PGP key -> ) http://telem.openu.ac.il/~rafi
On Wed, 3 Oct 2001, Vadim Antonov wrote:
>
>
>
> On Wed, 3 Oct 2001, E.B. Dreger wrote:
>
> > > Meanwhile, the problem is that the demand to do fancy routing
> > > things outstrips the Internet's current collective ability
> > > to supply it. As a result, we have to say "no" (or more $ than
> > > you can afford) to alot of things that seem worthwhile. One of
> >
> > Yes. Put bluntly, technology is not serving its users. It's the
> > oil-burning '73 Nova that won't die: far from ideal, but it
> > still runs, so we may as well use it instead of buying a new
> > car...
>
> I would really love to hear if anyone invented a way to do global routing
> with anything better than combination of flooding of aggregated
> reacheability information and defaut routes.
>
> It is not technology per se, it's the underlying concept which is barely
> adequate.
>
> --vadim
>
> PS I too have a pair of diverse DSLs and use combination of DNS
> (for ingress) and hash-based load sharing (for egress) packet
> routing. The resulting paths are sometimes hugely far from
> optimal.
>
>
