The 192.168.0.100 address you are using on your local network is a private IP address for the LAN. It's not accessible from the outside.
What you need to do is configure your router to forward ports 20 and 21 to that address. Once you do that, attempting to FTP to the router's IP address (in your case, 24.150.163.218) will pass through to the internal computer.
That said, don't use FTP for this. FTP is highly insecure. For one thing, the username and password are broadcast in the clear for anyone to grab and use, not to mention all the data.
The contemporary solution is to use sftp (secure FTP). Forward a port on your router to port 22 on the LAN IP address, and, on your Mac, go to the Sharing preferences and click "Remote Login" and specify the username that is permitted to login. Note that this still uses a password, but nothing is transmitted in the clean anymore.
If you really want to secure it, you need to go to the Terminal.app and modify /etc/sshd_config and change the line that says:
#PasswordAuthentication yes
to
PasswordAuthentication no
(to do this, type 'sudo nano /etc/sshd_config'), and signal SSH to read the new settings:
sudo killall -HUP sshd
... after that, password-based logins will be disabled and the only way to login will be to use keys. You can create a key pair like so:
ssh-keygen -C "+Your Colleague's Name Here+" -f shortname
...which will create two keys, a public and a private key. The private key you give to your colleague, and the public key you add to ~shortname/.ssh/authorized_keys . When your colleague wants to connect using sftp, he would do something like:
sftp -oIdentityFile=/path/to/the/private/key [email protected]
...oh, and if the file is not already compressed, using the -C option to sftp will automatically compress the data for transmission.
Applications like Cyberduck support SFTP.