Just going to toss this out. I have several BI5 servers scattered around different construction sites. It's occasionally hard, and in one case impossible to get DDNS or Static IP services from some rural ISPs. I'm also beta testing Starlink, which at this time has no Static or DDNS capability. Starlink does let me put high speed internet (currently 100 down 40 up average) in the middle of nowhere powered by a generator. Exactly the type of location that's prime for needing security cameras.
When I skimmed some the the new Remote Access features in BI5, I made a wrong assumption, and then proceeded to get very excited about it. My assumption, My bad.
I'm sure most people on this forum have used various remote access software services. LogMeIn, RemotePC, SharemyPC, etc. There are a ton of similar SAS providers in remote work, and remote support fields. Install a small client on the remote machine - go through a log-in/verification process on the cloud portal - gain full access to the remote machine (without static, IP, special routing, etc.). Anyway, the wrong assumption I made was that BI had a way to provide remote access WITHOUT creating static IPs, static routes, modifying port forwarding on routers, etc. You know, like those other software services.
Yes. It absolutely represents a reduction in security. A user who wanted such a service would have to accept that.
Yes, it would require BI to essentially host a routing/credential service in the cloud.
Yes, it's a radical departure from the local-install model that has allowed them to develop a beautiful piece of software.
On the other hand,
Many of you are paying $8-$12 a month for a static, and it's possible that a configuration-free RemoteBI SAS service for $5 a month would be appealing.
Camera access is one of the few, but possibly the most common reason for a Pro-Sumer to pursue a static IP.
It's an excellent first step into the SAS world for an add-on service for a well respected piece of software.
I assume Starlink will begin offering Static and DDNS service capability, but that's another assumption. Look how wrong I was on the last assumption
So, however unlikely, this is on my wish list.
When I skimmed some the the new Remote Access features in BI5, I made a wrong assumption, and then proceeded to get very excited about it. My assumption, My bad.
I'm sure most people on this forum have used various remote access software services. LogMeIn, RemotePC, SharemyPC, etc. There are a ton of similar SAS providers in remote work, and remote support fields. Install a small client on the remote machine - go through a log-in/verification process on the cloud portal - gain full access to the remote machine (without static, IP, special routing, etc.). Anyway, the wrong assumption I made was that BI had a way to provide remote access WITHOUT creating static IPs, static routes, modifying port forwarding on routers, etc. You know, like those other software services.
Yes. It absolutely represents a reduction in security. A user who wanted such a service would have to accept that.
Yes, it would require BI to essentially host a routing/credential service in the cloud.
Yes, it's a radical departure from the local-install model that has allowed them to develop a beautiful piece of software.
On the other hand,
Many of you are paying $8-$12 a month for a static, and it's possible that a configuration-free RemoteBI SAS service for $5 a month would be appealing.
Camera access is one of the few, but possibly the most common reason for a Pro-Sumer to pursue a static IP.
It's an excellent first step into the SAS world for an add-on service for a well respected piece of software.
I assume Starlink will begin offering Static and DDNS service capability, but that's another assumption. Look how wrong I was on the last assumption
So, however unlikely, this is on my wish list.
