HS Visu, camera, dyndns

[Warichet]

Hi,

Ive a question about HS Visu, camera, dyndns
I found the following, but it's not quite the same problem, no eibport, but LAN with private address 10.0.x.x, ADSL, rtr and switch.

In the Visu, I give acces to the outside world to cameras.
This works fine: either from within the Visu or direct link to
http://warichet.dyndns.org/: port/HS/imagepath. No problem.

But ... from the inside LAN, I'm unable to see the images over the dyndns link. It's quite normal, but I have to rely on someone else to test the setup.
I guess there is a workaround ?
I remember to have seen camera images from forum members, so maybe there is a trick ?
NB: The images are obviously available over the internal IP
http://10.0.1.2xxx/: port/HS/imagepath.

Thank you for any hint.

[MatthiasS]

What are you settings under "User - Kamera-Direktzugriiff"?

[MarkusS]

Raymond,

this behaviour is quite common because:

• Your router has a firewall feature-set? There is a simple rule which many firewalls obey by design: Never send traffic back to the interface where it originated.
• You try to "loop" internal traffic (source and destination) through your router/firewall by (trying) to access a internal address via external address. The problem is: You need some kind of NAT to get this working but NAT does only work for packets that enter the router through the outside interface.

[Warichet]

@ Matthias
The setting under "User - Kamera-Direktzugriiff";
the box is checked; although I don't fully understand the implications of this setting.

@Markus

The problem is: You need some kind of NAT to get this working but NAT does only work for packets that enter the router through the outside interface.

Indeed.
I was hoping for some trick at that level. I've seen things about "internal NAT to NAT" translation, but, pfiou...., too strong for me.
So you guys, you all have the same "problem" ? (although it isn't really a problem)

[MatthiasS]

I don't fully understand the implications of this setting.

This means, that with direct access you will use direct access to your camera. Your browser tries to contact the camera with the url you have entered.

Without direct access, your homeserver loads the picture of the cam and you will access the camera image from hs, not from the direct url.

[Warichet]

with direct access you will use direct access to your camera. Your browser tries to contact the camera with the url you have entered.

OK, thank you.
In this particular instance, I use the dyndns syntax, so it doesn't help.
I'm not sure there is a solution to this problem.

Anyway, I could:

• live without seeing the images from the Visu
• duplicate the pages with the camera and change the URL to the internal address, for my own use
• not offer the camera to the outside world

but I'm not happy with any of the above.

How do you do it ?
(Matthias is well known for having a solution to almost everything )

[HartmutB]

I'm not sure there is a solution to this problem.

Have you at least tried my proposed hint (via PN from yesterday, 11:34am) ?


In short: You wrote, internal access is possible. But only via the (non-NATted) IP address, not via the (external NATted) Dyndns IP address as this would route your request to the outside and then back (failing).

So, a solution ist not a question of access, but name resolution. If you can setup a split DNS server for internal, simply add an entry for "warichet.dyndns.org" together with your internal address there.
If that's not possible, add an appropriate hosts-entry to your local visu PCs. A host entry will be used before calling a DNS request and return your local address to the browser (another hint: After changing the hosts file, do a "ipconfig /flushdns" and restart the browser).


Regards,
Hartmut

[Warichet]

Have you at least tried my proposed hint (via PN from yesterday, 11:34am) ?

Yes, Sir!
I always do what you tell me to do
It didn't work, but at that time I was trying to redirect traffic via NAT & port 8080. So I skipped it

add an appropriate hosts-entry to your local visu PCs.

That's what I've tried before, and didn't work, because I messed around with NAT.
Now I've cleaned the mess and put all cameras on port XXXX to segregate icoming traffic intented for the HS (on port 80) form camera traffic (on port XXXX).

Now it works. So simple, and so great
Thank you very much, again.
I noticed it works only on the Visu PC which has a fixed IP.
I tried on a DHCP client, by putting the current IP in the hosts file, no go, but no problem.
I owe you a beer next time you pass along in Midi-Pyrénées