|
The incomming interface is a starfire.. not the eepro100
Here's tcpdump :
tcpdump port 80 -fn
Kernel filter, protocol ALL, TURBO mode (575 frames), datagram packet
socket
tcpdump: listening on all devices
22:58:02.206998 eth4 < 192.168.32.222.33257 > 192.168.35.199.http: S
950066482:950066482(0) win 5840 <mss 1460,sackOK,timestamp 41950996
0,nop,wscale 0> (DF)
22:58:05.203101 eth4 < 192.168.32.222.33257 > 192.168.35.199.http: S
950066482:950066482(0) win 5840 <mss 1460,sackOK,timestamp 41951296
0,nop,wscale 0> (DF)
22:58:11.202375 eth4 < 192.168.32.222.33257 > 192.168.35.199.http: S
950066482:950066482(0) win 5840 <mss 1460,sackOK,timestamp 41951896
0,nop,wscale 0> (DF)
and cat /etc/modules.conf
alias eth0 eepro100
alias eth1 starfire
alias eth2 starfire
alias eth3 starfire
alias eth4 starfire
Another nick in the black list ??
H.
On Tue, 2001-10-16 at 15:34, Julian Anastasov wrote:
>
> Hello,
>
> On 16 Oct 2001, Hervé Guehl wrote:
>
> > Repost.. I used the wrong mail account to send
> >
> > Hi,
> > I have a problem with ipvs 0.8.1...
> > In fact packets are not "forwarded"
> > here's what I can find with dmesg :
> > "IPVS: Incoming failed TCP checksum from 192.168.32.248 (size=40)!"
> > I am running 2.4.12, network card drivers eepro100 and starfire..
>
> Are the drivers from the kernel tree? We have reports from
> such checksum problems with the Intel's E100 driver and we still
> don't know where is the problem. This driver supports hardware
> checksuming, may be in CHECKSUM_HW form for the tested NIC. I still
> don't know whether they (the hw csuming) should work only for IA64,
> I'm reading their man page.
>
> > Made test on eth4 with 192.168.35.199/32 and 192.168.35.199/24
> >
> > Did I forgot something ??
> > PS: This works with the devel version 0.9.4..
>
> If these NIC drivers work with 0.9.4 then I really don't
> know where is the bug in IPVS 0.8.*. You better to use 0.9.4.
> With all these traps in the networking code, LVS should always receive
> CHECKSUM_NONE packets and so LVS is forced to make full packet check
> in LOCAL_IN. For the E100 driver a bad checksum results. So, I'm
> waiting for your feedback. I'm not able to debug the problem without
> such NIC. May be Ratz?
>
> > Regards
> > Hervé
>
> Regards
>
> --
> Julian Anastasov <ja@xxxxxx>
>
|
