How does this work?
No doubt you've heard about this and are familiar with how to set it up. IP-based restrictions in the DyKnow Cloud setup allows an admin to specify on which IP addresses students may be monitored. When a student's public IP address is outside that range, they will not be monitored even if a teacher requests it. For example, this often happens when the student wakes up his device at home and gets an IP address that's not in the approved range, so therefore he cannot be monitored.
If the school is concerned about students connecting through hotspots or cellular networks at school, we advise that you set up a Time restriction instead of an IP restriction in DyKnow Cloud.
Public vs. Private IP
Most times when you look at your IP address it's something like 192.168.1.1, 10.1.1.1, or 172.16.0.0. This is your private IP. Within your private network, you can communicate with this, but when you are accessing something outside your network it will require a public IP address in order to know where to send responses. Responses come into the same public IP address for everybody on the network, but responses get to the correct private IP address through a process called NAT.
An analogy for this is the phone system. Most schools have a single public phone number and then private extensions. Your specific phone extension is like your private IP. Your school public phone number is like your public IP.
If your school is migrating to DyKnow Cloud from DyKnow Desktop or DyKnow Monitor CP on your own server, you are used to dealing with private IPs. The change we made in DyKnow Cloud to use public IPs makes it an easier setup and more reliable for you.