Virtual server clients collision

[Alan DeKok]

Stanislav Lorenc wrote:
> i have two (and more) virtual servers. Each server has own business
> logic, port and defined separate clients.

  Not exactly.  Virtual servers can have related ports and clients, but
they don't have their own ports and clients.

> I completely use SQL modules. Clients are stored in database.

  The clients in SQL are *global* clients.  They're not tied to a
particular listener.

> Failed to add duplicate client rb1_pentagon::wlan1::192.168.1.10
> rlm_sql (auth_cernovice_net_sql): Released sql socket id: 4
> rlm_sql (auth_cernovice_net_sql): Failed to add client 192.168.1.10
> (rb1_pentagon::wlan1::192.168.1.10) to clients list.  Maybe there's a
> duplicate?

  Because you can't have two clients with the same IP address.

> Virtual server name in debug message is right.

  That doesn't matter.  The virtual server in the debug message doesn't
mean what you think it means.  It means that when the global listener
receives a packet from that client, it's routed to the named virtual server.

  It does *not* tie the client to the listener used by that virtual server.

> I think, clients are shared between virtual servers.

 The clients in the DB are global.

> Clients aren`t duplicates. Clients has different passwords and are
> placed within different virtual servers.
> How I get separate client list?

  Source code patches.

  Alan DeKok.