|
Yeah! The box is still down (or up but not communicating). If I dont setup
alias tunnels, how can I create two tunnel interfaces. I thought only one
ipip tunnel should be created and if you need others, they have to alias the
1st. How might this slow things down (besides the fact that they have to
encapsulate then deencapsulate)? Are there any other gotchas using ipip. I
use VS-TUN exclusively at my home office and it screams.
We dont have any goons at the remote site. These guys are providing
"colocation" which means they won't touch anything for free. I will be
putting a secure console server in place (HP's) so this will be my goon.
--kip
----- Original Message -----
From: "Peter Mueller" <pmueller@xxxxxxxxxxxx>
To: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, October 31, 2001 3:53 PM
Subject: RE: Geographically Distributed LVS
> |I thought this was going to be easy!
> |
> |--kip
>
> Assumption is the mother of all ******* ... unless you're running windows
> and using microsoft bob. yep that would be worse.
>
> what kind of things are you seeing in tcpdumps? or is the problem now
that
> the remote director box isn't up? setting alias tunl interfaces over
remote
> networks will probably slow down your project a lot :(. Why not have some
> goon admin over there setup a linux box and connect it to the director via
> serial? you could redirect console over it...
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
|
