|
On 08-03-2002 00:15, "Roberto Nibali" <ratz@xxxxxxxxxxxx> wrote:
>> Wel you could configure it without a default gateway... No idea where NT
>> would send the packets then.
>
> The stack code drops them.
That's not what we want then, I want it to get send out on the LAN
>> Anyway, that seemed to be the problem (or one of the problems). Since there
>> is a default gateway, NT tries to find out where to send it to and sends arp
>> requests on the loopback adapter. Of course there is no response, so no ACK
>> from the server :((
>
> Are you 100% sure that the MS loopback adapter sends arp requests?
> And you definitely need a DGW for LVS_DR setups.
Yes, I used Windump on the MS loopback adapter, and if I had a request
routed from the LVS to the real server, I saw the SYN on the real-ip, and
the MS loopback adapter trying to get the MAC address of the gateway by
sending arp requests. Of course the request never leaves the machine, but
it's stuck there :((
>> So to solve this I have put the 'real ip' as default gateway (in this case
>> 192.168.202.141), problem is again that there is no arp going out so the
>> machine has no idea of the MAC address. So add the MAC address to the static
>> MAC table and voila, that seemed to do it.
>
> Very strange. What is the output of 'route show|print' on the NT box?
Below is a routing table before my default gateway change (the arp request
on the MS loopback was 'who-has 192.168.202.1')
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 d0 b7 91 5d 88 ...... Intel(R) PRO PCI Adapter
0x3 ...00 b0 d0 49 92 c4 ...... Intel 82557-based Integrated Fast Ethernet
0x4 ...20 4c 4f 4f 50 20 ...... MS LoopBack Driver
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.202.1 192.168.202.140 1
0.0.0.0 0.0.0.0 192.168.202.1 192.168.202.141 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.202.0 255.255.255.0 192.168.202.141 192.168.202.141 1
192.168.202.140 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.202.141 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.202.255 255.255.255.255 192.168.202.141 192.168.202.141 1
192.168.212.0 255.255.255.0 192.168.212.179 192.168.212.179 1
192.168.212.179 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.212.255 255.255.255.255 192.168.212.179 192.168.212.179 1
224.0.0.0 224.0.0.0 192.168.202.140 192.168.202.140 1
224.0.0.0 224.0.0.0 192.168.202.141 192.168.202.141 1
224.0.0.0 224.0.0.0 192.168.212.179 192.168.212.179 1
255.255.255.255 255.255.255.255 192.168.212.179 192.168.212.179 1
===========================================================================
Below is the new routing table (on another machine with rip 192.168.202.145)
after modifying like I9 did in previous posts
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 d0 b7 91 52 7b ...... Intel(R) PRO PCI Adapter
0x3 ...00 b0 d0 49 96 17 ...... Intel 82557-based Integrated Fast Ethernet
0x4 ...20 4c 4f 4f 50 20 ...... MS LoopBack Driver
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.202.1 192.168.202.145 1
0.0.0.0 0.0.0.0 192.168.202.145 192.168.202.140 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.202.0 255.255.255.0 192.168.202.145 192.168.202.145 1
192.168.202.140 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.202.145 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.202.255 255.255.255.255 192.168.202.145 192.168.202.145 1
192.168.212.0 255.255.255.0 192.168.212.183 192.168.212.183 1
192.168.212.183 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.212.255 255.255.255.255 192.168.212.183 192.168.212.183 1
224.0.0.0 224.0.0.0 192.168.202.140 192.168.202.140 1
224.0.0.0 224.0.0.0 192.168.202.145 192.168.202.145 1
224.0.0.0 224.0.0.0 192.168.212.183 192.168.212.183 1
255.255.255.255 255.255.255.255 192.168.212.183 192.168.212.183 1
===========================================================================
>
>> So I guess another option is to leave the default gateway blank...
>
> Not really. Just the one for the loopback.
That's what I meant :)), so leaving it blank for the loopback would solve
this also according to your experience ????
>> If there are other people who tried using NT realservers and failed, please
>> let me know, because it worked..., but it randomly failed on monday :((
>
> All NT systems I had to integrate with the LVS_DR approach worked
> flawlessly. And I did it how it is described in the LVS HOWTO.
Thanks for all that info :)
>> Now it seems to work better, so I'll put it up again next week
I'll keep you all posted :)
|
