Docs about native devices

[jdelrue]

Native Devices can be any network device that is reachable through a Network Controller. Once a Native Device has been created, rules can be applied to the Native Device the same way rules are applied to servers and NIACs. While traffic to Native Devices is not encrypted on the network layer, they can be a safe way to reach devices that are only reachable by the Network Controller by connecting/giving access to the Network Controller to a specific VLAN.

For instance, should an IP camera be situated within the camera VLAN and access by specific users is required, you can register the camera's IP as a Native Device with the on-premises Network Controller. By establishing the appropriate access rules, users will then be able to access the camera from any location via Jimber Network Isolation.

@Baertie can you make this beautiful again? ^

[Baertie]

@jdelrue @danny-delrue

[danny-delrue]

Further refined

[JorisBassle]

It doesn't say how a Native device can be reached for a user. Once the native device is created the admin needs to add a 'allow custom port' rule that gives specific groups access to the native device (under destination)

Here group testers77 can ping to the native device called 'joskepc-staging.com'. All other groups can't reach the native device unless specifically said so.

[jdelrue]

Please extend with some more information

[JorisBassle]

Seems to be correctly added, I will have to reread the whole page to close this

[jdelrue]

Its not only allow custom port, also services