Speed limiting wan/dns

[MONGi]

Hello,

I would like connect to the FTP within the local network without ssl, so I had adjust follow things:

Require_Encrypted_Auth = !-ioFTPD !-USER1 !-USER2 *
Require_Encrypted_Data = !-ioFTPD !-USER1 !-USER2 *

Ok, the connection works without ssl...but...if I limiting the bandwidth e.g. to :

Global_Outbound_Bandwidth = 1000

..."all" downloads limited.
If a user connected from a dns-provider with ssl or a user connected from the wan without ssl, the limiting is always active.

I would like ignore the transfer speed limit for users from the wan-network (internal).

Is this possible to solve?

Thank you in advance.

[Yil]

What you want to do is create more than one service / device in the configuration file. Instead of just using FTP_Service with the 'Any' device, create a 2nd device called 'Local' and a 2nd service called FTP_Local and set Device_Name to Local and choose a different port= number. This gives you complete control over everything. Don't forward that new port in your router and only local connections can access it so you can disable SSL and not speed limit it. Everyone else will use the original port/service and be speed limited. The server is very flexible in this regard and you can do pretty much anything you want except you'll have to use separate ports for differently configured services. There is no way to use one set of rules for a client connecting locally versus remotely using the same server port number.

To finish up you'll have to also add the new service to the [Network] section under Active_Services so it would be "FTP_Service FTP_Local" now.

[MONGi]

What you want to do is create more than one service / device in the configuration file. Instead of just using FTP_Service with the 'Any' device, create a 2nd device called 'Local' and a 2nd service called FTP_Local and set Device_Name to Local and choose a different port= number. This gives you complete control over everything. Don't forward that new port in your router and only local connections can access it so you can disable SSL and not speed limit it. Everyone else will use the original port/service and be speed limited. The server is very flexible in this regard and you can do pretty much anything you want except you'll have to use separate ports for differently configured services. There is no way to use one set of rules for a client connecting locally versus remotely using the same server port number.

To finish up you'll have to also add the new service to the [Network] section under Active_Services so it would be "FTP_Service FTP_Local" now.

Hi Yil.

Perfect! Everything works now as I had wished.

Thank you very much.

To a other time ;)