| 
 After using the ipvs-0.9.12-2.2.14 patch against 2.2.15 
the output of 
$ipvsadm 
on a director that has been setup for VS-DR gives weird output
(example below). The entry in /proc/net.../vs is also wierd.
I assumed I'd trashed something and so compiled 
ipvs-0.9.8-2.2.14-patch against a clean 2.2.14 kernel source
tree (the previous setup I was using) and used ipvsadm-0.9.8
to setup the LVS.
This doesn't fix the problem. Here's the output for 0.9.8-2.2.14
IP Virtual Server version 0.9.8 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port          Forward Weight ActiveConn InActConn
TCP  lvs.mack.net:telnet rr
  -> 255.255.255.255:49320       Masq    4194304 0          0         
TCP  lvs.mack.net:netpipe rr
  -> 255.255.255.255:49320       Masq    4194304 0          0      
Note the realservers were 192.168.1.x and not 255^4, 
the weights are wrong and I'm using DR not NAT. The
LVS doesn't work either.
In case I have put some new files somewhere,  
there are no new files in /sbin, /bin, /usr/bin/, /usr/sbin, 
/usr/local/bin, /lib , /usr/lib, /usr/local/lib and looking
with find doesn't find anything obvious
Any ideas anyone?
Thanks
Joe
-- 
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center, 
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
 |