FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We are updating our platform to a new
system.
Read more: Important
information on the platform change.
04-17-2023 07:49 PM
I just got a core last week and I am going through the process of learing the device. I had set several IP addresses on both Ethernet ports last week. Today I was going through the VPN setup and realized I needed to leave the XF51 port (Eth1) dynamic. When I tried to save the change the unit reported that there was a issue with the change, but it appeared to have saved the setting. I was not seeing the address update so I elected to restart the device, from the menu option. Since then I have not bee able to access or even ping the device, yet teh status light is green.
I saw the post where codecaptin suggest using the IPv6 address, I used the caluculator and have verified this address but i am still not able to access the core.
I can see the correct IPv6 address in wireshark, but it is just several attempts to discover before stopping.
I cannot get a IPv4 address at all.
I have attempted this by going through a switch and directly to the device.
I have removed this device from my lab network so there should not be any duplicate IPs.
Solved! Go to Solution.
04-18-2023 06:55 AM
Hello, try to connect your Device directly to your laptop/pc and then start ctrlX WORKS and take a look there on the devices page.
Your device should be visible here. Click on the name (not the IP) of the device and try to connect. Use first XF10.
04-18-2023 12:10 PM
XF10 has default a static IP adress 192.168.1.1/24 which you should use incase there is a direct connection so make sure your PC has and IP address in the same range (e.g. 192.168.1.10) With IPv6 you do not have this problem and since you see this address in Wireshark it must work.
Did you use this as URL: https://[fe80::2680:..........]? Also make sur eIPv6 is enabled on your PC
06-22-2023 11:28 AM
Is this still an issue or can this topic be closed?
06-22-2023 06:17 PM
this has been resolved, I had to reset the core and I beleive shortly after that I upgraded the unit to 1.20. no longer having this issue.