FlashFXP Forums - Bind to IP-address dynamically also (for those having dyn-ip+router)

FlashFXP Forums (https://www.flashfxp.com/forum/)

- Suggestions (https://www.flashfxp.com/forum/flashfxp/release-archive/flashfxp-v2-1-a/suggestions/)

- - Bind to IP-address dynamically also (for those having dyn-ip+router) (https://www.flashfxp.com/forum/flashfxp/release-archive/flashfxp-v2-1-a/suggestions/2815-bind-ip-address-dynamically-also.html)

Bind to IP-address dynamically also (for those having dyn-ip+router)

It would be great if you could add bind to dynamic external address as well. If you have dynamic ip-address that change every other day it is annoying to go into the settings and change that all the time.
A way to implement it would be to read from this page (or your own webservice making the same thing) when you start FlashFXP:
http://checkip.dyndns.org

Best regards
Niklas

this is already supported in flashfxp. just sign up for one of the dynamic dns services..there are tons; then just put your address in the bind to field. ie, machine.dyndns.org

But this isn't a simple way.

Why don't you integrate a function which reads the current ip from a http site ?
http://repeater.smartftp.com
for example

Or another possibility would be to have a dns server who repeats the IP from the client.
This means
http://repeater.flashfxp.com
will point to your pc on port 80
I hope you understand this concept, but I don't know if it works and I don't know such a dns server. :-\

P.S: Sorry I hadn't seen this thread, I only posted my idea :-)

why this isn't simple?
just sign up for such service and get client that update your ip.
and good thing, you can use it anywhere on the internet, not just within flashfxp.

obtaining the ip from a http server is an option we will consider for future versions.

Quick hack for dyn-ip + router

One quick way to figure out the WAN IP without having to setup and maintain an echoing site (i.e., repeater.flashxp.com) would be to use the local machine's traceroute.

The user could specify the location of the traceroute executable and a nearby host (i.e., www.myisp.com). Or even better the user could specify the whole command. You could then parse the output line by line stopping at the first non-local ip (i.e., something other than 192.168.* or 10.*).

If you really wanted to get fancy you could provide a way for the client to learn how to parse the system's traceroute output. i.e., the user would specify the traceroute executable and a nearby host, flashfxp would capture the output, separate it into space delimited cells, the user selects the field that has his/her IP address and from then on flashfxp would use that field on the first PORT command of any active ftp session. The user would only have to do this once. With a few defaults the whole thing could be done with 1 click.

the way FlashFXP detects inet ip is perfectly fine.

i know for a fact that traceroute is not a reliable method to detect internet ip.
for one, some dsl modems, when in router mode do not support traceroute from the inside.
2nd, some isp use nice tricks to protect their servers by making them reply back with ips from nonroutable range, making them impossible to access unless you are on the same subnet. check out my tracerote.

Code:

Tracing route to dslreports.com [209.123.109.175]

over a maximum of 30 hops:

  1    23 ms    23 ms    27 ms  172.31.255.251

  2    22 ms    23 ms    22 ms  192.168.13.49

  3    22 ms    21 ms    20 ms  gigabitethernet5-0-146.ipcolo2.NewYork1.Level3.net [166.90.137.213]

  4    20 ms    23 ms    23 ms  gigabitethernet2-1.core1.NewYork1.Level3.net [64.159.17.69]

  5    22 ms    24 ms    21 ms  unknown.wcg.net [209.244.160.138]

  6    25 ms    23 ms    30 ms  nycmny2wcx3-pos9-0.wcg.net [64.200.87.226]

  7    23 ms    22 ms    26 ms  nycmnyhlce1-oc48.wcg.net [64.200.87.110]

  8    20 ms    20 ms    26 ms  nycmny2lce1-netaccess-atm.wcg.net [64.200.86.150]

  9    24 ms    25 ms    25 ms  1187.at-0-1-0.gbr1.oct.nac.net [209.123.11.150]

 10    22 ms    22 ms    23 ms  0095.gi-1-1.msfc1.oct.nac.net [64.21.102.2]

 11    24 ms    22 ms    24 ms  www.dslreports.com [209.123.109.175]

Trace complete.

as you can see 1st hop is a nonroutable ip, which is actually my machine w/o any firewalls or routers. 2nd hop is my dsl provider's redback, and 3rd is internet.
so as you can see it's impossible to determine my ip from outgoing traceroute. incoming traceroute looks similar only 1st hop(last hop for incoming) will have my real inet ip.

Heh, that checkip.dyndns.org doesn't work too well, if using local proxy ;)

Current IP Address: 192.168.1.11
Hostname: Unknown
Return to referring page

Anyways.. should be rather easy to do with Internet API (InternetOpen() etc) I suggest using regexps for parsing response

we'll be adding support for http lookups in the next release