OK, things start to get clearer. I understand that basically your framework is a sort of web server module. I presume it is configured correctly in its own right, because otherwise you would not be able to use it from your local network.

Next question: what are the IP-networks you use? Look at your IP-addresses and subnet masks. If the addresses are one of these:

Code:

10.x.x.x
172.[16-31].x.x
192.168.[0-255].x

you use indeed NAT and we have to sort that out first (in fact most consumer Wifi-routers do that per default). As you say you use dynamic IP addresses chances are you do not have a range of official IP addresses (who still, these days?) but merely a so-called "private address space"-network, as defined in RFC 1597. In this case, to make your server known, you will have to use dynamic DNS to keep at least the name the service is reachable at constant.

A final remark:

If this really works you'd better never succeed in connecting the system to the internet. The network address "0.0.0.0" is the "joker for all" and if the whole world comes down on your system requesting its services chances are it won't keep up with the load.

I still would appreciate if you could give a little more information aforehand instead of letting me guess. You now said several times that your IP addresses are dynamic but were silent about your network layout (which networks, subnet masks, connected how?) save for what i explicitly asked. As your problem is most probably a firewall problem it might help a wee bit to know these things.

I hope this helps.

bakunin