Hi folks - massively dumb question I'm afraid!
I can access zm on my local network (I go to http://10.50.60.77 from my browser - no problem). Latest liveCD. Works GREAT. Not a massive problem but I would like to be able to reach it externally from outside home (through my firewall).
Can anyone tell me in simple language what mandrake server changes I need to make to turn it into an internet-facing webserver - for example "http://8ace.com". My firewall is currently forwarding all port80 traffic to my zoneminder server at http://10.50.60.77 but it doesn't seem to work from the internet so I am guessing I have missed something obvious....
on the zm box, do I need to set up virtual hosts, etc? Set DNS and whatever? What file(s) do I edit on my zm server to make this work?
I am a little lost here so any suggestions would be appreciated.
I am not planning on any mail, FTP or other services running on the mandrake box.
Any tips? thanks in advance!
problem setting up (internet-accessible) zmserver?
This is the correct approach. So double check all your settings. You should be able to reach it at http://your.public.ip/zm/My firewall is currently forwarding all port80 traffic to my zoneminder server at http://10.50.60.77 but it doesn't seem to work from the internet so I am guessing I have missed something
You cannot usually test from inside your lan, you must test from the internet side.
Noon the zm box, do I need to set up virtual hosts, etc?
A dynamic hostname is helpfull to find your server if your public ip changes (ie most dsl and cable services) Check out dyndns.org. And ddclient is included on the ZMliveCD to keep your dyndns in syncSet DNS and whatever?
No changes should be needed on the server, as long as it is working from the LAN. You need to look elsewhere, your firewall settings for example.What file(s) do I edit on my zm server to make this work?
Best regards,
Ross
Last edited by rdmelin on Wed Jun 28, 2006 7:44 pm, edited 1 time in total.
i hope i got you right 
if port 80 is forwarded to your zm server you can access it from the internet with your external IP, not 10.50.60.77. and - depending on your firewall - you maybe cannot connect from your internal network to your external IP and reach the server. so you should try it from a different internet connection.
if you want some cool domain pointing to your server you can use http://www.dyndns.org or something similar.
if port 80 is forwarded to your zm server you can access it from the internet with your external IP, not 10.50.60.77. and - depending on your firewall - you maybe cannot connect from your internal network to your external IP and reach the server. so you should try it from a different internet connection.
if you want some cool domain pointing to your server you can use http://www.dyndns.org or something similar.
Code: Select all
$> man woman
$> Segmentation fault (core dumped)
One other possibility: The webserver (usually apache or apache2) might have been configured to only allow local traffic and is refusing access to internet queries.)
Debian and ubuntu default to allowing world access, but I guess some distro or other might block it by default.
(Quick to check: Simply try to visit a known page from outside).
I think the faulty port-forwarding router or another firewall issue is probably the problem here though. Original poster doesn't mention if they can see anything on that webserver from outside, or even if the router is on the same segment as the server and there's a more fundamental networking issue here.
Debian and ubuntu default to allowing world access, but I guess some distro or other might block it by default.
(Quick to check: Simply try to visit a known page from outside).
I think the faulty port-forwarding router or another firewall issue is probably the problem here though. Original poster doesn't mention if they can see anything on that webserver from outside, or even if the router is on the same segment as the server and there's a more fundamental networking issue here.
The versions of mandrake I've used the past (the last two major releases) have firewall rules that prevent outside access. You'll need to either relax the firewall rules, or as I usually did, just turn the damn thing off. Since you're behind a nat router, only port forward the services you want. And then for additional protection use /etc/hosts.allow and /etc/hosts.deny to narrow down the avenues of attack to your system.
you can shutdown the firewall system on your mandrake box by using the mandrake admin tool. Sorry don't remember the exact name of it, but it's in the menu system.
you can shutdown the firewall system on your mandrake box by using the mandrake admin tool. Sorry don't remember the exact name of it, but it's in the menu system.
the reason i turned the firewall (shorewall i think it was on that distro) was that even when I set exceptions to the rules to allow some service or other to come in, it still didnt' work for me. Don't know if it was a mandrake problem, firewall problem or simple user error, but I could never get it work satisfactorily.
Like most people, I didn't have the time or patience to track the problem down and simply give it a few jabs before giving up.
Like most people, I didn't have the time or patience to track the problem down and simply give it a few jabs before giving up.
-
jameswilson
- Posts: 5111
- Joined: Wed Jun 08, 2005 8:07 pm
- Location: Midlands UK
I must say if your having problems and 'dont have the time' to fix them, i dont think your gonna get very far with doing anything but basic stuff. If your having ip forwarding issues there are lots of things it could be, and last on the list is zm if it works on the lan
James Wilson
Disclaimer: The above is pure theory and may work on a good day with the wind behind it. etc etc.
http://www.securitywarehouse.co.uk
Disclaimer: The above is pure theory and may work on a good day with the wind behind it. etc etc.
http://www.securitywarehouse.co.uk