forked from sinara-hw/assembly
Add IP collision case
Signed-off-by: Egor Savkin <es@m-labs.hk>
This commit is contained in:
parent
d71bc3a57e
commit
2e14232474
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue