Obi 202: disable auto-provisioning permanently or??
giqcass:
I have all automatic updates off. Firmware and provisioning. I have had no issues.
QBZappy:
It may not be obvious, but keep in mind that the local web units provide configuration settings for 100% of the OBi features, while the portal does not. I don't know if it has been fixed but making backups and restoring OBi configs was broken even though they showed the control button on the portal. It may have been fixed. Someone else who uses this feature can confirm this. One of the biggest criticisms using the portal is that the call history is missing. The call history is useful for troubleshooting. If there is a config missing on the portal that you need to access it may force you to use the local unit web page approach. Also something to note. New features to the firmware are not always implemented immediately on the portal. Personally I use the local unit whenever I can. Who wants to use a crippled portal when the unit provides all the features.The portal is useful for setting up units far away.
I wish there was a way to point directly to the far away OBi unit without using the OBI portal, port forwarding, or using a VPN. I set up the url DDNS method as explained by gigcass, however as expected I hit the router since it is the gateway. The only way to achieve the end goal of configuring a far away OBi is to point to your own computer and become your own ITSP Provisioning server. This can be done with some effort. RonR has a utility for such an approach which helps to simplify it. I find it too much of a hassle to set up for just one unit.
sdb-:
I use ssh. Basically it gives me a quick and easy way to establish a temporary port forward that I can use to reach whatever I want on the remote network. Of course, that requires a fully functional ssh server on the remote network (in the router firmware or some other box on that network).
But I'm a software engineer specialized in network devices...
Navigation
[0] Message Index
[*] Previous page