Eth0 is the PI's actual network address that can be accessed by other computers. lo is the localhost loopback which every computer has to basically talk to itself. (see https://en.wikipedia.org/wiki/Localhost). In other words if you were on your PC and pointed its browser at http://127.0.0.1:8000 it would have tried to connect back to *itself* not the Raspberry PI. If you want your PC to connect to the Raspberry PI you need to tell it the PI's actual address as shown by ifconfig (in your case eth0 = 192.16x.xx.xx). Telling web2py to listen to 0.0.0.0 should work but from other computers you've still gotta address the Raspberry by it's eth0 IP address.
As for why you had to use port 80 instead of 8000 - my guess would be that something else was already using port 8000 on the Raspberry PI. Telling it some other unused port number like 8080 or 8001 or whatever would probably have worked too. ~Brian On Thursday, September 12, 2013 4:42:29 PM UTC-5, Zachary Burrows wrote: > > NOTE: I did have to boot up the server on port 80 instead of port 8000. > Any guesses why? > > > I will check ifconfig and let you know what IP it gets assigned. I assumed > that I needed to log on to the same IP address that is displayed in my > browser on the Pi. Is this not the case? I have tried the 0.0.0.0 this way > with no luck. > > -Zach > > > EDIT: Used ifconfig and got something like this back: > > eth0 Link encap Ethernet ... > inet addr: 192.16x.xx.xx > > ... > > lo Link encap: Local Loopback > inet addr: 127.0.0.1 Mask: 255.0.0.0 > ... > > > > What is the difference between these two? Thank you so much. It is working > now. I logged onto the 192.16x.xx.xx instead of the 127.0.0.1 IP. I would > like to understand why I was on the wrong track. There is obviously a gap > in my understanding. > > -Zach > > > On Thursday, September 12, 2013 2:33:11 PM UTC-7, Niphlod wrote: >> >> what ip address gets assigned to the raspberry ? (see the output of >> ifconfig). >> >> No matter what, you can always run web2py using 0.0.0.0, that means >> "accept connections listening on all ip addresses" >> >> On Thursday, September 12, 2013 11:28:39 PM UTC+2, Zachary Burrows wrote: >>> >>> Hello all, >>> >>> I have web2py installed on my Raspberry Pi. I have downloaded the source >>> code from the website as well as trying to follow this instructable: >>> >>> http://www.instructables.com/id/Raspberry-Pi-GPIO-home-automation/ >>> >>> Neither of these install methods include the option to launch a public >>> server with the IP form: >>> 192.168.xxx.xx >>> >>> I am able to create a website with my PC using web2py and this IP form, >>> and am guessing that if this form were available on my RPi it will work. >>> Because when I try the forms BESIDES the above one on my PC I cannot log >>> onto my PC's server from another computer. Only this 192.168.xxx.xx form >>> works. >>> >>> I do have these options on the RPi: >>> Public (0.0.0.0) >>> Public(127.0.1.1) >>> >>> but again, I can't log into either of them from another computer. >>> >>> Any ideas what I'm bumping up against? I am hooked up to Ethernet at my >>> work on both the PC and the RPi. >>> >>> Thanks! >>> -Zach >>> >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
