This example should quickly show you the possibilites of per-IP configurationwith vsftpd's tcp_wrappers integration. This is new with v1.1.3.To use this, you need vsftpd built with tcp_wrappers! This is accomplishedby editing "builddefs.h" and changing#undef VSF_BUILD_TCPWRAPPERSto#define VSF_BUILD_TCPWRAPPERSAnd then rebuild. If you are lucky your vendor will have shipped the vsftpdbinary with this already done for you.Next, to enable tcp_wrappers integration, you need this in your vsftpd.conf:tcp_wrappers=YESAnd you'll need a tcp_wrappers config file. An example one is supplied in thisdirectory: hosts.allow. It lives at /etc/hosts.allow.Let's have a look at the example:vsftpd: 192.168.1.3: setenv VSFTPD_LOAD_CONF /etc/vsftpd_tcp_wrap.confvsftpd: 192.168.1.4: DENYThe first line:If a client connects from 192.168.1.3, then vsftpd will apply the vsftpdconfig file /etc/vsftpd_tcp_wrap.conf to the session! These settings areapplied ON TOP of the default vsftpd.conf.This is obviously very powerful. You might use this to apply differentaccess restrictions for some IPs (e.g. the ability to upload).Or you could give certain classes of IPs the ability to skip connectionlimits (max_clients=0).Or you could increase / decrease the bandwidth limiter for certain classesof IPs.You get the point :-)The second line:Denies the ability of 192.168.1.4 to connect. Very useful to take care oftroublemakers. And now you don't need xinetd to do it - hurrah.