From 2e1423247478f8cf69b16c31602fb165fcb1da59 Mon Sep 17 00:00:00 2001 From: Egor Savkin Date: Fri, 12 Jul 2024 17:31:59 +0800 Subject: [PATCH] Add IP collision case Signed-off-by: Egor Savkin --- src/sw_sup/networking.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/sw_sup/networking.md b/src/sw_sup/networking.md index 7b8e458..68879f9 100644 --- a/src/sw_sup/networking.md +++ b/src/sw_sup/networking.md @@ -16,6 +16,7 @@ a-la `I can't connect, please help`. 7. Some weird bugs in Vivado, leading to not working SFP on certain combinations of builds and Kaslis (very rare) 8. Running configured for external reference Kasli without external reference clock signal 9. Using legacy firmware with newer hardware. ARTIQ-6 doesn't support Kasli v2.0.2 +10. Some other device in your network already reserved the configured IP address. ## Ways to diagnose @@ -27,6 +28,8 @@ a-la `I can't connect, please help`. 5. `nmap` and `arp` to scan your network to help your Kasli get discovered. May be restricted in your network. 6. Directly connect your Kasli to the PC via Ethernet and set up networking on the PC: `ip addr change 192.168.1.0/24 dev eth0` 7. Become a router and capture all the packets when your Kasli tries to connect to the network. +8. Turn off the Carrier/Kasli and `ping` the configured IP address. If it pings, then you'll need either set different + IP address on your Carrier or somehow deal with that other device - remove, assign different address, move to other network etc. ## Direct connection