This thread is a crumbling mess, although "I want wifi and ethernet to play nice" isn't the rarest of requests I would advise you try and create a new thread if you have further issues.JohnEdens wrote: ↑Wed Apr 25, 2018 10:29 pmI think the above referenced link is similar to what I want, however I won't be using DHCP and am not sure from the instructions at the link how this would work with static IP addresses. I'm also not sure whether or not I would need three different static IPs in this setup, one for the camera, one for eth0 and one for wlan0.
To answer your questions, and looking at the post your were referring to:
- Drop the dhcpcd part, you'll be working with static addresses
- Make the Pi's wifi interface a client on the wireless network. I suppose this is DHCP, see if you can get a fixed lease as you'll need to know this address in order to get to the cameras (via NAT, same as having a public website installed at home.)
- For the ethernet part, take 2 addresses on any network you want, like 192.168.0.1 and 192.168.0.2, use one for the Pi, one for the IP camera.
- In addition you have to NAT the wifi address, say port 8080/tcp to the IP cam's address, same port. That's an additional iptables rule you need to set in the file mentioned in the post. I think this is what you want.
So I would advise to install a test machine with the simple setup above, and see if you can reliably get a stream out of the test cam over a few days.
- If you don't, then the issue is with the wifi link, either in the Pi or in the AP (or both, or somewhere else, wireless is funny like that).
- Replace the Pi with a dedicated wireless device, like a pocket travel AP (which works as "ethernet to wireless bridge" for a single device) or whatever wireless device your IT recommends. Could play nice with MAC VLAN
- Replace wifi and Pi with a pair of powerline adapters (one next to the IP cam, one in the monitoring room -- or next the main ethernet switch in the museum building). Will play nice with MAC VLAN
- Deploy something like POF (plastic optical fiber) instead of ethernet: fast, flexible, small diameter, easy to install, carries no electricity. So it could be easy to install/reinstall. 50m cable runs should be ok. Requires a pair of powered copper-to-fiber adapters at each end, should be cheap but sourcing is a bit of a challenge. Will play nice with MAC VLAN.
- If you do, then all hail the mighty Pi. You'll still have that pesky VLAN and seamless integration with other cams to contend with.
Your IT will advise, but let me peddle a solution to it here. You can implement that with Pis and/or big honking servers. That would give you your VLAN and seamless integration, plus a welcome layer of security over the wifi link if you cipher the VPN tunnel(s).