From the PC, what is the output of:
ip -4 addr; ip -4 ro; ip neigh show
ip -4 addr; ip -4 ro; ip neigh show
returns
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
3: enxc84d4422e3e4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
inet 192.168.0.101/24 brd 192.168.0.255 scope global noprefixroute enxc84d4422e3e4
valid_lft forever preferred_lft forever
4: lxcbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
inet 10.0.3.1/24 brd 10.0.3.255 scope global lxcbr0
valid_lft forever preferred_lft forever
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown
169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown
192.168.0.0/24 dev enxc84d4422e3e4 proto kernel scope link src 192.168.0.101 metric 101
I donāt see the ip neigh show
@trendy
rebooted the machine and ip neigh show without combined ip cmds returns
192.168.0.176 dev enxc84d4422e3e4 FAILED
192.168.0.249 dev enxc84d4422e3e4 FAILED
192.168.0.206 dev enxc84d4422e3e4 FAILED
192.168.0.23 dev enxc84d4422e3e4 FAILED
192.168.0.92 dev enxc84d4422e3e4 FAILED
192.168.0.165 dev enxc84d4422e3e4 FAILED
192.168.0.234 dev enxc84d4422e3e4 FAILED
192.168.0.51 dev enxc84d4422e3e4 FAILED
192.168.0.120 dev enxc84d4422e3e4 FAILED
192.168.0.65 dev enxc84d4422e3e4 FAILED
192.168.0.150 dev enxc84d4422e3e4 FAILED
192.168.0.223 dev enxc84d4422e3e4 FAILED
192.168.0.36 dev enxc84d4422e3e4 FAILED
192.168.0.109 dev enxc84d4422e3e4 FAILED
192.168.0.178 dev enxc84d4422e3e4 FAILED
192.168.0.251 dev enxc84d4422e3e4 FAILED
192.168.0.192 dev enxc84d4422e3e4 FAILED
192.168.0.9 dev enxc84d4422e3e4 FAILED
192.168.0.94 dev enxc84d4422e3e4 FAILED
192.168.0.167 dev enxc84d4422e3e4 FAILED
192.168.0.236 dev enxc84d4422e3e4 FAILED
192.168.0.53 dev enxc84d4422e3e4 FAILED
192.168.0.122 dev enxc84d4422e3e4 FAILED
192.168.0.67 dev enxc84d4422e3e4 FAILED
192.168.0.136 dev enxc84d4422e3e4 FAILED
192.168.0.209 dev enxc84d4422e3e4 FAILED
192.168.0.38 dev enxc84d4422e3e4 FAILED
192.168.0.111 dev enxc84d4422e3e4 FAILED
192.168.0.180 dev enxc84d4422e3e4 FAILED
192.168.0.253 dev enxc84d4422e3e4 FAILED
192.168.0.194 dev enxc84d4422e3e4 FAILED
192.168.0.11 dev enxc84d4422e3e4 FAILED
192.168.0.80 dev enxc84d4422e3e4 FAILED
192.168.0.153 dev enxc84d4422e3e4 FAILED
192.168.0.238 dev enxc84d4422e3e4 FAILED
192.168.0.55 dev enxc84d4422e3e4 FAILED
192.168.0.124 dev enxc84d4422e3e4 FAILED
192.168.0.69 dev enxc84d4422e3e4 FAILED
192.168.0.138 dev enxc84d4422e3e4 FAILED
192.168.0.211 dev enxc84d4422e3e4 FAILED
192.168.0.24 dev enxc84d4422e3e4 FAILED
192.168.0.97 dev enxc84d4422e3e4 FAILED
192.168.0.182 dev enxc84d4422e3e4 FAILED
192.168.0.196 dev enxc84d4422e3e4 FAILED
192.168.0.13 dev enxc84d4422e3e4 FAILED
192.168.0.82 dev enxc84d4422e3e4 FAILED
192.168.0.155 dev enxc84d4422e3e4 FAILED
192.168.0.224 dev enxc84d4422e3e4 FAILED
192.168.0.41 dev enxc84d4422e3e4 FAILED
192.168.0.126 dev enxc84d4422e3e4 FAILED
192.168.0.71 dev enxc84d4422e3e4 FAILED
192.168.0.140 dev enxc84d4422e3e4 FAILED
192.168.0.213 dev enxc84d4422e3e4 FAILED
192.168.0.26 dev enxc84d4422e3e4 FAILED
192.168.0.99 dev enxc84d4422e3e4 FAILED
192.168.0.168 dev enxc84d4422e3e4 FAILED
192.168.0.241 dev enxc84d4422e3e4 FAILED
192.168.0.198 dev enxc84d4422e3e4 FAILED
192.168.0.15 dev enxc84d4422e3e4 FAILED
192.168.0.84 dev enxc84d4422e3e4 FAILED
192.168.0.157 dev enxc84d4422e3e4 FAILED
192.168.0.226 dev enxc84d4422e3e4 FAILED
192.168.0.43 dev enxc84d4422e3e4 FAILED
192.168.0.112 dev enxc84d4422e3e4 FAILED
192.168.0.185 dev enxc84d4422e3e4 FAILED
192.168.0.142 dev enxc84d4422e3e4 FAILED
192.168.0.215 dev enxc84d4422e3e4 FAILED
192.168.0.28 dev enxc84d4422e3e4 FAILED
192.168.0.170 dev enxc84d4422e3e4 FAILED
192.168.0.243 dev enxc84d4422e3e4 FAILED
192.168.0.56 dev enxc84d4422e3e4 FAILED
192.168.0.1 dev enxc84d4422e3e4 FAILED
192.168.0.86 dev enxc84d4422e3e4 FAILED
192.168.0.159 dev enxc84d4422e3e4 FAILED
192.168.0.228 dev enxc84d4422e3e4 FAILED
192.168.0.45 dev enxc84d4422e3e4 FAILED
192.168.0.114 dev enxc84d4422e3e4 FAILED
192.168.0.187 dev enxc84d4422e3e4 FAILED
192.168.0.128 dev enxc84d4422e3e4 FAILED
192.168.0.201 dev enxc84d4422e3e4 FAILED
192.168.0.30 dev enxc84d4422e3e4 FAILED
192.168.0.103 dev enxc84d4422e3e4 FAILED
192.168.0.172 dev enxc84d4422e3e4 FAILED
192.168.0.245 dev enxc84d4422e3e4 FAILED
192.168.0.58 dev enxc84d4422e3e4 FAILED
192.168.0.3 dev enxc84d4422e3e4 FAILED
192.168.0.72 dev enxc84d4422e3e4 FAILED
192.168.0.145 dev enxc84d4422e3e4 FAILED
192.168.0.230 dev enxc84d4422e3e4 FAILED
192.168.0.47 dev enxc84d4422e3e4 FAILED
192.168.0.116 dev enxc84d4422e3e4 FAILED
192.168.0.189 dev enxc84d4422e3e4 FAILED
192.168.0.130 dev enxc84d4422e3e4 FAILED
192.168.0.203 dev enxc84d4422e3e4 FAILED
192.168.0.16 dev enxc84d4422e3e4 FAILED
192.168.0.89 dev enxc84d4422e3e4 FAILED
192.168.0.174 dev enxc84d4422e3e4 FAILED
192.168.0.247 dev enxc84d4422e3e4 FAILED
192.168.0.60 dev enxc84d4422e3e4 FAILED
192.168.0.5 dev enxc84d4422e3e4 FAILED
192.168.0.74 dev enxc84d4422e3e4 FAILED
192.168.0.147 dev enxc84d4422e3e4 FAILED
192.168.0.216 dev enxc84d4422e3e4 FAILED
192.168.0.33 dev enxc84d4422e3e4 FAILED
192.168.0.118 dev enxc84d4422e3e4 FAILED
192.168.0.191 dev enxc84d4422e3e4 FAILED
192.168.0.132 dev enxc84d4422e3e4 FAILED
192.168.0.205 dev enxc84d4422e3e4 FAILED
192.168.0.18 dev enxc84d4422e3e4 FAILED
192.168.0.91 dev enxc84d4422e3e4 FAILED
192.168.0.160 dev enxc84d4422e3e4 FAILED
192.168.0.233 dev enxc84d4422e3e4 FAILED
192.168.0.62 dev enxc84d4422e3e4 FAILED
192.168.0.7 dev enxc84d4422e3e4 FAILED
192.168.0.76 dev enxc84d4422e3e4 FAILED
192.168.0.149 dev enxc84d4422e3e4 FAILED
192.168.0.218 dev enxc84d4422e3e4 FAILED
192.168.0.35 dev enxc84d4422e3e4 FAILED
192.168.0.104 dev enxc84d4422e3e4 FAILED
192.168.0.177 dev enxc84d4422e3e4 FAILED
192.168.0.134 dev enxc84d4422e3e4 FAILED
192.168.0.207 dev enxc84d4422e3e4 FAILED
192.168.0.20 dev enxc84d4422e3e4 FAILED
192.168.0.93 dev enxc84d4422e3e4 FAILED
192.168.0.162 dev enxc84d4422e3e4 FAILED
192.168.0.235 dev enxc84d4422e3e4 FAILED
192.168.0.48 dev enxc84d4422e3e4 FAILED
192.168.0.121 dev enxc84d4422e3e4 FAILED
192.168.0.78 dev enxc84d4422e3e4 FAILED
192.168.0.151 dev enxc84d4422e3e4 FAILED
192.168.0.220 dev enxc84d4422e3e4 FAILED
192.168.0.37 dev enxc84d4422e3e4 FAILED
192.168.0.106 dev enxc84d4422e3e4 FAILED
192.168.0.179 dev enxc84d4422e3e4 FAILED
192.168.0.248 dev enxc84d4422e3e4 FAILED
192.168.0.193 dev enxc84d4422e3e4 FAILED
192.168.0.22 dev enxc84d4422e3e4 FAILED
192.168.0.95 dev enxc84d4422e3e4 FAILED
192.168.0.164 dev enxc84d4422e3e4 FAILED
192.168.0.237 dev enxc84d4422e3e4 FAILED
192.168.0.50 dev enxc84d4422e3e4 FAILED
192.168.0.123 dev enxc84d4422e3e4 FAILED
192.168.0.64 dev enxc84d4422e3e4 FAILED
192.168.0.137 dev enxc84d4422e3e4 FAILED
192.168.0.222 dev enxc84d4422e3e4 FAILED
192.168.0.39 dev enxc84d4422e3e4 FAILED
192.168.0.108 dev enxc84d4422e3e4 FAILED
192.168.0.181 dev enxc84d4422e3e4 FAILED
192.168.0.250 dev enxc84d4422e3e4 FAILED
192.168.0.195 dev enxc84d4422e3e4 FAILED
192.168.0.8 dev enxc84d4422e3e4 FAILED
192.168.0.81 dev enxc84d4422e3e4 FAILED
192.168.0.166 dev enxc84d4422e3e4 FAILED
192.168.0.239 dev enxc84d4422e3e4 FAILED
192.168.0.52 dev enxc84d4422e3e4 FAILED
192.168.0.125 dev enxc84d4422e3e4 FAILED
192.168.0.66 dev enxc84d4422e3e4 FAILED
192.168.0.139 dev enxc84d4422e3e4 FAILED
192.168.0.208 dev enxc84d4422e3e4 FAILED
192.168.0.25 dev enxc84d4422e3e4 FAILED
192.168.0.110 dev enxc84d4422e3e4 FAILED
192.168.0.183 dev enxc84d4422e3e4 FAILED
192.168.0.252 dev enxc84d4422e3e4 FAILED
192.168.0.197 dev enxc84d4422e3e4 FAILED
192.168.0.10 dev enxc84d4422e3e4 FAILED
192.168.0.83 dev enxc84d4422e3e4 FAILED
192.168.0.152 dev enxc84d4422e3e4 FAILED
192.168.0.225 dev enxc84d4422e3e4 FAILED
192.168.0.54 dev enxc84d4422e3e4 FAILED
192.168.0.127 dev enxc84d4422e3e4 FAILED
192.168.0.68 dev enxc84d4422e3e4 FAILED
192.168.0.141 dev enxc84d4422e3e4 FAILED
192.168.0.210 dev enxc84d4422e3e4 FAILED
192.168.0.27 dev enxc84d4422e3e4 FAILED
192.168.0.96 dev enxc84d4422e3e4 FAILED
192.168.0.169 dev enxc84d4422e3e4 FAILED
192.168.0.254 dev enxc84d4422e3e4 FAILED
192.168.0.199 dev enxc84d4422e3e4 FAILED
192.168.0.12 dev enxc84d4422e3e4 FAILED
192.168.0.85 dev enxc84d4422e3e4 FAILED
192.168.0.154 dev enxc84d4422e3e4 FAILED
192.168.0.227 dev enxc84d4422e3e4 FAILED
192.168.0.40 dev enxc84d4422e3e4 FAILED
192.168.0.113 dev enxc84d4422e3e4 FAILED
192.168.0.70 dev enxc84d4422e3e4 FAILED
192.168.0.143 dev enxc84d4422e3e4 FAILED
192.168.0.212 dev enxc84d4422e3e4 FAILED
192.168.0.29 dev enxc84d4422e3e4 FAILED
192.168.0.98 dev enxc84d4422e3e4 FAILED
192.168.0.171 dev enxc84d4422e3e4 FAILED
192.168.0.240 dev enxc84d4422e3e4 FAILED
192.168.0.57 dev enxc84d4422e3e4 FAILED
192.168.0.14 dev enxc84d4422e3e4 FAILED
192.168.0.87 dev enxc84d4422e3e4 FAILED
192.168.0.156 dev enxc84d4422e3e4 FAILED
192.168.0.229 dev enxc84d4422e3e4 FAILED
192.168.0.42 dev enxc84d4422e3e4 FAILED
192.168.0.115 dev enxc84d4422e3e4 FAILED
192.168.0.184 dev enxc84d4422e3e4 FAILED
192.168.0.129 dev enxc84d4422e3e4 FAILED
192.168.0.214 dev enxc84d4422e3e4 FAILED
192.168.0.31 dev enxc84d4422e3e4 FAILED
192.168.0.100 dev enxc84d4422e3e4 FAILED
192.168.0.173 dev enxc84d4422e3e4 FAILED
192.168.0.242 dev enxc84d4422e3e4 FAILED
192.168.0.59 dev enxc84d4422e3e4 FAILED
192.168.0.73 dev enxc84d4422e3e4 FAILED
192.168.0.158 dev enxc84d4422e3e4 FAILED
192.168.0.231 dev enxc84d4422e3e4 FAILED
192.168.0.44 dev enxc84d4422e3e4 FAILED
192.168.0.117 dev enxc84d4422e3e4 FAILED
192.168.0.186 dev enxc84d4422e3e4 FAILED
192.168.0.131 dev enxc84d4422e3e4 FAILED
192.168.0.200 dev enxc84d4422e3e4 FAILED
192.168.0.17 dev enxc84d4422e3e4 FAILED
192.168.0.102 dev enxc84d4422e3e4 FAILED
192.168.0.175 dev enxc84d4422e3e4 FAILED
192.168.0.244 dev enxc84d4422e3e4 FAILED
192.168.0.61 dev enxc84d4422e3e4 FAILED
192.168.0.2 dev enxc84d4422e3e4 FAILED
192.168.0.75 dev enxc84d4422e3e4 FAILED
192.168.0.144 dev enxc84d4422e3e4 FAILED
192.168.0.217 dev enxc84d4422e3e4 FAILED
192.168.0.46 dev enxc84d4422e3e4 FAILED
192.168.0.119 dev enxc84d4422e3e4 FAILED
192.168.0.188 dev enxc84d4422e3e4 FAILED
192.168.0.133 dev enxc84d4422e3e4 FAILED
192.168.0.202 dev enxc84d4422e3e4 FAILED
192.168.0.19 dev enxc84d4422e3e4 FAILED
192.168.0.88 dev enxc84d4422e3e4 FAILED
192.168.0.161 dev enxc84d4422e3e4 FAILED
192.168.0.246 dev enxc84d4422e3e4 FAILED
192.168.0.63 dev enxc84d4422e3e4 FAILED
192.168.0.4 dev enxc84d4422e3e4 FAILED
192.168.0.77 dev enxc84d4422e3e4 FAILED
192.168.0.146 dev enxc84d4422e3e4 FAILED
192.168.0.219 dev enxc84d4422e3e4 FAILED
192.168.0.32 dev enxc84d4422e3e4 FAILED
192.168.0.105 dev enxc84d4422e3e4 FAILED
192.168.0.190 dev enxc84d4422e3e4 FAILED
192.168.0.135 dev enxc84d4422e3e4 FAILED
192.168.0.204 dev enxc84d4422e3e4 FAILED
192.168.0.21 dev enxc84d4422e3e4 FAILED
192.168.0.90 dev enxc84d4422e3e4 FAILED
192.168.0.163 dev enxc84d4422e3e4 FAILED
192.168.0.232 dev enxc84d4422e3e4 FAILED
192.168.0.49 dev enxc84d4422e3e4 FAILED
192.168.0.6 dev enxc84d4422e3e4 FAILED
192.168.0.79 dev enxc84d4422e3e4 FAILED
192.168.0.148 dev enxc84d4422e3e4 FAILED
192.168.0.221 dev enxc84d4422e3e4 FAILED
192.168.0.34 dev enxc84d4422e3e4 FAILED
192.168.0.107 dev enxc84d4422e3e4 FAILED
however ip neigh show responds differently depending on the cmd ran before it.
if I didnt run nmap, the above output didnt show. after nmap and then running ip neigh show, result changes
Did you try to access the dietpi recently? If there is nothing from ip neigh show there is something wrong with the PC, otherwise it should show that there is an incomplete entry for the dietpi IP.
i edited above post to show return from ip neigh show, please see.
I havnt been able to access the dietpi period, been trying for 3 days now, this has taken hours of back and forward and nothing has been gained.
il never buy a device from FriendlyElec again, their boards suck!!!
what about connecting with UART?
I would:
- try to connect it with a different cable.
- try to connect it on a router with default settings and let it get IP from the DHCP server of the router.
- If all above fails, connect the serial (3 pins next to USB) at 115200 8N1 with a USB2TTL adapter and check the terminal to see what is going on in there.
1 Like
regarding 2. should i edit /boot/dietpi.txt back to dhcp instead of static?
also you say 3 pins next to USB, from the freindly elec page does it not show the UART pins are 8 and 10 + gnd ofc?
6 GND
8 GPIO3_A4/UART1_TX 100
10 GPIO3_A6/UART1_RX 102
Guys keep in mind, AUTO_SETUP parameter are applied on the first Initial boot only. As well you might need to use a crossover cable if Iām not mistaken?
Anyway what is the plan with the Neo? because without a valid internet connection, you will not be able to complete the initial setup or install other stuff. I highly recommend to connect the Neo into the router or switch to gain regular access.
@Joulinar my plan first is to just get SSH or UART access to the neo3ā¦
3 days wasted, soon im thinking to hit the device with a hammer, and just buy another raspberry piā¦ atleast the thing is straight forward and up and running within 5 minutes.
freindlyelec devices are rubbish.
Itās not the device, itās the way you are trying to gain access, without even the knowledge how to do. Simply plug it into your router, let it become a regular IP address and your are done. Not sure why you are trying it that complicate.
it appears nobody has the knowledge here, because the problem is still unsolved.
could it possibly be how the dietpi image file is copied to the sd card?
sudo dd if=DietPi_NanoPiNEO3-ARMv8-Bookworm.img of=/dev/sde bs=16M
If you have possibility to gain UART access would be best. This way you can see whatās happen on the device.
Or simply plug the Neo into your router. Still not sure why you are not doing it.
@Joulinar I dont have a router, but I could buy one just for this purpose.
im going to try access via UART before I go shopping.
I am referring to the debugging UART port.
https://wiki.friendlyelec.com/wiki/index.php/NanoPi_NEO3#Configure_parameters_for_serial_port
But how does your desktop is connecting to the internet?
The problem is, that you went an unusual way:
- No router involved, so no DHCP server that cares about IP assignment and just little knowledge about networking
- Neo3 is locally only accesible via UART (if this even counts as locally?), no output for a monitor for easy troubleshooting. Setting up an adapter would also require some sort of access to the device.
- the changes made in DietPiās
boot/dietpi.txtonly apply on very first boot after flashing the image
IDK if itās easily possible to read the SDcard from another PC and make directly changes to the /etc/interfaces? You would need a card reader though to do this.
But the good thing is, you learned a lot from this stuff, even when you are now getting gray hairā¦
When I started with SBCs (with RPiās you consider as āeasyā) I wasted days because I had no idea what I was doing 
I think every modern NIC (build after 2000) should detect this automatically, thanks to auto-MDIX feature.
But when I look into dietpi survey I see active NEO3 users, who does not have problems with NEO3 NIC
2 Likes
Could the root cause of the problem be that the firstboot stucks in a state where no ssh connection is enabled because the item
AUTO_SETUP_AUTOMATED = 1
was not set in dietpi.txt?
See Usage hints / HowTo - DietPi.com Docs for further details.
@MichaIng : I do not know how the firstrun setup behaves if there is no internet connection for time sync resp. updatesā¦
1 Like
the system will boot and perform some inital steps like asign an IP address and wait for the first login. Internet access should not matter for the first access.
1 Like
As the host is a Linux system, all fine with directly editing /etc/network/interfaces (instead of dietpi.txt) on the NEO3 SD card as well as on the host PC it is connected to. I never tried to link two devices directly, but what trendy says sounds logic.
On the host PC, replace the whole config block with:
allow-hotplug enxc84d4422e3e4
iface enxc84d4422e3e4 inet static
address 192.168.0.101/24
I am not sure how well config keys without values work, but not defining the gateway at all definitely works. Then to assure it is up:
ifdown enxc84d4422e3e4
ifup enxc84d4422e3e4
On the NEO3, replace the whole /etc/network/interfaces with:
allow-hotplug eth0
iface eth0 inet static
address 192.168.0.100/24
I did not see the allow-hotplug eth0 line in your config above. Without it, the interface is defined, but not brought up at boot automatically, which would explain why you cannot reach it. Instead of allow-hotplug, you could also use auto, which does not wait for the device to be detected/trigger udev, but brings up the network in any case at a fixed stage/order at boot.
However, for a direct and assured access to the device, I also recommend to have a USB-UART adapter at hand. This is also great for debugging issues at a much earlier boot stage, having U-Boot console, if needed etc. The debug UART at the 3 pins next to the USB port is enabled OOTB, and PuTTY can be used as well to connect to the serial/COM port from the host.
2 Likes