Further examination of this reveals fixing it is as simple as a new forwarding rule from port 62003 to the ftp proxy.
Nevertheless my points still stand. Use a pre-existing protocol, on a standard port. Your requirements are not unique and your aim should be to make supporting a not particularly mainstream service easier for the users and sysadmins, than letting developers fart around with unnecessary custom protocols.
Custom FTP like protocol? You are fools. Port 62003 is blocked by default in any half decent firewall. A custom 'FTP like' protocol doesn't work with proxies specifically designed to handle real FTP - that work on every other FTP server, except yours.
WebDAV, rsync, scp or heck, HTTP/HTTPS with a couple of custom attributes is better than the mess that you've created.
Now I have to muck around trying to figure out how to push this through my OpenBSD firewall, which will probably involve writing custom code. I can expect no help in this, because when I report it to the OpenBSD community they will a) laugh at me a bit and b) rightly call the Desura developers idiots, because you've tried to overload a protocol. It's also not easily possible to debug this without looking up exactly what's custom about the protocol, instead of using existing tools if a well known protocol was used.
FTP is a deeply horrid protocol that was not designed for today's Internet, reacts extremely badly with firewalls and is lacking with features compared to more modern protocols. Anyone looking to use it in a new system needs their head examining.
Never re-invent the wheel - absolutely correct. Another valuable maxim is not to create something that looks mostly like a wheel but is actually a hexagon.
Stop wasting my time with something that should just work and use an existing protocol. No, I'm not going to consider using a less secure firewall that works with this broken protocol.
Syllopsium
Peter joined
This member has provided no bio about themself...