Making webpy framework accessible from outside the local network Post: 302879824

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Making webpy framework accessible from outside the local network Post 302879824 by frad on Sunday 15th of December 2013 09:05:24 PM

12-15-2013

Registered User

Quote:

Quite correct. The IP you see when you query your own IP over the internet is the "outside" interface of your router/modem (sometimes these are two different boxes, sometimes this is bound into one). It is this address by which your web server will be known outside. Notice, though, that the IP address will likely change with every dial-up you do. Therefore, if you configure an IP address into these rules you will have to change that whenever the connection is (re-)established. You should prepare a script for that therefore, maybe you can trigger its execution even, making the thing as "automatic" as it can get.

By the way, before you try to operate your framework: have even tried to contact the "naked" web server from outside? Has it worked? If not, what was the error code?

It is getting more clear but lets make sure that we are not getting confused with the nicknames of the ips.

IP1= the result we get from the "whatsmyip" website (the IP assigned to the connection by the ISP)
IP2a= eth0 result -changes- and IP2b wlan result from "ifconfig"

Without configuring the ip tables, just by opening the port of choice (8081) trying to connect to the framework from outside results in connection time out. The same when IP1 is forwarded to IP2a (if the command I am using is correct)

When IP2a is forwarded to IP1 the framework is only available on the computer that launched it, not even on the other computers on the network. The error message is "page inaccessible" when attempting to connect from other computers on the local network and "connection time out" when attempting to connect from outside.

Please clarify "naked webserver"

frad

View Public Profile for frad

Find all posts by frad

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...

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. ...

LEARN ABOUT CENTOS

pppoe-sniff

PPPOE-SNIFF(8)						      System Manager's Manual						    PPPOE-SNIFF(8)

NAME

       pppoe-sniff - examine network for non-standard PPPoE frames

SYNOPSIS

       pppoe-sniff [options]

DESCRIPTION

       pppoe-sniff listens for likely-looking PPPoE PADR and session frames and deduces extra options required for pppoe(8) to work.

       Some  DSL providers seem to use non-standard frame types for PPPoE frames, and/or require a certain value in the Service-Name field.  It is
       often easier to sniff those values from a machine which can successfully connect rather than try to pry them out of the DSL provider.

       To use pppoe-sniff, you need two computers, a DSL modem and an Ethernet hub (not an Ethernet switch.)

       If the DSL modem normally connects directly to your computer's Ethernet card, connect it to the "uplink" port on the  Ethernet  hub.   Plug
       two  computers into normal ports on the hub.  On one computer, run whatever software the DSL provider gave you on whatever operating system
       the DSL provider supports.  On the other computer, run Linux and log in as root.

       On the Linux machine, put the Ethernet interface into promiscuous mode and start pppoe-sniff.  If the ethernet interface is eth0, for exam-
       ple, type these commands:

	    ifconfig eth0 promisc
	    pppoe-sniff -I eth0

       On  the	other  machine, start your DSL connection as usual.  After a short time, pppoe-sniff should print recommendations for the value of
       PPPOE_EXTRA.  Set this value in /etc/ppp/pppoe.conf.  If pppoe-sniff indicates that something special is required in PPPOE_EXTRA, please e-
       mail this to pppoe@roaringpenguin.com along with the name of your ISP and the manufacturer and model number of your DSL modem.  This infor-
       mation will be collated and provided on the PPPoE web page for users who do not have two computers.

       After pppoe-sniff finishes (or you stop it if it seems hung), remember to turn off promiscuous mode:

	    ifconfig eth0 -promisc

OPTIONS

       -I interface
	      The -I option specifies the Ethernet interface to use.  Under Linux, it is typically eth0 or eth1.  The interface should be "up" and
	      in promiscuous mode before you start pppoe-sniff.

       -V     The -V option causes pppoe-sniff to print its version number and exit.

BUGS

       pppoe-sniff only works on Linux.

AUTHORS

       pppoe-sniff was written by David F. Skoll <dfs@roaringpenguin.com>.

       The pppoe home page is http://www.roaringpenguin.com/pppoe/.

SEE ALSO

       pppoe-start(8), pppoe-stop(8), pppoe-connect(8), pppd(8), pppoe.conf(5), pppoe(8), pppoe-setup(8), pppoe-status(8), pppoe-server(8), pppoe-
       relay(8)

4th Berkeley Distribution					    3 July 2000 						    PPPOE-SNIFF(8)