On Thu, 14 Aug 2008, David Coulson wrote: > I have a number of IPVS rules configured like this. > > Prot LocalAddress:Port Scheduler Flags > -> RemoteAddress:Port Forward Weight ActiveConn InActConn > TCP 10.250.83.201:80 wrr > -> 169.254.1.20:80 Local 1 0 0 > -> 169.254.1.21:80 Masq 1 0 0 > > Everything works okay, however for connections where the forwarding > method is 'Local', the resulting TCP connection is not modified and in > the case above, we see connections still going to 10.250.83.201, rather > than 169.254.1.20. Is this the intended method,
yes. the replies have to come from the VIP, so the connection from the client has to terminate in the VIP. > and is there a work around so that the TCP connection is > modified such that the destination address of the TCP > connection is changed? have a look at this. http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.rewrite_ports.html#re-mapping_ports_with_iptables however since your setup is working the way it's supposed to, it would be easier to use it that way, rather than trying to break it. Joe -- Joseph Mack NA3T EME(B,D), FM05lw North Carolina jmack (at) wm7d (dot) net - azimuthal equidistant map generator at http://www.wm7d.net/azproj.shtml Homepage http://www.austintek.com/ It's GNU/Linux! _______________________________________________ LinuxVirtualServer.org mailing list - [email protected] Send requests to [EMAIL PROTECTED] or go to http://lists.graemef.net/mailman/listinfo/lvs-users
