| LinHES Forums http://forum.linhes.org/ |
|
| Configuring MythWeb for outside access http://forum.linhes.org/viewtopic.php?f=11&t=11861 |
Page 1 of 1 |
| Author: | shonmm03 [ Wed Sep 27, 2006 6:28 am ] |
| Post subject: | Configuring MythWeb for outside access |
I'm having trouble getting MythWeb to respond to browser requests from outside my LAN. Access to MythWeb from inside the LAN works fine. I've turned off the firewall features of the router that provides access to the WAN, as well as turning on port forwarding for port 80. I also verified that apache is using port 80. I can ping the url I have set up from outside, but http requests to the address return a server timed out error. Any ideas? |
|
| Author: | khrusher [ Wed Sep 27, 2006 7:19 am ] |
| Post subject: | |
how do you 'ping a url' if you are pinging the external IP address, you are only 'talking' to the WAN side of the router. You can't ping a specific port as ping functions at a lower layer in the IP stack (Network Layer) while http is at the top in the application layer. I wuld double check the port forwarding settings again. Is your apache server listening on port 80? is the IP address and port number entered correctly. Is the URL you are using from the WAN correct? |
|
| Author: | shonmm03 [ Wed Sep 27, 2006 9:23 am ] |
| Post subject: | |
That answers the first question: pings aren't going to the box because they're on a lower level of the stack, and are being handled by the router itself. I wasn't sure if that was a valid test to see if traffic was going to the right place or not. It isn't. I guess I used the wrong terminology earlier - it's probably more correct to say I was pinging the domain (i.e. mysite.dyndns.org), not the url. The domain was correctly resolving to the IP address, so it seems the dyndns service is working correctly. Once you pointed out that pings weren't doing what I thought, I did some more looking around, and I'm now pretty sure that my ISP is blocking port 80. Hopefully changing apache to use another port and reconfiguring dyndns to point to the new port will fix everything. Thanks for the help. |
|
| Author: | khrusher [ Wed Sep 27, 2006 10:13 am ] |
| Post subject: | |
you dont need to need to do anything with the dyndns settings. Dyndns only maps the host alias to your WAN ip address. Dyndns doens't care about ports. if port 80 is blocked all you need to do is move apache to an alternate port, 8080 is common. on the firewall, forward 8080 to the mythbox Then use 8080 in all urls, internal and external external url will look like http://<dyndnsdomain>:8080/mythweb depending on the router the same url can be used while on the LAN. I have used 'residential grade' routers that don't allow accessing the WAN ip / port forwarding configs from the LAN (caugh "Belkin") |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|