reseller setting issues

I setup a reseller account and have found a few things and am curious how to change them: I am not able to get the resellers domains they create to auto-allocate ipv6 form a given range of ip addresses. it only sets the ip address at the system default or the one i set..the ability to auto-apply a singular, upwardly incremental address is not obyed at reseller account creation and the option is not presented to the reseller at all and there for all reseller initialized accounts are stuck at the system default

The resellers php execution time was set at 40 seconds despite the main system being set to 300. All account under the root admin follow the settings for the main system while reseller created accounts default to 40 seconds.

As i find more i'll add more threads.

Status: 
Fixed (pending)

Comments

For the IP allocation - are you looking for a way to define an IP range that will be used specifically for that reseller's new virtual domains?

I am not able to get the resellers domains they create to auto-allocate ipv6 form a given range of ip addresses. it only sets the ip address at the system default or the one i set..the ability to auto-apply a singular, upwardly incremental address is not obyed at reseller account creation and the option is not presented to the reseller at all and there for all reseller initialized accounts are stuck at the system default

Any updates on this? Is there any further information you require?

So do you mean that on the domain creation form for resellers, there is no option shown to allocate an IPv6 address?

there is..but virt doesn't obey it.

Do you mean that on the domain creation form, the resellers don't even see the "IPv6 network interface" field?

I put EXACTLY what is going on in the ticket...would you like pictures?

Ok I get it now - and I found the bug that causes this. You should be able to grant a reseller permissions to using IPv6 addresses on the Edit Reseller page, but the option for that is missing currently. It will be fixed in the next Virtualmin release.

has this been fixed?

This was added to our source control when Jamie posted above, though it doesn't look like we've had a new release since the fix was made.

That'll go out with our next release... while I don't have an ETA, it should be fairly soon.