On Monday 13 June 2005 01:02, Henrik Nordstrom wrote: > > If the ftp server ran on its own ip > > address, then qemu could simply set up new servers on new ports for the > > new data connections and have the client connect to them. > > You already have the router virtual IP address under your (or SLIRP) full > control. No need to invent additional addresses imho.
I don't think this is a good idea. The current behaviour is to automatically forward connections to the router on to the host. INMO this is very useful and desirable behaviour, so any new services should be added on a different virtual IP. We already use additional addresses for dns, tftp and SMB. > I don't see why active should be much harder than passive. SLIRP already > have support for both accepting and making connections both ways. Just > use what there is. There will be a somewhat hefty state machinery involved > however.. writing an FTP daemon within SLIRP is considerably more complex > than the same thing as a stand-alone daemon. It doesn't have to be. You can use the same trick as the fork_exec code does. ie. the ftp code listens on a localhost socket, and use the normal slirp connection forwarding. Paul _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
