New
#11
Well that's a beauty, Bree. I had that software and dragged it out and ran it - minus any browsers - and it found the camera alright and enabled a log in and configuration.
So I configured it for my wifi point, the broadband router.
And then checked with a browser. And it appeared!
So why, what happened, I don't know.
But I think I have an idea. It was originally configure with a non standard port for http. port 90.
What I did do this time was reconfigure that to port 80.
Maybe that is what it was all about. Sounds like it, doesn't it?
The browser wants http. Ping and wireshark don't.
So it was 'all my fault' inasmuch as I had set that port.
The answer to my query if all of that is correct is that the device has a non-standard http port.
I completely overlooked the port. Forgot there's two parts to an IP address in reality, when we get to routing traffic for instance, through a NAT.
How the Foscam software deals with it I don't know and would very much like to know.
For that's the 'centre' of my query, really, isn't it.
So thanks for that.
Now I'll go see what the router says about devices attached to it (via wifi) with an IP from another subnet.
Just looked. It doesn't seem to see it. So maybe there's no wifi connection at all. Only the port thing enable the browser ethernet connection.
I will continue exploring.....
:)
Quote