/ Zope / Apsis / Pound Mailing List / Archive / 2006 / 2006-03 / NAPT confuses pound

[ << ] [ >> ]

[ RE: [Pound Mailing List] Bad URL / ... ] [ pound, zope and SSL / Christian Sell ... ]

NAPT confuses pound
Victor Granic <victorgranic(at)yahoo.com>
2006-03-01 22:59:03 [ FULL ]
Hi there!

Intro:  I'm running pound 1.9 on a solaris 9 server.  I've had great
success with it and really appreciate the hard work invested in this
project.  Thanks!

Problem:  There are multiple public addresses which point to the pound
service which are translated by the firewall to private addresses bound
on the pound server.  No problem with this configuration.  Because a
large number of new sites are coming online soon and because I don't
have control over the cluster config, I was prompted to use unique
ports on the pound server to distinguish between the sites instead of
using unique IP addresses.  Here's a snippet of my config (urls changed
to protect the innocent):

ListenHTTPS 10.10.10.20,44301 /etc/pound/1.pem
ListenHTTPS 10.10.10.20,44302 /etc/pound/1.pem
ListenHTTPS 10.10.10.20,44303 /etc/pound/1.pem

    UrlGroup ".*"
    HeadRequire Host "www.aaa.com.*"
    Session COOKIE jsessionid 1800
    BackEnd 10.10.20.205,8094,1
    BackEnd 10.10.20.209,8094,1
    EndGroup

    UrlGroup ".*"
    HeadRequire Host "www.bbb.com.*"
    Session COOKIE jsessionid 1800
    BackEnd 10.10.20.229,8094,1
    BackEnd 10.10.20.234,8094,1
    EndGroup

    UrlGroup ".*"
    HeadRequire Host "www.zzz.com.*"
    Session COOKIE jsessionid 1800
    BackEnd 10.10.20.229,8094,1
    BackEnd 10.10.20.234,8094,1
    EndGroup

When I point my browser to www.aaa.com I get a 503 and pound writes to
the log that there's no backend for the specified request.  Here's how
the NAPT is configured on the firewall:

1.2.3.4:443 -> 10.10.10.20:44301
1.2.3.5:443 -> 10.10.10.20:44302
1.2.3.6:443 -> 10.10.10.20:44303

Anyone have any ideas why this doesn't work?

Thanks,

Victor

[...]

Re: [Pound Mailing List] NAPT confuses pound
Robert Segall <roseg(at)apsis.ch>
2006-03-06 11:43:38 [ FULL ]
On Wed, 2006-03-01 at 13:59 -0800, Victor Granic wrote:[...]

This is nothing to do with NAPT - it just means that there is no
back-end that fits your current request and that Pound can talk to.
Normally this is either a bad combination of URL pattern and
HeadRequire/HeadDeny or that all defined back-ends are currently dead.

In your case I would change the HeadRequire to read

    HeadRequire Host ".*www.aaa.com.*"

as I suspect your browser sends something else...[...]

MailBoxer