Local Network IP range issue

NickNikzad

I successfully established a connection between my laptop and the OAK-CM4 device using a VNC connection. In order to use it on our production system, I attempted to access my OAK-CM4 pi via VNC from a different network range, specifically 10.1.1.x, but encountered connection issues. To troubleshoot, I modified the RPi IP to 10.1.1.2, but regrettably, I am now unable to establish any access from my laptop. I would greatly appreciate any guidance or suggestions to resolve this matter.

jakaskerl

Hi NickNikzad
You can connect a monitor mouse and a keyboard directly to the CM4 and reset the settings from there.
Thanks,
Jaka

NickNikzad

Thank you for your response. In my case, I have the OAK-D CM4 PoE version. Should I consider opening the case to directly connect a monitor, mouse, and keyboard? Another concern I have is how to utilize it within my local network with a different IP range. Changing the network IP range might be challenging since many other devices are already connected and operational.

jakaskerl

Hi NickNikzad
Would you mind specifying the IP's/network masks and how your network is set up?
You can usually just change the network of your laptop to the same subnet to be able to connect to it again. Just make sure you change it back afterwards to avoid any conflicts.

NickNikzad Another concern I have is how to utilize it within my local network with a different IP range.

A different subnet would require port fowarding or running vnc on cloud.

Hope this helps,
Jaka

NickNikzad

jakaskerl Thanks for the reply. Could you assist me in understanding how to perform port forwarding and set up VNC on the cloud? In my local network, the IP range is 10.1.1.x with a subnet mask of 255.255.255.0. All devices are linked to a switch before connecting to two separate PCs.

jakaskerl

Hi NickNikzad
It's probably best if you look it up on the web, the process is standard for any machine running linux (CM4 is just a glorified RPI and should therefore have the same setup as the RPI).

I'm also adding this quick guide from ChatGPT:

Port Forwarding:

Access your router's web interface. This usually involves typing in an IP address into a web browser. Common addresses include 192.168.0.1 or 192.168.1.1. Consult your router's documentation for the correct address.
Log in. Use the username and password for your router. If you haven't set one, it might still be the default credentials (commonly "admin" and "admin" or "password").
Navigate to the port forwarding section. This may be labeled as "Port Forwarding", "Virtual Server", or something similar.
Add a new rule:
- External (or WAN) Port: Choose a port that you want to use from the outside. For instance, 5900 is standard for VNC, but you might want to use a different one for security reasons.
- Internal (or LAN) IP Address: This should be the IP address of your OAK-D CM4 PoE device, e.g., 10.1.1.x.
- Internal Port: This will typically be 5900 for VNC.
- Protocol: Usually, you can select TCP for VNC.
Save and apply changes. The port forward is now set up.

VNC on Cloud:

If you're thinking of using a cloud service as a bridge for VNC, the idea would be to:

Set up a Virtual Private Server (VPS) on cloud platforms like AWS, Google Cloud, DigitalOcean, etc.
Install a VNC server on your OAK-D CM4.
Connect the OAK-D CM4's VNC server to the VPS.
From your other locations or networks, connect to the VPS. This way, you don't need to change anything in your local network.

Steps:

Sign up and create a VPS instance on a cloud provider. Ensure the VPS has a static public IP address.
Install a VNC server on the VPS.
Secure your VPS: Before exposing the VNC server to the internet, ensure you have proper security measures. This includes strong passwords, disabling root login, and possibly using a tool like fail2ban.
Connect your OAK-D CM4's VNC client to the VPS's IP address.
From anywhere in the world, use a VNC client to connect to your VPS's IP address. It will then be relayed to your OAK-D CM4.

Notes:

This method essentially treats the VPS as a relay or bridge.
Ensure to regularly update and maintain security patches for all devices and servers involved. There are significant risks when exposing services to the internet.
For sensitive applications, consider using VPNs or more secure methods of remote access.

Given the complexity and potential security implications of these steps, especially if you're not familiar with networking and cloud systems, you might want to consult with an IT specialist or someone familiar with these tasks to ensure everything is set up securely and correctly.

Hope this helps you in any way.

Thanks,
Jaka

NickNikzad

jakaskerl Thanks indeed.