Hi,mushu999 wrote: ↑Wed Nov 07, 2018 11:36 pmI've confused myself into a corner. Trying to hook up a security cam in the garage to a Pi 3B+ running MotionEye application (not O/S) on Stretch. The cam has a built-in wireless access point (AP) and an Ethernet connection for wired access. Simplistically, that tells me that it wants to be "the server" for wireless connections or "the client" for wired ones. I know the cam works because I hooked it directly into my home router via wired when I opened it and it got assigned a 192.168.x.x IP via DHCP and I was able to view the image through a browser, but now it is mounted on the side of the house and I have this conundrum. My Pi is currently in the garage as well and connected to the home network via wireless and has a valid 192.168.x.x IP address. So the $10M question: how do I get the Pi to "see" the cam via the Ethernet connection?
My first thought was to simply use a CAT 5 and hook them together. But...nothing. So then I grabbed a cheap little switch and connected the Ethernet ports together that way. Nothing. Now I'm thinking I need an ethernet-to-ethernet Bridge. If I ran 80 feet of CAT 5 from the living room into the garage directly to the cam it would work just fine but I really really don't want to do that. There *must* be a way to make this work. Thoughts anyone? Getting desperate.
Good idea.PhatFil wrote: ↑Thu Nov 08, 2018 3:32 amwithout a make/model number of your camera its tricky to advise, but in my limited experience with a few home wifi gadgets, when a device starts up offering an AP it can often be a setup portal for configuring your networks wifi credentials and sometimes even allow the setting of a static ip. A common address used for a config-AP is 192.168.4.1.
So i would start by using a wifi enabled puter to connect to the cameras AP and point a browser @ 192.168.4.1 or the gateway addy you retrieve from an ipconfig/ifconfig command at the command prompt.
That's because the router in the living room runs a DHCP server.mushu999 wrote: ↑Wed Nov 07, 2018 11:36 pmMy first thought was to simply use a CAT 5 and hook them together. But...nothing. So then I grabbed a cheap little switch and connected the Ethernet ports together that way. Nothing. Now I'm thinking I need an ethernet-to-ethernet Bridge. If I ran 80 feet of CAT 5 from the living room into the garage directly to the cam it would work just fine.
Fwiw i really dont like all these 'cheap' 'smart' home products that rely on dodgy phone apps that require every privilege your phone can offer Needing remote servers and services that could cease operation at the drop of a hat.epoch1970 wrote: ↑Thu Nov 08, 2018 1:45 pmWell, I ran through the doc (one-page manuals, I like those) and apparently the device also works as a wifi client if you want. It's described in the Q&A block: a) boot the cam with ethernet, b) download the mobile app, c) in mobile app set cam to wifi network of choice, d) reboot cam & disconnect ethernet.
Since the cam wants to notify the mobile app, or send email and stuff, it wants Internet access. A single network would make that easier.
- If the cam can get ok wifi from the router, you're done.
- If not, you'd need to wire the cam to a switch, and that switch to the router. You can't bridge 2 network segments over wifi (ok you can with a tunnel, but that will twist your brains), so a switch is in, and the Pi is out.
Note that wiring ethernet outside a building should call for specific precautions: UV/weather resistant cable and earthing. Without lightning protection your whole network could go poof in a single strike. Or worse, put the house on fire... If in doubt, do take advice.
If you were a business I would profess to absolutely put the cam in its own network; It surely has vulnerabilities so sandboxing it in its own network, with a router standing guard is a must. But then you'd need to route the notifications and Internet access; with the help of a one-page manual.