Here’s a summary of my situation - I’m trying to setup a Closed network on location somewhere (for filming). Many modern 360 video cameras (such as the Z-cam S1/S1 Pro, Liveplanet and more to come) require two things
- Power
- Gigabit ethernet
In an effort to control these kinds of cameras on location - many of us (myself included) have been using small wireless routers. However in some cases a more hardcore solution was needed - namely the Pepwave AC-One.
The problem is that there is NO WAY that I can see (and I asked 3G Store and Frontier US for help - they came up empty also) to enable the LAN port to issue IP addresses from the same pool as the DHCP on the Wifi Access Point.
In other words - here’s what I’m trying to connect (on a remote location)
Multiple Wi-Fi devices (e.g. Laptop and iPad Pro) and 2 wired devices (specifically the Teradek Sphere and the Z-cam S1).
On any normal router - when I go into router mode - there is a downstream LAN port and an upstream LAN port.
So long as I ignore the upstream LAN port the downstream LAN port(s) are on the same subnet as the devices connected to Wifi (for the sake of argument 192.168..) - so they can all see each other.
However the Pepwave AC One cannot be configured that way.
So in my configuration (which on location in a desert shoot looks a bit like this)
My network is as follows:
iPad connects to router via WiFi
Teradek Sphere connects to router via Ethernet cable
ZCam S1 camera connects to router via Ethernet cable
Windows laptop connects via WiFi
All these devices need to see each other.
And my only solution (using the Pepwave One) is to use it in Bridge mode…but the ONLY reason this worked is because it so happens that the S1 camera can be set to act as a DHCP server rather than client.
So the Camera itself is issuing IP addresses to all other devices (including laptop) from the same pool.
This works - but is inconvenient - because it means that in other environments I have to keep changing camera settings (e.g. in the Office) - because the camera needs to be a DHCP client (as with most devices) when connected to a regular network.
The solution to this seems easy - (and I suspect can be done in software as a flag) - when the user selects ROUTER mode for the Pepwave ONE - one or more ports should be enabled as a downstream port.
Perhaps there is some way to “hack” the router settings into doing this - but if so - I don’t know what it is.
Curious if other people think this is useful or if I’m an edge case.