From: "Spencer" Date: Mon, 16 May 2005 20:06:02 +0000 Subject: [LARTC] load balancing causes authentication problems? Message-Id: <00a101c55a5a$89462800$640fa8c0@hotsitespencer> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============1657507040==" List-Id: To: lartc@vger.kernel.org This is a multi-part message in MIME format. --===============1657507040== Content-Type: multipart/alternative; boundary="----=_NextPart_000_009E_01C55A1F.DCA95CA0" This is a multi-part message in MIME format. ------=_NextPart_000_009E_01C55A1F.DCA95CA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable We are currently using iproute2 to perform a round robin type load = balancing.=20 ip route add default proto static scope global=20 nexthop via XXX.XXX.XXX.XXX dev eth0 weight 1 nexthop via XXX.XXX.XXX.XXX dev eth1 weight 1 nexthop via XXX.XXX.XXX.XXX dev eth2 weight 1 From my understanding this is destination based load balancing. And it = has worked fine 99% of the time. The problem we are running into is for = web sites that have a separate authentication server. For example a = user authenticates on an authentication server through eth0. After = authentication the user is redirected to the application server, however = since the application server is a different destination the user can now = be routed out through eth1 or eth2. In the case that the user is routed = out through either eth1 or eth2 the application server now sees a = different ip address than the one used to authenticate and thus denies = the user access. It is also possible that I'm way off base and this is not at all = what is happening and is not the reason for users getting denied access = after authenticating, but that's what it looks like to me. I was = wondering if anyone else had seen a similar problem and had a possible = solution. I didn't see anything in the archives right off but I wasn't = sure exactly what to search for either. Thanks Spencer=20 ------=_NextPart_000_009E_01C55A1F.DCA95CA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
We are currently using iproute2 to = perform a=20 round robin type load balancing. 
ip route add default proto static scope = global=20
       =20             nexthop=20 via XXX.XXX.XXX.XXX dev eth0 weight 1
       =20             nexthop via=20 XXX.XXX.XXX.XXX dev eth1 weight 1
          &nbs= p;        =20 nexthop via XXX.XXX.XXX.XXX dev eth2 weight 1
 
From my understanding this = is destination=20 based load balancing.  And it has worked fine 99% of the = time. The=20 problem we are running into is for web sites that have a separate=20 authentication server.  For example a user authenticates on an=20 authentication server through eth0.  After authentication the user = is=20 redirected to the application server, however since the application = server is a=20 different destination the user can now be routed out through eth1 = or=20 eth2.  In the case that the user is routed out through either eth1 = or eth2=20 the application server now sees a different ip address than the one used = to=20 authenticate and thus denies the user access.
    It is also possible = that I'm way=20 off base and this is not at all what is happening and is not the reason = for=20 users getting denied access after authenticating, but that's what = it looks=20 like to me.  I was wondering if anyone else had seen a similar = problem and=20 had a possible solution.  I didn't see anything in the archives = right off=20 but I wasn't sure exactly what to search for either.
 
Thanks
Spencer 
 
------=_NextPart_000_009E_01C55A1F.DCA95CA0-- --===============1657507040== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc --===============1657507040==--