Hello. We are experimenting with Pound 2.1. Without Type it works
perfectly--it just round-robins through each BackEnd server (we have
two setup).

However, the target application requires that a client stay connected
to the same HTTP server. To support this, we are attempting to use
'Type IP'. However, I've found that when using 'Type IP', at least in
Pound 2.1, we are hitting the same BackEnd server for each request.
Specifically, we are hitting the first BackEnd server listed for the
Service in pound.cfg. I can verify and reproduce this condition from
several remote IP's, even with the TTL set to 1.

Perhaps we are doing something wrong?

Note, we are using lynx for testing to prevent client-side caching
during our testing.

Our configuration for pound follows. Notice that we disable
daemon-mode since we are using cronolog.

..
User            "pound"
Group           "pound"

LogLevel        3
Daemon          0

Alive           30

ListenHTTP
        Address ServerA
        Port    81
End

Service
        Session
                Type    IP
                TTL     1
        End

        BackEnd
                Address ServerB
                Port    80
        End
        BackEnd
                Address ServerC
                Port    80
        End
End
..

---
Puryear Information Technology, LLC
Baton Rouge, LA * 225-706-8414
http://www.puryear-it.com

Author:
  "Best Practices for Managing Linux and UNIX Servers"
  "Spam Fighting and Email Security in the 21st Century"

Download your free copies:
  http://www.puryear-it.com/publications.htm

Anyone have any ideas about this?

Monday, August 28, 2006, 7:30:18 AM, you wrote:

> Hello. We are experimenting with Pound 2.1. Without Type it works
> perfectly--it just round-robins through each BackEnd server (we have
> two setup).

> However, the target application requires that a client stay connected
> to the same HTTP server. To support this, we are attempting to use
> 'Type IP'. However, I've found that when using 'Type IP', at least in
> Pound 2.1, we are hitting the same BackEnd server for each request.
> Specifically, we are hitting the first BackEnd server listed for the
> Service in pound.cfg. I can verify and reproduce this condition from
> several remote IP's, even with the TTL set to 1.

> Perhaps we are doing something wrong?

> Note, we are using lynx for testing to prevent client-side caching
> during our testing.

> Our configuration for pound follows. Notice that we disable
> daemon-mode since we are using cronolog.

> ..
> User            "pound"
> Group           "pound"

> LogLevel        3
> Daemon          0

> Alive           30

> ListenHTTP
>         Address ServerA
>         Port    81
> End

> Service
>         Session
>                 Type    IP
>                 TTL     1
>         End

>         BackEnd
>                 Address ServerB
>                 Port    80
>         End
>         BackEnd
>                 Address ServerC
>                 Port    80
>         End
> End
> ..

> ---
> Puryear Information Technology, LLC
> Baton Rouge, LA * 225-706-8414
> http://www.puryear-it.com

> Author:
>   "Best Practices for Managing Linux and UNIX Servers"
>   "Spam Fighting and Email Security in the 21st Century"

> Download your free copies:
>   http://www.puryear-it.com/publications.htm