> oommen> raju> Fairly straightforward. The simplest method is to use a seperate
> oommen> raju> network (and consequently IP address) for each card, so that (e.g.)
> oommen> raju> ftp.xyz.com becomes 192.168.1.x while www.xyz.com becomes
> oommen> raju> 10.10.10.x. This way all ftp/http requests automatically get routed to
> oommen>
> oommen> This seems possible.
> oommen> How to do this with IP addresses - using ipfwadm ?
> oommen>
> oommen> raju> the appropriate network interface and network. Tell your FTP and WWW
> oommen> raju> daemons to bind to these addresses (how to do that depends on which
> oommen> raju> programs you are using).
> oommen> raju>
> oommen>
> oommen> We use Apache 1.2.6 and wu-ftpd (Version wu-2.4.2-academ[BETA-16](1) Thu
> oommen> May 7 23:18:05 EDT 1998)
> oommen>
>
> In Apache, we can use BindAddress directive, but what about ftpd?
> I doubt whether it is possible to bind an IP addr is ftp.
ftpd is normally run from inetd. If you use xinetd, it is possible to
specify that a service binds to a specific IP address (you could
always modify inetd to do the same thing).
Another alternative is to use e.g. faucet (from the netpipes) package
to run ftpd. Again, this allows you to bind to a specific IP address.
-- Glynn Clements <glynn@sensei.co.uk> - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu