Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Making webpy framework accessible from outside the local network Post 302879777 by bakunin on Sunday 15th of December 2013 09:38:37 AM
Old 12-15-2013
Quote:
Originally Posted by frad
All computers connected via wifi/ethernet to my modem/router can see the framework by typing http://0.0.0.0:8080/ or variants after I start the server with
Code:
 python code.py

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:

Quote:
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
 

2 More Discussions You Might Find Interesting

1. IP Networking

ssh server is attachable from local network not from another network

hello i have a ubuntu ssh server that i can acess from any of my comnputers but only if they are on the same wireless network as the server. i tested trhis my tehtehring my samsung blackjack to my windows partition and installing openssh to windows it works when windows is on the wireless but no... (1 Reply)
Discussion started by: old noob
1 Replies

2. Infrastructure Monitoring

SF4800 SC not accessible thru network

Hi All, I have my SC setup as attached below but I am having problem accessing the port thru network. sc0 was accessible only after i failed over the configuratios to sc1 (now then sc1 was not pingable :(). Just wondering is there anything wrong with my sc settings? Appreciate your advice. ... (4 Replies)
Discussion started by: honmin
4 Replies
ubuntu-dev-tools(5)						File Formats Manual					       ubuntu-dev-tools(5)

NAME
ubuntu-dev-tools - Configuration for the ubuntu-dev-tools package. DESCRIPTION
The ubuntu-dev-tools package is similar in scope to the devscripts(1) package, providing a collection of scripts which may be of use to Ubuntu and Debian developers or others wishing to build Debian packages. Some of these scripts have options which may be configured on a system-wide and per-user basis. These options are configured in devscripts.conf(5). All variables are described in the script's manpages. Package-wide variables begin with "UBUNTUTOOLS" and are listed below. Every script which reads the configuration files can be forced to ignore them by using the --no-conf command-line option. ENVIRONMENT
All ubuntu-dev-tools configuration variables can be set (and overridden) by setting them in the environment (unlike devscripts). In addition, several scripts use the following environment variables: UBUMAIL Overrides DEBEMAIL and DEBFULLNAME when the target is clearly Ubuntu. Can either contain an e-mail address or Full Name <email@example.org>. DEBEMAIL, DEBFULLNAME As in devscripts(1). PACKAGE-WIDE VARIABLES The currently recognised package-wide variables are: UBUNTUTOOLS_BUILDER This specifies the preferred test-builder, one of pbuilder (default), sbuild, pbuilder-dist. UBUNTUTOOLS_DEBIAN_MIRROR The preferred Debian archive mirror. Should be of the form http://ftp.debian.org/debian (no trailing slash). If not specified, the master will be used. UBUNTUTOOLS_DEBSEC_MIRROR The preferred Debian security archive mirror. Should be of the form http://security.debian.org (no trailing slash). If not speci- fied, the master will be used. UBUNTUTOOLS_UBUNTU_MIRROR The preferred Ubuntu archive mirror. Should be of the form http://archive.ubuntu.com/ubuntu (no trailing slash). If not specified, the master will be used. UBUNTUTOOLS_UBUNTU_PORTS_MIRROR The preferred Ubuntu archive mirror. Should be of the form http://ports.ubuntu.com (no trailing slash). If not specified, the mas- ter will be used. UBUNTUTOOLS_LPINSTANCE The launchpad instance to communicate with. e.g. production (default) or staging. UBUNTUTOOLS_MIRROR_FALLBACK Whether or not to fall-back to the master archive mirror. This is usually the desired behaviour, as mirrors can lag the masters. If on a private network with only a local mirror, you may want to set this to no. One of yes (default) or no. UBUNTUTOOLS_UPDATE_BUILDER Whether or not to update the test-builder before each test build. One of yes or no (default). UBUNTUTOOLS_WORKDIR The directory to use for preparing source packages etc. When unset, defaults to a directory in /tmp/ named after the script. SEE ALSO
devscripts(1), devscripts.conf(5) AUTHORS
This manpage was written by Stefano Rivera <stefanor@ubuntu.com>. ubuntu-dev-tools December 19 2010 ubuntu-dev-tools(5)
All times are GMT -4. The time now is 07:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy