i tossed my ftp up 192.168.0.115 for anyone wanting to DL my new zip package with some redone bab-5 and sg1 models. basically i made them a bit more refined. tships file is included to cut/paste to yours.
email me if any problems logging in
login is guest pass welcome
balogs ftp up for a bit
Moderators: Moderators for English X Forum, Scripting / Modding Moderators
Heya Balogt! What you listed for an IP address is your Local Area Network address. You'll need to provide your internet IP for people to access your FTP. Probably the quickest way to get that address is through something like http://whatsmyip.org/. You'll see your Internet IP in bold at the top of the page there.
Thanks a lot for access to the resources!
Thanks a lot for access to the resources!
ftp address for balogs ftp
according to whatsmyip.org its 24.65.199.204 someone try it. although my
ftp server program says its the 192.168.0.115 still? any way to get the
ftp program to grab that address instead?
ftp server program says its the 192.168.0.115 still? any way to get the
ftp program to grab that address instead?
We are bordering Off-Topic here, but since it is essentially about getting access to scripts ... 
NAT. Network Address Translation. Your machine has address that can be used only in private LAN. Your machine connects to some other network device that connects to Internet Service Provider that connects to WAN, aka inet. And responses return the same route. Now one box in the line has that public IP address, and address within your LAN. Your machine probably calls it a gateway or router. And that router translates (NAT) the private source address of your server into its public address.
But now suppose you call from outside. The call goes to the router. It thinks that it is the destination, does no NAT, and then refuses the connection since it is no FTP server. If you do have control of that router, then there is "port forwarding" (aka "demilitarized zone") that may be possible. To tell the router to pass FTP from outside forward to you. Standard "you will open your firewall for attacks to FTP" warnings do apply.
Option B: The ISP firewall drops all incoming connections for all clients. Nothing that you can do. That is why there exists public filesharing services.
NAT. Network Address Translation. Your machine has address that can be used only in private LAN. Your machine connects to some other network device that connects to Internet Service Provider that connects to WAN, aka inet. And responses return the same route. Now one box in the line has that public IP address, and address within your LAN. Your machine probably calls it a gateway or router. And that router translates (NAT) the private source address of your server into its public address.
But now suppose you call from outside. The call goes to the router. It thinks that it is the destination, does no NAT, and then refuses the connection since it is no FTP server. If you do have control of that router, then there is "port forwarding" (aka "demilitarized zone") that may be possible. To tell the router to pass FTP from outside forward to you. Standard "you will open your firewall for attacks to FTP" warnings do apply.
Option B: The ISP firewall drops all incoming connections for all clients. Nothing that you can do. That is why there exists public filesharing services.