Closed fvcouture closed 1 month ago
Hi @fvcouture, please refer to the information below
Note: follow this step for scenarios such as establishing a network among robots [under 192.168.2.xxx only] or using one off-shelf router to establish a network among robot(s) [under any xxx.xxx.xxx.xxx depending on the router]
Hello Kaibiao
Thank you so much for your response! This was very helpful. What I was missing is that I can access the web ui of 192.168.2.1 (are those instructions anywhere in the documentation? Should I have read some docs instead of asking here?)
However, the hints on that post is not exactly what I wanted to do,
Here's what I did:
on that 10.10.10.XXX network:
So know the controller is in static address for VLAN1, once that configuration is in, the robot is getting a 10.10.10.XXX IP from my dhcp server
Ideally I would have loved to be able to configure the robot IP statically as well, but its ok as I can do a DHCP Reservation on my dhcp server (similar to what was done on the controller)
And I still have a routing issue. The controller and robot are reachable from the 10.10.10. network, but they are not using my gateway (10.10.10.1) to get out of that subnet and be able to ping/connect to other devices
i.e. My workstation is on network 10.10.11.X, I can ping all devices on 10.10.10.X except the robot and controller When I connect my workstation to network 10.10.10.X, I can ping the robot and controller, hence why I think they are not using 10.10.10.1 as gateway to reach other subnets.
on the controller admin web page, in Network -> Static Routes I did change the default 0.0.0.0 route to use 10.10.10.1 as gateway
Apologies for all the technical details here, my 2 questions are:
question 2 is much lower priority to us:
Hi @fvcouture,
Thank you for explaining further! Since making the controller a network client and assigning static IP involves more lower-level configurations, please send me a direct email (in my profile) and we can schedule a time to complete these configurations on a meeting call. Thanks!
Hi kaibiao!
I will send you an email next week and we can proceed from there
Many thanks!
I am unable to find how to change the ip address of the robot controller 192.168.2.100
I would like to be able to change the ip address of the controller and also be able to enable or disable the DHCP server on the controller (Looks like the DHCP Server ip address is 192.168.2.1)
ideally we want to set a static address on the interface, if the controller works as a dhcp client (rather than dhcp server) that works too.
We want to be able to reach multiple controllers on our network and we need to be able to control their IP and network range (i.e. not be limited to the 192.168.2.0/24 network)