Re: per_source on redhat 7.2

>Does the per_source option not apply for multi-homed 
>machines or is it in the works?

It applies the same. The per_source option uses the
connections remote address and the service entry in it
comparison. It does not look at the server's address for
the per_source option.

The source code lines in question are xinetd/access.c 317

if ( (SERVER_SERVICE( serp ) == sp) &&
     ( cop = SERVER_CONNECTION( serp ) ) ) {

sp is the server being executed, serp is the server in the
list & cop is its connection. So it reads, if the current
server is our server and its connections isn't null

line 324

if ( SC_IPV4( scp ) &&
     (cop->co_remote_address.sa_in.sin_addr.s_addr ==
     (CONN_XADDRESS(cp))->sa_in.sin_addr.s_addr) )
           n++;

cp is the currently executing server's connection, scp is
the currently executing servers configuration pointer. It
reads if the current server is configured as IPv4 and
address of the remote connection of the server found in the
server list is the same as the current servers remote
connection address, increment n.

and line 336

if ( n >= scp->sc_per_source )
      return( AC_PER_SOURCE_LIMIT ) ;

You can do a kill -USR1 pid_of_xinetd to dump the internal
state of xinetd to /var/run/xinetd.dump. That file should
give you the value for per_source. You might want to see
what its using. Also, you can add some msg() statements to
collect more data if you are inclined to programming.

I have my server setup the same way you describe. One ftp
for each website. I let them have 2 connections each. The
server I use has 12 ip address. So its a smaller version of
your setup. So far I have not been able to duplicate the
problem.

-Steve Grubb

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com