From: Klaus E. D. <mo...@ke...> - 2006-04-04 23:50:50
|
Hi again Fra: Erik Jakobsen=20 Til: mot...@li...=20 Emne: Re: [Motion-user] Remote control ? I have mixed your replies together, hope you can follow anyway. ;) >I have a firewall running on my server, where motion resides. Its a >Linux server -Clarkconnect-, and the incoming port 8080 has been = opened. That should be allright unless you're running a proxy on the machine = witch often use port 8080 but the you write >Its a while since I played with motion. Thought it was port 8080, but = it >is 8082. In that case it is port 8082 you need to open but that part i think you = have correct also :) >############################################################ ># HTTP Based Control >############################################################ ># TCP/IP port for the http server to listen on (default: 0 =3D = disabled) >control_port 8082 ># Restrict control connections to localhost only (default: on) >control_localhost off ># Output for http server, select off to choose raw text plain (default: = on) >control_html_output on ># Authentication for the http based control. Syntax username:password ># Default: not defined (Disabled) >; control_authentication username:password >Do you see anything worng there ?. No it looks okay to me, the danger i see here is if one of the = "webcam_port" is set to that port too - not sure what would happen then. I have just tried my own and also ran in to some trouble, the difference = in my setup is that i use another port and have enablet = "control_authentication" My first try was from the machine writing from now, a Windows 2000 - i = get the login box enter username and password but when submitting i got = a "Page could not be displayed" ? - checking username and password in = motion.conf and that was correct. I then tried on my Win XP and there it works as expected, back to this = machine but it don't work here - real strange i must admit. There was no problem on the motion machine itself (fedora 5) using = 127.0.0.1. The Motion version i use myself is a snap from december 2005 as the = latest version have the bad idea that it should drop the cams adding a = gray image that stays there until motion restart so that is not to = compare with your SVN version of motion and i'm afraid that i can not = help much more here. The only thing i can think of if it should not be something broken in = motion is that you have set your browsers up so it uses an outside proxy = without setting that the proxy is not to be used on your local network = but again with all the machines you have tried i find i hard to think = that it could be that. >What port could you suggest Klaus to be better than the 8080 ?. Allmost everything > 1024 and not listet in "/etc/services" would be a = good choice - on my own machines i use something odd from 50000-60000 = that i can remember as they seem not to probed so often as the lower = ports but if you only set it up to access from the inside it don't = really matters at all. So the things i would check now is: 1) no "webcam_port" is set to the = same as "control_port", 2) the browsers not set up to use outside proxy. Good luck with the hunt for the reason /klaus |