|
> 19:44:44.141903 eth1 < router.external.smartbasket.com.64036 >
> vip.sidestep.com.www: S 1477353113:1477353113(0
> ) win 16384 <mss 1460,nop,nop,sackOK> (DF)
> 19:44:44.141926 eth1 > router.external.smartbasket.com.64036 >
> vip.sidestep.com.www: S 1477353113:1477353113(0
> ) win 16384 <mss 1460,nop,nop,sackOK> (DF)
> 19:44:44.142013 eth1 < router.external.smartbasket.com.64036 >
> vip.sidestep.com.www: S 1477353113:1477353113(0
> ) win 16384 <mss 1460,nop,nop,sackOK> (DF)
> 19:44:44.142024 eth1 > router.external.smartbasket.com.64036 >
> vip.sidestep.com.www: S 1477353113:1477353113(0
> ) win 16384 <mss 1460,nop,nop,sackOK> (DF)
> 19:44:44.142109 eth1 < router.external.smartbasket.com.64036 >
> vip.sidestep.com.www: S 1477353113:1477353113(0
> ) win 16384 <mss 1460,nop,nop,sackOK> (DF)
> 19:44:44.142121 eth1 > router.external.smartbasket.com.64036 >
> vip.sidestep.com.www: S 1477353113:1477353113(0
> ) win 16384 <mss 1460,nop,nop,sackOK> (DF)
Just without checking the other facts, this for me indicates a not
handled arp-problem or you're trying to connect to the VIP from
inside the cluster.
Best regards,
Roberto Nibali, ratz
--
mailto: `echo NrOatSz@xxxxxxxxx | sed 's/[NOSPAM]//g'`
|
