Remote Users, Adding a Client
 

I've been trying to get the 'client_add' remoting option to work as I would expect, but maybe I'm expecting too much.

Trying to add a new client, I am setting the following variables:
What isn't working as expected, is the "limit_web_ip." What I am expecting is that when the user creates a new site, they will only be able to use the IP I set in this field, assuming it is one of the server's configured IP addresses. Am I correct?

If yes, it is not working properly. The user can still select the asterisk or any of the IP addresses assigned to the server. How do I resolve this?

If I am incorrect, is there any functionality built in that would allow this restriction?

Thanks

Youre wrong, the Limit you are searching for is set in the server_ip database table and not in the client table. See ispconfig interface: System > Server IP, there you assign the IP addresses to a client.

I understand how to do all this manually; I need it done automagically. Is there any way to assign an IP to a client using the remoting framework?

The functions to add / edit / delete server IP adresses have been added in the svn stable branch. I've added the chnaged files.

You can get the SVN stable release with:

svn export svn://svn.ispconfig.org/ispconfig3/branches/ispconfig-3.0.4

the required files are:

interface/lib/classes/remoting.inc.php
interface/web/admin/lib/remote.conf.php

Copy these files into your ispconfig installation, then enable the new functions in the remote user. The function names are:

server_ip_get, server_ip_update and server_ip_delete

I will check it out. Will this allow me to specify multiple clients per IP address or is it limited to 1 per IP? What I want to avoid is someone being able to select the asterisk when they're adding domains.

Edit: After changing all the domains to the asterisk, aside from those needing their ssl cert, nothing went awry. Must have been a misconfig on my part somewhere else causing the issue.

In ISPConfig a IP address is either visible to all clients (if no client is assigned to the IP) or one client.

The asterisk is a wildcard and not a IP, so its not affected by IP settings. The asterisk is always visible to all clients. Normally you would use the asterisk for all websites and assign only IP addresses to specific clients that need a sl website.

A function to disable the * wildcard will be availble in ISPConfig 3.0.5 as you can see in the roadmap:

http://bugtracker.ispconfig.org/inde...1977&project=3

I did see that in the roadmap. I believe what I ran into before is that when I selected the * for a domain, it messed with sites that didn't have the * and would show the wrong site. Say I went to www.a.com, it would show www.b.com.

The problem is that a IP address is priorized in favor of a wildcard by apache. But this can be avoided by the correct IP setup:

1) Create a "fake" client account and assign it the "main" ip which is internally used for all sites with *. So there is no site where this IP address is selected directly,all sites that point in DNS to this IP use * instead.

2) All websites that dont use SSL use *. The clients have no other choice then using * as there are no other IP's active on the server 'globally' and the only other IP is assigned to the fake client.

3) If you add a ssl site that requires a separate IP, add this new ip under system > Server IP and assign it to the client that owns this sl site. So this IP will only show up for him and no other customers.

In the SVN I wasn't able to find any examples or API docs on these functions. I'm guessing the usage is:
Is this correct?

The usage on all functions is similar. So if you refer to one of the _get functions, then you can pass an array as parameter to search or select values.