Unfortunately I've got another problem using CoreFTP Server Build 178:
I configured it to listen to two different IPs
the first one is my LAN IP
the second one is the IP of a virtual network created with an OpenVPN client
The configuration works fine when starting CoreFTP Server manually AFTER the second interface is already enabled (starting CoreFTP Server after OVPN client has established connection).
But since Openvpngui (I use) is starting in usermode, core ftp server does not listen to the second interface since it's not available at the time the ftp server starts.
The ability to start coreftp server in usermode does NOT solve the problem completely. Although this should give me the chance to force it starting after OVPN and might work in 'normal' cases, there still would be a problem if the vpn connection temporarily fails (the connection is configured to infinitely retry connecting).
Is it possible to bind to an interface that is currently not available when coreftp server starts? Chance for future implementations?
Nevertheless it would be a good thing to have the option of starting the server in user mode.
Thank you for your endeavour!
Listening on interfaces that are not yet available
-
- Posts: 3
- Joined: Thu Jan 11, 2007 12:39 am