lvs-users
|
To: | tc lewis <tcl@xxxxxxxxx> |
---|---|
Subject: | Re: route on non-ip interface? |
Cc: | Joseph Mack <mack.joseph@xxxxxxx>, lvs-users@xxxxxxxxxxxxxxxxxxxxxx |
From: | Joseph Mack <mack@xxxxxxxxxxx> |
Date: | Wed, 12 Jul 2000 20:05:15 -0400 (EDT) |
On Wed, 12 Jul 2000, tc lewis wrote: > what i'm asking is: does the director's eth2 need an ip on > 192.168.100.0/24, yes. All IPs in a network need to be in the same network for the machines to be able to talk to each other. In your case the eth2 on the director will need an IP on the 192.168.100.0/24 network. It doesn't matter that you aren't explicitely using that IP, but other network processes use it. arp looking out onto the realserver network from the director will ask "who has realserver1, tell IP at director eth2" Joe -- Joseph Mack mack@xxxxxxxxxxx |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: Announce ldirectord version 1.13, Horms |
---|---|
Next by Date: | Re: Initial load slow, after that snappy, Joseph Mack |
Previous by Thread: | Re: route on non-ip interface?, tc lewis |
Next by Thread: | Re: route on non-ip interface?, Ted Pavlic |
Indexes: | [Date] [Thread] [Top] [All Lists] |