meteohub.de

Hi all,
I have a problem :

I've this configuration:

Router 192.168.0.1
Linksys 192.168.0.4
IP Mobotix 192.168.0.6
This PC 192.168.0.8

All dhcp are activate (dhcp = on).

If I swich the IP cam only for a fixed ip
IP 192.168.0.6
Sub 255.255.225.0
DNS 192.168.0.1

After a random time (sometimes after 1 hour, or 3 hours or more or less) the IP cam does not works and I need ro restart (power off/on) the IP cam.

If I chenge the IP Cam to dhcp the problem it is solved.

The same problem has a my frend using an Intellinet IP cam.

Does anyone know why this ?
Thanks, Alberto.

If you are using a static (fixed) IP address for anything on your router, you should assign it an address outside of the DHCP range. There should be a setting somewhere that defines the DHCP range (e.g. 192.168.0.5 through 192.168.0.50 or such)... if that's your range, give the camera the IP address 192.168.0.51 and it will never have a conflict.

Otherwise because you are assigning a static IP at the low end of the DHCP range, the router does not know that *.0.6 has already been assigned, and it gives it out to the next client asking for a DHCP lease. When you cycle the power on the camera, it pings the router as the most recent system on *.0.6, so it works again for a while, but eventually the cycle repeats itself.

Hallo' Sevenless
and thank you for your prompt reply !

I try to setup my hardware using your instructions

Now are:

Router dhcp range *.0.2 *.0.51

Router (dhcp on) *.0.1
Meteohub fixed ip *.0.6
IP Cam Fixed *.0.60
Davis IP Fixed *.0.52
This PC: (dhcp on) *.0.8
2nd PC: (dhcp on) *.0.9

I hope it is correct. Now all hardware does
works as well


I reply you tomorrow for the details of this test.

Thank You
Alberto.

Meteohub fixed ip *.0.6

This is still a possible problem. If you have multiple DHCP clients using your router, one of them might get assigned *.0.6 and then there would be a conflict with the Meteohub, which is using that address (remember, the router doesn't know that the Meteohub is doing its own static IP address assignment.)

You should either change the Meteohub to *.0.53 or change the DHCP range to use *.0.7 - *.0.51 to avoid this problem. Make sure you have no static clients within the DHCP range!

Hi, bad news..
Ip Cam crash in the night.

I' don't undertand where is the problem.
If I use all harware with dhcp activate (2 pc, meteohub, ipcam) ip cam does work as well without crash.

If i change only the ip cam for a fixed ip address, meteohub crash the ip cam after 2/3 hours

If I disconnect meteohub the ip cam don't crash.

I can use all dhcp to solve this problem, but i like to know why this crash...

Alberto.

Who makes the webcam and what model is it?

Hi,
the Ip cam it is an Intellinet:
http://www.intellinet-network.com/en-US ... ork-camera

The cam does one ftp of jpg image every 5 minuts and also I can view the streaming video with dyndns.org
I need to use a fixed ip in the cam becouse I have a NAT in the Netgear router to view the real time image.
I have a dynamic ip WAN only.

May be it is a problem of port?
Here is the configuration of Ip Cam:


Thank You.
Alberto.

Hi all,
I found the solution myself.

Only changed the web server port from 80 to 90 in the Meteohub the and IP cam does works as well.

May be it is not possible to use the same web server port 80 for all hardware.

Alberto.

You should be able to use port 80 for access on as many systems as you want, as long as you specify forwarding for each of them on your router using unique external ports. For example:

External port 80 -> internal IP cam port 80
External port 8000 -> internal Meteohub port 80
External port 8080 -> internal web server port 80 (or whatever else is running)

If accessing externally, you can only use each port for access to one internal system, but thanks to port forwarding, internally you can use the same port over and over again on different systems.

Inside your local network, you can have as many systems using the same port as you want, because each has its own local IP address for access and thus there is no conflict between them (they appear as 192.168.0.5:80, and 192.168.0.10:80)

Perhaps you have uPnP activated on the router and the IP Cam, which is a technology that is meant to simplify setting up port forwarding, but often causes problems if multiple systems are using it to set themselves up with default values and each assumes it is the only internal system.

Anyway, all of that is moot because it sounds like your change has fixed the problem, regardless of the original cause.

One last word of warning: you should probably not use port 90 for Meteohub access because that port number is reserved by the IANA for DNSIX Security Attribute Token Map and Pointcast transmissions. You are not likely to run into conflicts because of this, but when using non-standard port numbers you should always select a high range such as 8080 (which the IANA has already assigned as an HTTP alternate), or unassigned numbers.

sevenless wrote: One last word of warning: you should probably not use port 90 for Meteohub access because that port number is reserved by the IANA for DNSIX

Hallo' sevenless and thank you for your suggestion.

I' can access from network to Meteohub with address 192.168.0.200:90/ without problem, and Meteohub and Ip cam they works as well. No ip cam crash from 2 days using fixed ip.

If I change the port from 90 to 80 the IP cam crash into an hour.
If I swich off Meteohub ip cam does not crash.

Alberto.