|
All,
After working with Julian and Joseph I found it was my NIC driver causing
the problems.
My director has 2 Intel eepro100 nic cards. I wasn't using the default
ee100pro driver that came with kernel 2.4.7, instead I was using the latest
(at the time I downloaded it) driver from intel for that NIC, e100-1.6.6 due
to an earlier bug in the eepro100 driver causing unrelated NFS problems.
After going back to the default eepro100 driver, my problem went away.
I just tried upgrading to Intel's now latest e100 driver (e100-1.6.13) to no
avail. Looks like I'm stuck using the default eepro100 driver suppied with
the kernel to make LVS on 2.4.7 work.
This problem is for both LVS-0.8.1 and LVS-0.9.3.
-----Original Message-----
From: Julian Anastasov [mailto:ja@xxxxxx]
Sent: Monday, September 10, 2001 1:03 PM
To: Jeremy Kusnetz
Cc: 'mack.joseph@xxxxxxx'; 'lvs-users@xxxxxxxxxxxxxxxxxxxxxx'
Subject: RE: SYN_RECV LVS_NAT on 2.4.7 kernel
Hello,
On Mon, 10 Sep 2001, Jeremy Kusnetz wrote:
> My client is 216.163.120.2 on a different box then the director.
BTW, what show these commands on the director:
ip route get from 216.163.120.2 to 10.75.0.2 iif eth0
ip route get to 216.163.120.2 from 10.75.0.2 iif eth1
And I assume that ping to 10.75.0.2 from the client host does not work.
Regards
--
Julian Anastasov <ja@xxxxxx>
|
