NanoPi M1 Plus | Ethernet issues

[lucas-law]

Creating a bug report/issue

Required Information

• DietPi version | cat /boot/dietpi/.version
  G_DIETPI_VERSION_CORE=7
  G_DIETPI_VERSION_SUB=5
  G_DIETPI_VERSION_RC=2
  G_GITBRANCH='master'
  G_GITOWNER='MichaIng'
  G_LIVE_PATCH_STATUS[0]='not applicable

• Distro version | echo $G_DISTRO_NAME or cat /etc/debian_version
  10.10

• Kernel version | uname -a
  buster
  Linux DietPi 5.10.60-sunxi #21.08.1 SMP Wed Aug 25 18:19:32 UTC 2021 armv7l GNU/Linux

• SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
  NanoPi M1 Plus (armv7l)

• Power supply used | (EG: 5V 1A RAVpower)
  5V 2A RAVpower

• SDcard used | (EG: SanDisk ultra)
  Samsung 32 EVO +

Additional Information (if applicable)

• Software title | (EG: Nextcloud)
  dhclient
• Was the software title installed freshly or updated/migrated?
  freshly
• Can this issue be replicated on a fresh installation of DietPi?
  Yes

• Bug report ID | echo $G_HW_UUID
  e77f1110-dd72-4724-8388-464f14fdc84e

Steps to reproduce

1. configure eth0 adapter and request ip
2. use tcpdump to capture the dhcp package.

Expected behaviour

• Normal request to ip

Actual behaviour

• Received nothing dhcp reply pkg from router，request id failed。

Extra details

1. wlan0 can request ip.
2. eth0 links ok and can recv other udp msg from network.
3. the wlan0's tcpdump data as fllows:

root@DietPi:~# dhclient -i wlan0
16:22:04.459956 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from b0:f1:ec:2d:c1:d8 (oui Unknown), length 300, xid 0xe5899552, Flags [none] (0x0000)
	  Client-Ethernet-Address b0:f1:ec:2d:c1:d8 (oui Unknown)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Hostname Option 12, length 6: "DietPi"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, BR, Time-Zone, Default-Gateway
	      Domain-Name, Domain-Name-Server, Option 119, Hostname
	      Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route
	      NTP
	    Client-ID Option 61, length 19: hardware-type 255, ec:2d:c1:d8:00:01:00:01:27:9c:b9:93:02:81:2c:03:fa:12
	    END Option 255, length 0
	    PAD Option 0, length 0, occurs 12
16:22:04.495060 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 576)
    192.168.178.1.bootps > 192.168.178.77.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 548, xid 0xe5899552, Flags [none] (0x0000)
	  Your-IP 192.168.178.77
	  Server-IP 192.168.178.1
	  Client-Ethernet-Address b0:f1:ec:2d:c1:d8 (oui Unknown)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Offer
	    Server-ID Option 54, length 4: 192.168.178.1
	    Lease-Time Option 51, length 4: 864000
	    RN Option 58, length 4: 432000
	    RB Option 59, length 4: 756000
	    Subnet-Mask Option 1, length 4: 255.255.255.0
	    Default-Gateway Option 3, length 4: 192.168.178.1
	    Domain-Name-Server Option 6, length 4: 192.168.178.1
	    Domain-Name Option 15, length 9: "fritz.box"
	    BR Option 28, length 4: 192.168.178.255
	    NTP Option 42, length 4: 192.168.178.1
	    END Option 255, length 0
	    PAD Option 0, length 0, occurs 239
16:22:04.495605 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from b0:f1:ec:2d:c1:d8 (oui Unknown), length 300, xid 0xe5899552, Flags [none] (0x0000)
	  Client-Ethernet-Address b0:f1:ec:2d:c1:d8 (oui Unknown)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Request
	    Server-ID Option 54, length 4: 192.168.178.1
	    Requested-IP Option 50, length 4: 192.168.178.77
	    Hostname Option 12, length 6: "DietPi"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, BR, Time-Zone, Default-Gateway
	      Domain-Name, Domain-Name-Server, Option 119, Hostname
	      Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route
	      NTP
	    Client-ID Option 61, length 19: hardware-type 255, ec:2d:c1:d8:00:01:00:01:27:9c:b9:93:02:81:2c:03:fa:12
	    END Option 255, length 0
16:22:04.664402 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 576)
    192.168.178.1.bootps > 192.168.178.77.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 548, xid 0xe5899552, Flags [none] (0x0000)
	  Your-IP 192.168.178.77
	  Server-IP 192.168.178.1
	  Client-Ethernet-Address b0:f1:ec:2d:c1:d8 (oui Unknown)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: ACK
	    Server-ID Option 54, length 4: 192.168.178.1
	    Lease-Time Option 51, length 4: 864000
	    RN Option 58, length 4: 432000
	    RB Option 59, length 4: 756000
	    Subnet-Mask Option 1, length 4: 255.255.255.0
	    Default-Gateway Option 3, length 4: 192.168.178.1
	    Domain-Name-Server Option 6, length 4: 192.168.178.1
	    Domain-Name Option 15, length 9: "fritz.box"
	    BR Option 28, length 4: 192.168.178.255
	    NTP Option 42, length 4: 192.168.178.1
	    END Option 255, length 0
	    PAD Option 0, length 0, occurs 239

4. the eth0 tcpdump data as fllows:

root@DietPi:~# dhclient -i eth0
16:23:18.079786 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 02:81:2c:03:fa:12 (oui Unknown), length 300, xid 0xc9aeb208, Flags [none] (0x0000)
	  Client-Ethernet-Address 02:81:2c:03:fa:12 (oui Unknown)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Hostname Option 12, length 6: "DietPi"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, BR, Time-Zone, Default-Gateway
	      Domain-Name, Domain-Name-Server, Option 119, Hostname
	      Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route
	      NTP
	    Client-ID Option 61, length 19: hardware-type 255, 2c:03:fa:12:00:01:00:01:27:9c:b9:93:02:81:2c:03:fa:12
	    END Option 255, length 0
	    PAD Option 0, length 0, occurs 12
16:23:27.021965 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 02:81:2c:03:fa:12 (oui Unknown), length 300, xid 0xc9aeb208, secs 9, Flags [none] (0x0000)
	  Client-Ethernet-Address 02:81:2c:03:fa:12 (oui Unknown)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Hostname Option 12, length 6: "DietPi"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, BR, Time-Zone, Default-Gateway
	      Domain-Name, Domain-Name-Server, Option 119, Hostname
	      Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route
	      NTP
	    Client-ID Option 61, length 19: hardware-type 255, 2c:03:fa:12:00:01:00:01:27:9c:b9:93:02:81:2c:03:fa:12
	    END Option 255, length 0
	    PAD Option 0, length 0, occurs 12
16:23:32.770496 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 02:81:2c:03:fa:12 (oui Unknown), length 300, xid 0xc7b65164, Flags [none] (0x0000)
	  Client-Ethernet-Address 02:81:2c:03:fa:12 (oui Unknown)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Hostname Option 12, length 6: "DietPi"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, BR, Time-Zone, Default-Gateway
	      Domain-Name, Domain-Name-Server, Option 119, Hostname
	      Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route
	      NTP
	    Client-ID Option 61, length 19: hardware-type 255, 2c:03:fa:12:00:01:00:01:27:9c:b9:93:02:81:2c:03:fa:12
	    END Option 255, length 0
	    PAD Option 0, length 0, occurs 12

5. I installed another OS like debain and it looks good.

[MichaIng]

If you have a screen+keyboard or serial console attached, please run the following commands and paste the output here:

ifdown --force wlan0
ifdown --force eth0
ifup eth0
ip l
ip a
ip r

Quote tags around console pastes are btw nice for readability (see my edit of your post):

```
text from monotype console
```

[lucas-law]

There are some outputs from serial port:

root@DietPi:~# ifdown --force wlan0
Removed stale PID file
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/b0:f1:ec:2d:c1:d8
Sending on   LPF/wlan0/b0:f1:ec:2d:c1:d8
Sending on   Socket/fallback
DHCPRELEASE of 192.168.178.123 on wlan0 to 192.168.178.1 port 67
root@DietPi:~# ifdown --force eth0
Removed stale PID file
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/02:81:2c:03:fa:12
Sending on   LPF/eth0/02:81:2c:03:fa:12
Sending on   Socket/fallback
root@DietPi:~# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 02:81:2c:03:fa:12 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether b0:f1:ec:2d:c1:d8 brd ff:ff:ff:ff:ff:ff
root@DietPi:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 02:81:2c:03:fa:12 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether b0:f1:ec:2d:c1:d8 brd ff:ff:ff:ff:ff:ff
root@DietPi:~# ip r
root@DietPi:~# 

[Joulinar]

I guess command ifup eth0 is missing, correct?

[lucas-law]

Yes, ifup eth0 have some erros like:

root@DietPi:~# ifup eth0
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/02:81:2c:03:fa:12
Sending on   LPF/eth0/02:81:2c:03:fa:12
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
root@DietPi:~# 

[Joulinar]

did you changed Ethernet cable or used a different port? How does it behave if you switch to STATIC IP on eth0

[lucas-law]

1. switch to static ip and it works not good:

root@DietPi:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.178.199  netmask 255.255.255.0  broadcast 192.168.178.255
        ether 02:81:2c:03:fa:12  txqueuelen 1000  (Ethernet)
        RX packets 7431  bytes 616556 (602.1 KiB)
        RX errors 0  dropped 810  overruns 0  frame 0
        TX packets 487  bytes 156390 (152.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 45  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 8  bytes 660 (660.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8  bytes 660 (660.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@DietPi:~# ping 192.168.178.1
PING 192.168.178.1 (192.168.178.1) 56(84) bytes of data.
^C
--- 192.168.178.1 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 134ms

root@DietPi:~# 

2. This board just have 1 Ethernet cable, and It works good on other OS. so maybe some errors occured.

[Joulinar]

can you check for kernel error messages

dmesg -l err,crit,alert,emerg

[lucas-law]

root@DietPi:~# dmesg -l err,crit,alert,emerg
[    6.860327] lima 1c40000.gpu: dev_pm_opp_set_regulators: no regulator (mali) found: -19
root@DietPi:~# 
root@DietPi:~# 

[MichaIng]

This is 1, isn't it?

cat /sys/class/net/eth0/carrier

Can you check whether there are kernel upgrades available, and which kernel packages are installed?

apt update
apt full-upgrade
dpkg -l | grep 'linux-image-'

[lucas-law]

1. yes , cat /sys/class/net/eth0/carrier and it print 1

2. dpkg -l print:

ii  linux-image-current-sunxi              21.08.1                             armhf        Linux kernel, version 5.10.60-sunxi

[MichaIng]

Does the router/DHCP server show any logs or info about the DietPi device? I don't think that it is a clear issue with hardware or DietPi when everything else, including static IP and DHCP on WiFi work fine and also outgoing DHCP requests do not fail.

So it seems to be the DHCP server which does not receive or block those or for another reason denies to assign an IP. Probably it simply does not like the fact that it has a client with this hostname in the list already (due to WiFi DHCP assignment) and then ignores the request with same hostname form Ethernet? So probably removing the WiFi based DHCP reservation/info for that DietPi system helps, or the other way round, changing the systems hostname from DietPi to a more specific one.

[lucas-law]

I tried to connect another router, and set hostname to nanopi instead of DietPi the same problem as the old router.

[Joulinar]

Do you have any firewall software installed?

[lucas-law]

No, after installing the new dietpi os, there will be problems configuring the network with eth0.